Coding standards, frameworks, refactoring, and code review (16K skills)
Resume a GSD project by reading its recorded state and automatically running the next workflow step. Before advancing, it checks earlier phases for unfinished work and verification failures, then offers ways to handle any gaps.
Start the next milestone in an existing project by clarifying goals, optionally researching new features, and defining requirements and a roadmap. Update planning documents while preserving project history and continuing the existing phase numbering.
Create a developer preference profile from past sessions or a questionnaire. The skill produces files Claude can discover to tailor its responses, and can refresh an existing profile while backing it up and showing changes.
Analyze an existing codebase with four parallel agents and produce seven structured documents covering technologies, integrations, architecture, file organization, conventions, tests, and concerns. Use the resulting map to understand unfamiliar projects or prepare for refactoring.
Create a pull request branch from the current branch while filtering out commits for `.planning/`. Keep planning and progress documents out of the review so reviewers can focus on code changes, with `main` as the default target branch.
Review open GitHub issues and pull requests against project templates and contribution guidelines. Get a report of missing information and compliance problems, with options to apply labels or close incomplete submissions with explanatory comments.
Create a separate GSD workspace containing selected Git repositories and its own planning directory. Choose worktrees, lightweight working copies, or fully independent clones, then use the generated workspace manifest to organize an isolated development session.
Plan a phase for an MVP, a minimum viable product, by clarifying who needs what and why. Check whether the user story should be split, record it in the roadmap, and hand it to detailed planning.
Turn a roadmap phase into executable PLAN.md files through research, planning, and repeated checks. Use requirements documents, verification gaps, or review feedback to shape the plan, then receive a continuation command for phase execution.
Check the integrity of a project's planning directory and receive actionable reports on missing files, invalid settings, inconsistent state, and orphaned plans. An optional repair flag passes repair requests to the underlying workflow.
Fix issues recorded in a phase’s REVIEW.md, commit each fix separately, and produce a summary. Choose which severity levels to include, or repeat fixes and reviews for up to three iterations.
Find GSD workspaces saved on your computer and display a summary table showing each workspace’s name, path, repository count, strategy, and project status, making multiple working environments easier to review.
Close a completed project milestone by checking phase summaries, collecting accomplishments and change statistics, and archiving its roadmap and requirements. Update project records and create a Git tag to mark the shipped version.
Investigate failed or stalled GSD workflows using Git history, planning files, and the current project state. Produces a saved diagnostic report with evidence for detected anomalies and recommendations for corrective action.
Convert a GSD-2 project back to GSD v1 format while preserving completion status, research files, and summaries. Preview the files and migration statistics before confirming the conversion, with the original project directory left intact.
Turn a project idea into documented context, scoped requirements, and a phased roadmap. The skill gathers details through questions, optionally researches the domain, and creates planning files that support the next stage of work.
Handle tiny development tasks directly in the current conversation, such as fixing typos, changing settings, or making small code edits. It skips delegated agents and planning files for work that takes under two minutes.
Review Claude's assumptions before planning a development phase. The skill explains the proposed technical approach, implementation order, scope, risks, and dependencies so users can correct misunderstandings and decide how to proceed.
Search structured information about a codebase’s architecture, APIs, dependencies, and file roles. Check how current the records are, inspect changes since the last snapshot, or rebuild the information by analyzing the codebase.
Execute a development phase by grouping plans into waves based on dependencies and assigning them to subagents. Collect results and handle checkpoints, with options to run one wave, focus on fixes, or work sequentially with user input.
Explore development ideas through probing questions before turning them into plans. The skill can initiate research when needed and route the results into GSD notes, tasks, research questions, requirements, or new phases.
Investigate bugs through symptom gathering, hypotheses, and testing, with session state saved to files so work can resume after context resets. Choose diagnosis alone for a root cause report, or continue through fixing the issue.
Review code changed during a development phase for bugs, security vulnerabilities, and quality issues. Choose the analysis depth or specific files, then receive a report with findings grouped by severity and an inline summary.
Build a project knowledge graph, a map of information and its relationships. Search by term, inspect relationship confidence, check freshness and statistics, and compare builds, with JSON, HTML, and Markdown reports saved for inspection.