2.0 KiB
2.0 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| spec-manager | Manage specification files for spec-driven development. Use when creating, updating, or deleting spec files. Supports feat, fix, docs, refactor, and chore scopes. | Read, Write, Glob, Grep, Bash, AskUserQuestion |
Spec Manager
Manages specification files in specs/{scope}/{work-name}.md for spec-driven development workflow.
Principles
- One spec = one task (unless frontend + backend work together)
- No "before" sections - Focus only on the final desired state
- XML tag format - Use XML tags for structure (varies by scope)
- Minimal code examples - Avoid code in specs; if necessary, keep it brief and illustrative
- Check for duplicates - Always verify if similar specs exist before creating
Operations
Create
- Analyze request and infer scope (feat/fix/docs/refactor/chore)
- Search
specs/{scope}/for similar existing specs - If found, ask: "Create new", "Update existing", or "Cancel"
- If ambiguous scope, ask user to confirm
- Generate filename (lowercase-with-hyphens)
- Use appropriate template based on scope
- Fill in XML tags based on user request
Update
- List existing specs in relevant scope
- Let user select which to update
- Verify update aligns with original purpose
- If purpose changed significantly, suggest new spec
- Apply changes while maintaining XML structure
Delete
- List all specs organized by scope
- Let user select spec(s) to delete
- Confirm and remove
List
Display all specs organized by scope directory structure.
Templates
See templates directory for scope-specific XML tag structures:
feat→ templates/feat-template.mdfix→ templates/fix-template.mddocs→ templates/docs-template.mdrefactor→ templates/refactor-template.mdchore→ templates/chore-template.md
Each template uses different XML tags appropriate to its scope.