/hapo:specs#

/hapo:specs is the entry point for structured feature work.

Usage#

/hapo:specs Build a Google Meet transcript extension with AI summaries
/hapo:specs --validate meet-transcript-mvp

What It Produces#

specs/<feature-name>/
├── spec.json
├── requirements.md
├── research.md
├── design.md
└── tasks/
    └── task-R*.md

Responsibilities#

• create a coherent spec workspace
• define requirements and constraints
• define canonical contracts in design
• generate implementation-ready task files
• maintain task_files and task_registry

Validation Mode#

Use:

/hapo:specs --validate <feature-name>

Validation should catch:

• stale provider wording
• conflicting auth or transport contracts
• tasks that are missing evidence requirements
• mismatches between task files and spec.json

Do Not Use It For#

• tiny one-line fixes
• code changes that do not need a feature spec
• emergency hotfixes where a full spec would slow down the repair

Next Step#

Once the spec is validated and ready, move to /hapo:develop.