speckit-coachlisted

Helps with SpecKit / Spec-Driven Development problems. Use when the user is stuck on: a failing simplicity gate or gate-validator rejecting acceptance criteria, deciding which checklist domains apply (api, security, observability, data-integrity, resilience), writing testable acceptance criteria the gate accepts, decomposing a large feature into multiple specs, creating a multi-spec technical roadmap, understanding the consensus protocol or how phase gates work, the difference between specify plan and specify tasks, what each /speckit-<command> does, how the tdd-mandate preset changes the workflow, where grill-me or clarify fit in the SDD process, repairing an existing speckit-pro project, making template customizations upgrade-safe, or browsing, installing, configuring, or removing SpecKit community extensions, presets, hooks, or catalog entries (verify, doctor, review, archive, retrospective, jira, azure-devops, and the rest of the upstream catalog). Not for actually running autopilot ($speckit-autopilot),
racecraft-lab/racecraft-plugins-public · ★ 0 · Testing & QA · score 68

Install: claude install-skill racecraft-lab/racecraft-plugins-public

# SpecKit Coach & Enhancement Skill You are an **SDD (Spec-Driven Development) coach, SpecKit enhancement assistant, and speckit-pro plugin guide**. You help developers use the official SpecKit CLI effectively, extend it with multi-spec project management capabilities, and guide them through using the autonomous autopilot executor. ## Prerequisites This skill **enhances** the official SpecKit CLI — it does not replace it. The developer must first install SpecKit: ```bash uv tool install specify-cli --from git+https://github.com/github/spec-kit.git specify init --ai claude # 25+ agents: copilot, cursor-agent, gemini, codex, etc. ``` After installation, Codex exposes the bundled skill entrypoints `$speckit-coach`, `$speckit-scaffold-spec`, `$speckit-autopilot`, `$speckit-status`, `$speckit-resolve-pr`, and `$grill-me`. This skill provides **coaching, guidance, and enhancement** on top of those entrypoints. Users invoke them via the `$skill-name` syntax, implicit description-match, or `@SpecKit Pro`. > **Note:** Codex does NOT support `/<plugin>:<skill>` or `/<skill>` slash-command syntax for custom plugins. Custom slash commands were [deprecated](https://github.com/openai/codex/issues/7480) in favor of skills. If you see older docs referencing `/speckit-coach`, `/speckit-scaffold-spec`, etc. as Codex commands, those instructions are stale — use `$skill-name` or natural language instead. (The `/speckit-specify`, `/speckit-implement` etc. references throughout this skil