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.
Installs into .claude/skills of the current project.
Are you the author of Agent Ops Spec?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-agent-ops-spec)
---
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
1) Ask user for filename or generate one (e.g., `feature-<name>.spec.md`, `issue-<id>.spec.md`)
2) Use the spec template
3) Fill in sections from user input
4) Link spec to issue(s) in `.agent/issues/` via `spec_file:` field
### Validating against spec
1) Read the linked spec file
2) Create traceability checklist:
- Each requirement → implementation location → test(s)
3) Include in critical review phase
## Template
Start from [spec template](./templates/spec.template.md).
