Guide a 10-step process for developing evidence-based specifications with risk assessment.
npx skills add https://github.com/haposoft/cafekit --skill hapo-specs
Please help me install this Agent Skill. Skill: hapo:specs Source: https://github.com/haposoft/cafekit/tree/main/packages/spec/src/claude/skills/specs Command: npx skills add https://github.com/haposoft/cafekit --skill hapo-specs
This Skill addresses the challenge of turning ambiguous ideas into well-defined specifications that can guide implementation and verification.
Run the /hapo:specs <feature-description> command to initiate the specification process for a new feature.
High-intent search queries and answers about installing and using this skill.
To transform vague ideas into actionable software specifications, use a structured 10-step workflow that requires evidence-based analysis and risk assessment before proceeding. This gated process ensures ideas become well-defined specifications ready for implementation and verification.
An evidence-based specification workflow is a process that requires research and evidence validation at each phase before allowing progression to the next step. This approach prevents unverified assumptions from entering the final specification documentation.
Document requirements with risk assessment by following a gated specification framework that integrates technical constraints and user requirements. The framework provides a comprehensive structure for validating specifications against defined criteria during development.
Yes, you can resume an incomplete specification process through interactive state discovery. This feature allows you to select the appropriate phase to restart or continue the workflow based on your current project needs.
To start writing detailed project specifications, you need a thorough understanding of the project domain, technical constraints, and user requirements. Providing a feature description initiates the structured specification workflow.
Use a gated specification process instead of standard documentation when ambiguous ideas require rigorous validation and risk assessment before implementation. This ensures robust specifications by blocking progression until sufficient evidence is established.
xiaoweidotnetGenerate structured technical specification documents defining project scope, architecture, and success criteria.
OmexITVerify test outputs, build logs, and screenshots before shipping features.
CharGrnmnMark completed research milestones, archive documents, and tag them in version control.
BryceEWatsonCoordinate feature development through SPEC, PLAN, and REVIEW templates.
