Claude Skills by buildomator

Archive completed milestone and prepare for next version

Systematic debugging with persistent state across context resets

Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

Route freeform text to the right GSD command automatically

Generate or update project documentation verified against the codebase

Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan

Execute all plans in a phase with wave-based parallelization

Socratic ideation and idea routing — think through ideas before committing to plans

Extract decisions, lessons, patterns, and surprises from completed phase artifacts

Execute a trivial task inline — no subagents, no planning overhead

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format

Build, query, and inspect the project knowledge graph in .planning/graphs/

Diagnose planning directory health and optionally repair issues

Show available GSD commands and usage guide

Ingest external plans with conflict detection against project decisions before writing anything.

Triage and review all open GitHub issues and PRs against project templates and contribution guidelines

Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.

Insert urgent work as decimal phase (e.g., 72.1) between existing phases

Query, inspect, or refresh codebase intelligence files in .planning/intel/

Join the GSD Discord community

Surface Claude's assumptions about a phase approach before planning

List active GSD workspaces and their status

Interactive command center for managing multiple phases from one terminal

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

Plan an MVP-mode phase — captures an "As a / I want to / So that" user story, runs SPIDR splitting, then delegates to plan-phase

Initialize a new project using Documentation-Driven Development. Research, then write user-facing docs (SPEC.md) as the spec, then user validates docs, then phases derive from doc sections. Best for CLIs, libraries, SDKs, APIs, plugin systems, anything with a well-defined user-facing surface.

Start a new milestone cycle — update PROJECT.md and route to requirements

Initialize a new project with deep context gathering and PROJECT.md

Create an isolated workspace with repo copies and independent .planning/

Automatically advance to the next logical step in the GSD workflow

Zero-friction idea capture. Append, list, or promote notes to todos.

Create context handoff when pausing work mid-phase

Create phases to close all gaps identified by milestone audit

Create detailed phase plan (PLAN.md) with verification loop

Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone

Create a clean PR branch by filtering out .planning/ commits — ready for code review

Generate developer behavioral profile and create Claude-discoverable artifacts

Check project progress, show context, and route to next action (execute or plan). Use --forensic to append a 6-check integrity audit after the standard report.

Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents

Reapply local modifications after a GSD update

Capture or review how this project connects to external systems (GitHub, AWS, npm, SSH, etc.) so future sessions know the auth recipe. Auto-detection hook logs candidate captures to an inbox; this skill promotes them to permanent recipes in `.planning/AUTH-RECIPES.md` and optionally to user-global memory at `~/.claude/auth-recipes/`.

Remove a future phase from roadmap and renumber subsequent phases

Remove a GSD workspace and clean up worktrees

Research how to implement a phase (standalone - usually use /gsd:plan-phase instead)

Schedule a future resume of work - e.g. '/gsd:resume-at 09:00', '/gsd:resume-at +2h', or '/gsd:resume-at 04:00 --cmd /gsd:execute-phase 9'

Resume work from previous session with full context restoration

Review and promote backlog items to active milestone

Request cross-AI peer review of phase plans from external AI CLIs