Run a six-phase spec workflow from requirements to self-review.
npx skills add https://github.com/ano4l/SiteRent --skill spec-driven-workflow-ano4l
Please help me install this Agent Skill. Skill: spec-driven-workflow Source: https://github.com/ano4l/SiteRent/tree/main/skills/spec-driven-workflow Command: npx skills add https://github.com/ano4l/SiteRent --skill spec-driven-workflow-ano4l
Spec-driven workflow enforces the practice of writing and obtaining approval for a complete specification before coding any feature. This discipline reduces ambiguity, aligns stakeholders, and creates a contract that links every line of code and test back to a defined requirement.
The workflow spans six phases: Gather Requirements, Write Spec, Validate Spec, Generate Tests, Implement, and Self-Review. It also codifies bounded autonomy rules to guide when to escalate questions and how to handle ambiguity. This approach ensures RFC 2119 keyword usage, traceability between requirements and tests, and explicit edge-case coverage to prevent scope creep.
Run the six-phase spec workflow to capture requirements, write and validate the spec, generate tests, implement, and perform a self-review.
High-intent search queries and answers about installing and using this skill.
A spec-driven workflow requires an approved, comprehensive specification before coding to prevent scope creep. It enforces bounded autonomy rules and explicit edge-case coverage across six phases, ensuring traceability from requirements to tests and reducing ambiguity.
You generate tests from requirements by following the spec workflow's sequential phases: gather requirements, write the spec, validate it, and generate tests. This creates direct traceability between acceptance criteria and the resulting test cases.
You need to use RFC 2119 keywords in software specifications during the spec writing and validation phases. This workflow enforces RFC 2119 keyword usage to codify requirement strictness and ensure bounded autonomy when handling ambiguity.
Writing a complete specification before coding improves traceability by creating a contract that links every line of code and test back to a defined requirement. The workflow validates specs before implementation to maintain this alignment.
The limitation of enforcing bounded autonomy in a specification workflow is the strict requirement for an approved spec before any code is written. This prevents immediate coding but eliminates ambiguity by dictating exactly when to escalate questions.
haposoftTransforms raw ideas into validated, spec-ready designs for software architecture.
dfrysingerRun acceptance tests against implemented code and present pass/fail results.
CaptainCrouton89Automate software tests to verify functionality against acceptance criteria.
opsMachineImplement approved specs directly without test-driven development.
