implementation-runner
Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.
When & Why to Use This Skill
The Implementation Runner is a specialized Claude skill designed to streamline the software development lifecycle by executing code changes and tracking implementation progress. It automates the transition from technical design to actual code modification, ensuring that all changes are recorded in the analysis context and completion states are accurately tracked for agentic workflows.
Use Cases
- Automating the application of code changes based on user requirements and predefined technical decisions within a repository.
- Tracking file modifications and implementation status in complex, multi-step coding tasks to maintain context across an agentic chain.
- Serving as the execution engine for AI software engineers to handle feature development, refactoring, or bug fixes while maintaining a record of changed files.
| name | implementation-runner |
|---|---|
| description | Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation. |
Implementation Runner
Inputs
analysisContext.request.userMessageanalysisContext.decisions.skillChainanalysisContext.repo.openFilesanalysisContext.artifacts.contextDocPath(if present)
Procedure
- Check requirements and context.
- Define change scope and implement.
- Record changed files and key change summary.
- Update implementation completion in
analysisContext.
Output (patch)
signals.implementationComplete: true
repo.changedFiles:
- src/...
notes:
- "implementation: complete, changed_files=3"
Rules
- Do not call other skills/subagents.
- If failed or deferred, record the reason in
notes.