SkillsAdd

jkappers/agent-skills

spec-writer

Write feature specifications that capture requirements and acceptance criteria.

First seen Feb 9, 2026

Installation

$ npx skills add jkappers/agent-skills --skill spec-writer
View on skills.sh ↗ GitHub repository ↗

Summary

  • Write feature specifications that capture requirements and acceptance criteria.
  • Use when (1) writing a new feature spec, (2) documenting functional requirements, (3) defining acceptance criteria for a feature, (4) capturing design goals and constraints for planned work, or (5) structuring a product idea into a formal specification.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Shared topics
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Shared topics
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Shared topics
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-rbac Shared topics
microsoft/azure-skills 489K installs
azure-hosted-copilot-sdk Shared topics
microsoft/azure-skills 440.4K installs

Also in this package

Other skills from jkappers/agent-skills · top by installs.

npx skills add jkappers/agent-skills
conventional-commit 67 dotnet-dockerfile 44 enhance-prompt 43 react-dockerfile 28 optimize-md 21 skill-creator 20 gap-analysis 20 sprint-planner 15 tech-planner 14 plan-jira-ticket 11

Browse all from jkappers/agent-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License MIT
Default branch main
Open issues 1
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,453 B
  • docs SUMMARY.md 352 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 22 installs

SKILL.md

Spec Writing

Capture WHAT and WHY. Never prescribe HOW.

When invoked with arguments, write a spec for: $ARGUMENTS

Workflow

  1. Gather context: Collect feature description, target users, problem statement, and constraints from user input or $ARGUMENTS. Ask clarifying questions for missing information.
  2. Create directory: specs/feature-name/
  3. Copy assets/spec.md to specs/feature-name/README.md
  4. Complete every section from the Required Sections table below
  5. Validate against the checklist before completing

Required Sections

Section Content
Feature Overview 2-3 paragraphs: what, who, problem solved
Success Criteria Measurable outcomes defining "done"
Design Goals Primary (must) and secondary (nice to have)
User Experience 1-2 paragraphs: interaction, journey
Design Rationale 1-2 paragraphs: why this approach, trade-offs
Constraints/Assumptions Technical constraints, business assumptions
Functional Requirements FR-N format, max 6-8, with acceptance criteria
Edge Cases Unusual inputs, failure scenarios

Acceptance Criteria

- [ ] Given [context], when [action], then [expected result]

Include 2-4 criteria per requirement: happy path + key failure cases.

Scope Check

More than 6-8 requirements = feature too large. Split: identify 3-4 core requirements, flag rest for separate spec in "Scope Notes" section.

Validation Checklist

  • Single MVP focus (one deliverable)
  • All requirements have testable criteria
  • No TODO/TBD placeholders
  • Edge cases documented

Exclusions

A spec defines WHAT to build, not HOW to build it. Exclude:

  • Implementation approach or technical strategy
  • Architecture diagrams
  • Code examples
  • Database schemas
  • API signatures
  • Technology or framework choices
  • Development estimates, timelines, or phase sections

Supporting Files

  • assets/spec.md - Spec template
  • references/spec-guide.md - Extended guidance on ADRs and archival