Menu
Start spec-driven development — write a structured specification before writing code
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Use when an AI tool gains support for a feature agentsmesh does not yet expose — or exposes wrongly — and you must raise or correct an existing target's capability for project and/or global scope (rules, additionalRules, commands, agents, skills, mcp, hooks, ignore, permissions). Also use to audit every target for capability gaps, or to act on an audit/feature-request someone else wrote. Start by verifying the claim against the tool's OWN primary docs — such findings are frequently fabricated, stale, or wrong-scoped, so be ready to reject. Covers verification-first research, descriptor wiring, round-trip symmetry, global-only scopeExtras emission, settings-merge and plugin safety, format/path-change blast radius, strict TDD, two-stage review, and matrix/docs sync. Start with `pnpm capabilities:audit`; research only STALE/MISSING cells; the ledger memoizes verified formats so audits stay fast.
Use when an AI tool gains support for a feature agentsmesh does not yet expose — or exposes wrongly — and you must raise or correct an existing target's capability for project and/or global scope (rules, additionalRules, commands, agents, skills, mcp, hooks, ignore, permissions). Also use to audit every target for capability gaps, or to act on an audit/feature-request someone else wrote. Start by verifying the claim against the tool's OWN primary docs — such findings are frequently fabricated, stale, or wrong-scoped, so be ready to reject. Covers verification-first research, descriptor wiring, round-trip symmetry, global-only scopeExtras emission, settings-merge and plugin safety, format/path-change blast radius, strict TDD, two-stage review, and matrix/docs sync. Start with `pnpm capabilities:audit`; research only STALE/MISSING cells; the ledger memoizes verified formats so audits stay fast.
Use when about to edit a file or run a state-changing command, or after any failure, correction, or surprising result.
Use when about to edit a file or run a state-changing command, or after any failure, correction, or surprising result.
Use when about to edit a file or run a state-changing command, or after any failure, correction, or surprising result.
A relentless interview to sharpen a plan or design.
Based on SOC occupation classification
| name | am-command-spec |
| description | Start spec-driven development — write a structured specification before writing code |
| x-agentsmesh-kind | command |
| x-agentsmesh-name | spec |
Invoke the agent-skills:spec-driven-development skill.
Begin by understanding what the user wants to build. Ask clarifying questions about:
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
