Interactive workflow for adding a new agent CLI vendor to the SpecRoute supported matrix. Walks through scaffolding the runtime layout, adding the vendor's row to the matrix table, creating the per-vendor rule file, wiring MCP rendering (if applicable), and updating cross-vendor sync. Use when proposing or…
Convene the relevant SpecRoute implementation agents to plan, collaborate, implement, and review a piece of work end-to-end. Engages only the specialists the work actually touches, runs autonomously through planning into implementation and review, and accepts free-text work or a path to a PRD / spec / issue file.…
Audit SpecRoute's documentation for staleness against reality - vendor facts, version anchors, dates written in the wrong tense, counts that no longer match disk, and claims mirrored inconsistently across the four vendor-matrix copies. Use before a release, after any vendor ships a breaking change, or on a scheduled…
Guided end-to-end build of the canonical worked example under examples/sample-project/. Walks through each artifact in spec-driven order (PRD → requirements → design → tasks → agent roster → phased prompts → implementation plan), invoking the right specialist agent for each. Use when bootstrapping the worked example…
Validates YAML frontmatter across SpecRoute artifacts (agents, skills, commands) against the per-artifact contract. Reports missing required fields, malformed YAML, and drift between similar artifacts. Use proactively before commits, when reviewing PRs, or when an agent/skill/command isn't loading correctly.
Interactive scaffolding for any SpecRoute artifact (PRD, spec, agent, skill, command, hook, prompt, runtime layout). Asks for artifact type and vendor (where applicable), copies the canonical template, generates the directory structure, and pre-fills the frontmatter. Use when starting a new artifact under prds/…
This directory contains the 12 Claude Code agents that implement the SpecRoute skeleton. They are project-internal - they build SpecRoute itself, not consumer-facing templates that ship as artifacts.
Use when checking whether SpecRoute's claims about the outside world are still true - vendor config surfaces, hook event taxonomies, frontmatter contracts, version anchors, transition dates, and counts that must match disk. Owns the currency cycle, not the prose. Runs before releases, after any vendor ships a breaking…
Use when drafting or revising framework documentation under agentic-docs/. Owns philosophy.md, spec-driven-development.md, agentic-coding-model.md, automation-decision-framework.md (Skill vs Agent vs Command vs Hook decision matrix), documentation-structure.md, two-tier-docs-pattern.md, multi-vendor-context-files.md…
Use when drafting or reviewing hooks under hooks/. Owns the per-vendor starter templates and scripts, including Claude's 3-event starter and Kiro v1 JSON with 10 triggers. Documents each vendor's native taxonomy and blocking contract. Triggers - "draft the hooks.json template", "add a Kiro file-pattern hook", "what…
Use when drafting, reviewing, or extending PRD content under prds/. Owns the full 23-section enterprise PRD template, the lightweight PRD template, the platform-SRS template, the PRD lifecycle directories (active/deprecated/archive), and example PRDs. Triggers - "draft a PRD template", "fill out prd-template.md"…
Use when drafting or reviewing prompts under prompts/. Owns the master/phase/task prompt template trio in prompts/shared/ (global-master-prompt-template.md, phase-master-prompt-template.md, task-prompt-template.md), per-vendor prompts in prompts/codex/ and prompts/claude/, and shared prompts (prd-to-spec…
Use when building or updating runtime layouts under runtimes/, the MCP single-source-of-truth, or cross-vendor sync utilities under tools/. Owns the six copy-pasteable layouts at runtimes/.claude/, runtimes/.codex/, runtimes/.gemini/, runtimes/.kiro/, runtimes/.cursor/, and runtimes/.devin/, plus runtimes/mcp/…
Use when designing or extending skills under skills/. Owns the folder-per-skill convention with SKILL.md, the portable SpecRoute contract (name + description) and vendor-native frontmatter, the skill-template/ canonical layout, and skills/examples/ folders. Ensures skills are interactive parameterized workflows with a…
Use when drafting or reviewing spec content under specs/. Owns the spec triplet (requirements-template.md + design-template.md + tasks-template.md), the lightweight feature-spec-template.md, the technical-spec-template.md, and architecture-decision-record.md. Ensures requirement IDs are stable and tasks back-reference…
Use when reviewing templates for the "production-grade and immediately usable" criterion. Rejects abstract checklists, theory-only docs, and templates that don't produce valid artifacts when filled in. Verifies frontmatter contracts (skills, agents, commands), checks that examples exist alongside templates, ensures…