Create a new specification with guided wizard
Guides creation of new OAPS specifications through a structured wizard process.
/plugin marketplace add tbhb/oaps/plugin install oaps@oapsOptional spec title or topicspec/You are helping a developer create a new OAPS specification using a guided wizard. This command coordinates spec-architect, spec-writer, and spec-reviewer agents to produce a well-structured specification.
Initial topic: $ARGUMENTS
Goal: Understand what specification needs to be created
oaps skill context spec-writing --references spec-structure formattingGoal: Design specification structure before writing content
Launch spec-architect agent to design structure:
Design a specification structure for: [topic description]
Consider:
1. Appropriate scope and boundaries
2. Document hierarchy (index.md + supplementary docs if needed)
3. Requirement categories (FR, QR, SR, etc.)
4. Test coverage strategy
5. Dependencies on existing specs
Based on existing patterns in .oaps/docs/specs/
Present proposed structure to user:
Ask user for approval or refinements using AskUserQuestion
Goal: Create the specification directory and initial content
Determine next spec ID: Check .oaps/docs/specs/index.json for highest ID and increment
Run CLI to create spec directory structure:
oaps spec create --title "Spec Title" --slug "spec-slug"
Or manually create:
.oaps/docs/specs/NNNN-slug/Launch spec-writer agent to create initial content:
Create initial specification content based on this approved structure:
[Include: topic, approved structure from architect, user preferences]
Create:
1. index.md with overview, scope, and initial sections
2. index.json with metadata (title, status: draft, version: 0.1.0)
3. requirements.json with initial requirements (follow RFC 2119)
4. tests.json with placeholder tests linked to requirements
5. history.jsonl with creation entry
Present created files to user
Goal: Validate the new specification
Launch spec-reviewer agent:
Review the newly created specification: [spec ID]
Check for:
- Required files present
- JSON schema compliance
- Valid frontmatter in markdown
- Requirement format and RFC 2119 compliance
- Test-requirement bidirectional links
- Cross-reference validity (if any)
Present review findings to user
If issues found, fix them directly or launch spec-writer to address
Goal: Document what was created
Mark all todos complete
Summarize:
Show commands for further work:
/spec:info NNNN # View spec details
/spec:review NNNN # Review spec quality
oaps spec show NNNN # CLI info