| name | agent-ops-spec |
| description | Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation. |
| category | core |
| invokes | ["agent-ops-state","agent-ops-interview"] |
| invoked_by | ["agent-ops-planning","agent-ops-critical-review"] |
| state_files | {"read":["focus.md","issues/*.md"],"write":["focus.md","issues/*.md","specs/*.md"]} |
Spec Management workflow
Purpose
Capture, organize, and trace specifications/requirements so the agent can validate implementation against them.
Location
All specs live in .agent/specs/ with user-specified or auto-generated filenames.
Procedure
Creating a spec
- Ask user for filename or generate one (e.g.,
feature-<name>.spec.md, issue-<id>.spec.md)
- Use the spec template
- Fill in sections from user input
- Link spec to issue(s) in
.agent/issues/ via spec_file: field
Validating against spec
- Read the linked spec file
- Create traceability checklist:
- Each requirement → implementation location → test(s)
- Include in critical review phase
Template
Start from spec template.