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.
Scanned 2/12/2026
Install to Claude Code
Skills Directorynpx -y skills add majiayu000/claude-skill-registry --skill agent-ops-spec --agent claude-codeInstalls 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 automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-agent-ops-spec)More formats (shields.io, HTML) on the badges page.
---
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).
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer raised npm security.
