Generate formal executable specifications from clear requirements via spec-kit.
npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill spec
Please help me install this Agent Skill. Skill: spec Source: https://github.com/rhuss/cc-superpowers-sdd/tree/main/skills/spec Command: npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill spec
This Skill allows you to directly create formal, executable specifications when you already have clear and detailed requirements, bypassing the brainstorming phase. It ensures your specs are sound, complete, and validated against project principles before any coding begins.
SKILL.md file.To create a spec for a new API endpoint, provide the details: Create a spec for a REST API endpoint to update user profiles. PUT /api/users/:id/profile
High-intent search queries and answers about installing and using this skill.
Formal specifications transform clear requirements directly into structured SKILL.md files with functional, technical, error handling, and success criteria sections. Provide detailed requirements or a PRD, and the spec generation process creates executable contracts that are validated against project principles before implementation begins.
Requirements must be clear, detailed, and well-defined—ideally from a PRD or user story. Include acceptance criteria, functional and non-functional needs, authentication requirements, API endpoints, data formats, and error scenarios. The more complete your input, the more thorough the generated specification.
Yes. After spec generation, constitution validation automatically checks the new specification against your project's defined principles and standards. This ensures soundness, completeness, and consistency before any development work begins.
Yes. Common use cases include REST API endpoints and microservices. Provide endpoint details like HTTP method, path, parameters, authentication type, request/response formats, and error handling requirements to generate formal, executable API specifications.
Spec-driven development starts with clear, formal specifications that lock down requirements upfront. This approach skips brainstorming when requirements are already well-defined. Exploratory design iterates through dialogue when requirements are ambiguous or evolving.
Yes. Soundness review ensures specifications are complete, unambiguous, implementable, and testable. This validation catches gaps and inconsistencies before coding, reducing rework and ensuring the spec satisfies all functional and technical requirements.
JochenYangGenerate structured PRDs and user stories with acceptance criteria.
BaSui01Capture implementation decisions into structured code-spec documents under .trellis/spec/.
MartyBonacciAutomate spec-driven feature workflows from specification to validated implementation.
ZaxbyHubTransform fuzzy project requirements into approved specifications through structured guided dialogue.