implementation-loop
implca が tasks を更新しながら実装→テスト→修正を回すための手順。
When & Why to Use This Skill
The implementation-loop skill is a structured Standard Operating Procedure (SOP) designed for Claude agents to manage the end-to-end software development lifecycle. It establishes a rigorous cycle of implementation, testing, and bug-fixing while maintaining real-time documentation. By enforcing task tracking in tasks.md and recording technical decisions in notes.md, it ensures high-quality code output, minimizes technical debt, and facilitates seamless handovers for human code reviews.
Use Cases
- Autonomous Feature Implementation: Streamlining the process of writing code, running tests, and fixing errors in a continuous loop until the feature is fully verified.
- Standardized Development Workflows: Establishing a consistent procedure for AI agents to follow, ensuring that every code change is accompanied by linting, testing, and documentation.
- Project State Persistence: Maintaining an up-to-date record of progress and hurdles in markdown files, allowing the agent to resume complex tasks without losing context.
- Enhanced Code Review Readiness: Automatically generating detailed implementation logs and 'Must-fix' lists that simplify the review process for senior developers.
- Technical Debt Prevention: Using the notes.md rule to capture compromises and remaining issues immediately during the implementation phase.
| name | implementation-loop |
|---|---|
| description | | |
目的
実装の進捗・検証結果・詰まりを docs// に残し、レビュー/引き継ぎを楽にする。
手順
docs/<work_item>/implementedplan.mdを読むdocs/<work_item>/tasks.mdを上から順に進める- 実装後は最小限の確認(lint/test/build)を回す
- 結果を tasks.md(必要なら notes.md)に短く残す
- review.md が来たら Must から順に潰す
記録ルール
- tasks.md: 完了した項目にチェックを付け、必要なら1行メモ
- notes.md: 判断が必要そうな点、妥協点、残課題だけを短く
実行コマンドの扱い
- 原則: lint/test/build/dev(非破壊)
- 実行したら「何を実行しどうだったか」を必ず残す