speckit-pro

Run an interactive, one-question-at-a-time design interview before SpecKit specification work and produce a Design Concept record. Use when an active user requests Grill Me—for example “grill me,” “interview me about,” “walk the design tree,” or “produce a Design Concept”—or invokes $speckit-pro:grill-me, or when interactive $speckit-pro:speckit-scaffold-spec delegates its required interview. SPEC setup, worktree creation, and workflow population belong to $speckit-pro:speckit-scaffold-spec; a setup request alone is not an interview delegation. SDD methodology, checklist selection, and gate guidance without a requested design interview belong to $speckit-pro:speckit-coach. Recommend one grounded answer first for every consequential choice. Not for autonomous, background, CI, autopilot, or subagent execution.

Install or refresh the bundled SpecKit Pro Codex custom subagents. Copies the plugin's TOML agent templates into $CODEX_HOME/agents/ (default ~/.codex/agents/), verifies the installed files, and tells the user to restart Codex so the new subagents load.

Archive a merged SpecKit spec, remove completed active specs, refresh roadmap and project-memory state, and prepare the cleanup PR after merge. Only for SpecKit spec archives after the implementation PR has merged. Do not use for generic git housekeeping such as pruning merged branches, deleting stale worktrees, git gc, or clearing build output, and not for scaffolding, autopilot, status, or PR review work.

Autonomous SpecKit workflow executor. Reads a populated workflow file and runs all 7 SDD phases (specify → clarify → plan → checklist → tasks → analyze → implement) with programmatic gate validation, multi-agent consensus resolution, and auto-commits. Use when the user says "run autopilot", "execute workflow", "autonomous speckit", "autonomous execution", "kick off autopilot", "start the autonomous pipeline", "drive it through all the SDD phases", "run the whole thing autonomously", "full end-to-end speckit run", or hands over a populated SPEC-NNN-workflow.md file for end-to-end execution. Requires SpecKit CLI installed, constitution created, and a populated workflow file. Not for SDD methodology questions ($speckit-pro:speckit-coach), pre-spec scoping ($speckit-pro:grill-me), new-spec setup ($speckit-pro:speckit-scaffold-spec), status checks ($speckit-pro:speckit-status), or PR comment resolution ($speckit-pro:speckit-resolve-pr).

Coach developers through Spec-Driven Development and SpecKit Pro. Use for SDD methodology, SpecKit command and gate guidance, technical-roadmap and workflow design, roadmap-MOC guidance, checklist selection, SpecKit project repair, selective formal-methods guidance and model/checker selection, SpecKit consensus protocol and voting rules, or SpecKit preset and extension discovery and configuration. Not for running autopilot, conducting grill-me, or unrelated coding (including MCP tool implementation). Formal-check execution and autopilot resume belong to speckit-autopilot.

Install the SpecKit CLI and initialize the current repository for one or both coding-agent integrations (Claude Code, Codex CLI). Use when the operator says: 'install speckit', 'set up speckit', 'initialize speckit in this repo', 'add speckit to this project', 'specify init for me', 'install spec-kit', '$speckit-pro:speckit-install', or has a repo with no .specify/ directory and wants to start using Spec-Driven Development. Detects existing installs and hands off to $speckit-pro:speckit-upgrade rather than overwriting. Safe to run on any repo. Not for upgrading an existing speckit install ($speckit-pro:speckit-upgrade), not for scaffolding a new spec on an already-installed repo ($speckit-pro:speckit-scaffold-spec), and not for installing this plugin's own bundled Codex subagents (use $speckit-pro:install for that).

Collaboratively create or update a lean PRD, its 1:1 technical-roadmap SPEC catalog, and a roadmap-MOC home note. Use when an active user asks to write a PRD, create a product requirements document, turn an idea or brief into a PRD and roadmap, plan a product, or invokes $speckit-pro:speckit-prd. Read-only workflow status and next-spec recommendations belong to $speckit-pro:speckit-status. Roadmap-only decomposition or dependency planning from an existing PRD, without creating or updating the PRD, belongs to $speckit-pro:speckit-coach. Ask one grounded decision at a time, then hand off the resulting roadmap to $speckit-pro:speckit-scaffold-spec. Not for per-spec scoping, worktree preparation, or general SDD coaching.

Address actionable review feedback on a pull request, push the fixes, and resolve review threads. Reads the PR comments, updates the code, runs project verification, replies to review threads, and reports what changed.

Use this skill when the user wants to set up, scaffold, bootstrap, prep, initialize, or prepare a SPEC-ID from the technical roadmap for autonomous execution. Triggers on: set up SPEC-XXX, scaffold SPEC-XXX, bootstrap SPEC-XXX for development, prep SPEC-XXX, initialize the workspace for SPEC-XXX, prepare SPEC-XXX for the autonomous run, create a spec branch and workflow for SPEC-XXX, generate the workflow file for SPEC-XXX, I need a workflow file generated for SPEC-XXX, fill the prompts from the roadmap, pre-fill the workflow template, start working on SPEC-XXX, populate the workflow file for SPEC-XXX. Opens with a blind-spot pass, creates the git worktree, spec branch, Design Concept doc, and populated workflow file, then hands off to planning. Accepts --answers-file for unattended setup; otherwise interviews the user. Not for checking roadmap status (use $speckit-pro:speckit-status), running a populated workflow (use $speckit-pro:speckit-autopilot), or SDD coaching (use $speckit-pro:speckit-coach).

Show the current SpecKit roadmap and workflow status in Codex. Aggregates workflow files and technical roadmaps, highlights active specs, identifies blocked work, and recommends the next unblocked spec to start. Read-only: never creates files, branches, or worktrees. Do not use to set up or scaffold a spec (speckit-scaffold-spec), run a workflow (speckit-autopilot), fix PR review comments (speckit-resolve-pr), or explain SDD methodology, the consensus protocol, or voting rules (speckit-coach).

Upgrade or migrate an existing SpecKit installation safely. Use when the operator asks to execute an upgrade or migration: 'upgrade speckit', 'update speckit', 'specify integration upgrade', 'speckit migration to skills', 'safely upgrade spec-kit', 'bump speckit version', '$speckit-pro:speckit-upgrade', or moving an existing .specify/ installation to the current spec-kit release. Preserves customizations (constitution.md, template overrides) via backup-and-restore. Supports upgrading one or both integrations (Claude Code, Codex CLI). Hands off to $speckit-pro:speckit-install when .specify/ is missing. Not for pre-upgrade project, template, or preset repair (use $speckit-pro:speckit-coach), installing speckit for the first time (use $speckit-pro:speckit-install), scaffolding a new spec ($speckit-pro:speckit-scaffold-spec), or installing this plugin's bundled Codex subagents ($speckit-pro:install).

Build or refresh the repository's ubiquitous-language terms document, a committed Markdown table of domain terms (term, meaning here, identifiers) that humans and agents read before designing. Use when the user asks to define domain terms, create or update a glossary or ubiquitous language, pin what a term means in this codebase, reconcile names between the spec and the code, or invokes $speckit-pro:ubiquitous-language. Also runs the advisory identifier lint on a diff. Not for scoping interviews, PRD authoring, or general SDD coaching.