개발 스킬

Archive phase directories left behind by completed project milestones. Identify eligible folders, preview the proposed changes, and move them into versioned milestone archives after confirmation, helping organize accumulated planning directories.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organize phase folders from completed milestones
• Review which folders will be archived
• Move past phases into versioned milestone archives

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a map of project information and relationships
• Search for terms and inspect related information
• Check graph freshness and statistics

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning the next release of an existing project
• Defining requirements for a new feature milestone
• Updating a roadmap while continuing phase numbering

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing active GSD workspaces
• Finding workspace locations
• Checking repository counts and strategies

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Get familiar with an unfamiliar codebase
• Document an existing project before planning development
• Review the current structure before major refactoring

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating a stalled GSD workflow
• Checking missing artifacts or abandoned work
• Reviewing the effects of a crash or interruption

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Documenting development preferences from past sessions
• Building a profile using only a questionnaire
• Creating preference files for Claude

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Searching recorded information about a codebase
• Checking whether architecture records are outdated
• Reviewing changes since the previous snapshot

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate a bug from its symptoms and reproduction steps
• Resume an interrupted debugging session
• Review hypotheses and evidence from active sessions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create a detailed plan for a roadmap phase
• Build a plan from a requirements document
• Plan work to close verification gaps

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code changes at the end of a development phase
• Check specific files for bugs and security issues
• Analyze dependencies and calls across multiple files

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Returning a GSD-2 project to GSD v1
• Previewing files before migration
• Preserving completed work and research during conversion

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Define the user story for an MVP phase
• Check whether a large feature request needs splitting
• Record the agreed scope in the roadmap

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Execute all plans in a development phase
• Run a single wave to manage usage
• Execute only plans that close verification gaps

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Archive the roadmap and requirements for a shipped version
• Summarize accomplishments and development statistics
• Update project records when closing a milestone

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare a branch for code review
• Exclude planning commits from a pull request
• Keep code changes separate from progress records

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review technical assumptions before planning
• Check implementation order and dependencies
• Clarify scope boundaries and risks

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare an isolated workspace for several repositories
• Work on a feature branch with separate planning files
• Choose fully independent clones for a workspace

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Exploring an idea before committing to a plan
• Thinking through an authentication strategy
• Identifying questions that need research

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying a new project idea
• Defining requirements and scope
• Creating a phased project roadmap

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fixing a typo in a file
• Making a small configuration change
• Applying a minor refactor

Clarify implementation choices before planning through focused questions, existing project context, and codebase exploration. Record decisions in a context file that guides subsequent research and planning, with options for automatic defaults or answering questions in a file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Clarifying unresolved choices before planning
• Carrying earlier decisions into the next phase
• Recording decisions for research and planning

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing open issues for missing information
• Checking pull requests against contribution guidelines
• Applying labels based on submission type

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fix critical issues and warnings from a code review
• Include informational findings in the fixes
• Repeat fixes and reviews up to three times