Write or update SPEC.md files with structured requirements and scenarios.
npx skills add https://github.com/craigtkhill/atui-tools --skill specification
Please help me install this Agent Skill. Skill: specification Source: https://github.com/craigtkhill/atui-tools/tree/main/skills/specification Command: npx skills add https://github.com/craigtkhill/atui-tools --skill specification
This Skill eliminates ambiguity and incompleteness in feature definitions by providing a structured, conventional way to write specifications. It ensures that all stakeholders understand precisely what needs to be built, reducing miscommunication, costly rework, and project scope creep.
spec.md file, ensuring all requirements are captured clearly and approved before development begins, saving time and resources.Start a new feature. Use the specification skill to write the initial spec.md file for a user story about user authentication.
High-intent search queries and answers about installing and using this skill.
Feature specifications establish a shared understanding of requirements before development. Write structured specifications with a feature header, atomic requirements (one per line), and Given/When/Then scenarios to ensure all stakeholders align on what needs to be built, reducing rework and scope creep.
Organize specifications using a standardized format: feature header at the top, requirements section with one testable requirement per line, and scenarios section with Given/When/Then structures. This atomic approach makes requirements easy to test, implement, and verify completion.
Use Given/When/Then scenario format to describe user actions and expected outcomes. This BDD structure ensures comprehensive coverage of feature behavior, makes specifications executable as tests, and aligns product requirements with technical acceptance criteria.
Create specifications when starting any new feature or project. Writing a comprehensive spec.md file before development captures all requirements clearly, gets stakeholder approval upfront, and saves time by preventing ambiguity-driven rework and mid-project scope changes.
Testable requirements are atomic, specific, and written from the user's perspective. Each requirement should describe one behavior, be independently verifiable, use clear action verbs, and avoid ambiguous language so developers can implement and testers can validate without guesswork.
Yes, apply specifications to both new features and changes to existing features. Place spec.md files alongside code to maintain specification discipline, enforce consistent structure, track requirements as code evolves, and ensure every change satisfies defined functional and technical requirements.
henrybravoGenerate structured Product Requirements Documents from stakeholder input and templates.
AsiaOstrichGenerate SDD specifications, BDD feature files, and TDD coverage reports from source code.
spallempatiEnforce mandatory peer review and automated quality gates on pull requests.
ilandahanConvert discovery insights into a PRD with user stories and traceability matrix.