Create a SPEC.md with user stories, acceptance criteria, and risks.
npx skills add https://github.com/notque/claude-code-toolkit --skill spec-writer-notque
Please help me install this Agent Skill. Skill: spec-writer Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/spec-writer Command: npx skills add https://github.com/notque/claude-code-toolkit --skill spec-writer-notque
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definitions, risks, and estimation to ensure alignment before design and implementation.
Draft a SPEC.md at the project root describing the feature scope, user stories, acceptance criteria, and risks in a single, testable document.
High-intent search queries and answers about installing and using this skill.
A software specification defines user stories, testable acceptance criteria, out-of-scope items, risks, and estimation to ensure alignment before design. This approach enforces a measurable document serving as the single source of truth for development and validation.
A feature specification document prevents scope creep by explicitly defining at least three out-of-scope items alongside user stories and acceptance criteria. Including risks, assumptions, and estimation further constrains the feature lifecycle boundaries before implementation begins.
A specification should include a maximum of seven user stories to maintain focus before moving to feature design. Limiting user stories ensures the specification remains testable, measurable, and manageable while enforcing gate checks prior to design execution.
Generating a SPEC.md works within an active git worktree by saving the artifact to .feature/SPEC.md instead of the project root. This ensures the specification document integrates seamlessly into isolated feature branches and phased workflows.
You need to define risks and assumptions in a project specification before proceeding to feature design and implementation. Documenting these elements alongside estimation and acceptance criteria ensures the team addresses potential roadblocks early in the phased workflow.
The best way to structure acceptance criteria for user stories is to make them objective and testable. This ensures the specification serves as a measurable single source of truth for validation and guides the entire feature lifecycle from design to release.
telihaGenerate specification files from requirements into specs/[feature-name]/spec.md.
zenbuappsConvert vague requirements into design artifacts through structured iterative questioning.
ngocsangyemDraft gate-driven planning documents with YAML frontmatter and acceptance criteria for MeowKit implementations.
ChazzCoinConvert rough descriptions into spec-task user stories with acceptance criteria.
