implementation

Executes approved implementation plans through branch creation, TDD cycles, review, and PR creation.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill implementation-ryoma99
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/RyoMa99/chezmoi_dotfiles/tree/main/dot_claude/skills/implementation
Command: npx skills add https://github.com/RyoMa99/chezmoi_dotfiles --skill implementation-ryoma99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved plan into merged code involves many error-prone steps: creating branches, committing plan files, running TDD per task, reviewing changes, verifying with typecheck/lint/test, and opening a PR. This Skill orchestrates that entire implementation workflow so nothing is skipped. ## Core Features & Use Cases - Structured Implementation Flow: Creates a working branch with naming conventions (feature/, fix/, refactor/, chore/), commits the plan file to docs/plan/, and optionally writes ADRs decided during planning. - Task-Level TDD Execution: Runs each planned task through a TDD cycle in dependency order, handles Spike tasks as time-boxed investigation, and confirms with the user after each task. - Review and Verification Pipeline: Runs /review and /simplify passes, then validates with typecheck, lint, and tests before committing, pushing, and creating a PR with the plan embedded in the description. - Use Case: After approving a plan in Plan mode for a new user-auth feature, invoke this Skill to create the feature/user-auth branch, implement each task with TDD, review the diff, and open a PR containing the full plan summary. ## Quick Start Ask the AI to execute the approved implementation plan using the implementation workflow, starting with branch creation and ending with a pull request.

Frequently Asked Questions about implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement an approved plan step by step with git?▼

Create a working branch from the latest default branch, commit the plan file to docs/plan/, then implement each task in dependency order using TDD. Finish with review, typecheck, lint, and test before committing and opening a PR.

What branch naming convention should I use for new features?▼

Use a prefix matching the work type followed by a kebab-case slug: feature/ for new functionality, fix/ for bug fixes, refactor/ for restructuring, and chore/ for CI or dependency updates. Example: feature/user-auth.

Should spike or research tasks use TDD?▼

No. Spike tasks are time-boxed investigations whose output is decision material, not production code, so TDD does not apply. Report the findings to the user and assess the impact on subsequent tasks instead.

When should the plan file be deleted from the repository?▼

Delete docs/plan/ only after the PR is created, since the plan content is merged into the PR description and the file remains in git history. If no PR is created, keep the file for later sessions.

What happens if the review step finds critical issues?▼

Critical findings are reported to the user and fixed before proceeding. The workflow does not advance to the simplify pass until Critical and Major issues are resolved, and verification reruns afterward.