implementation

name	implementation
description	Use when implementing features, fixing bugs, refactoring, updating tests/docs/config, or making any non-trivial repository change.

Implementation Skill

Use this skill for repository changes. Aim for small, correct, reviewable diffs with honest validation.

Workflow

1. Orient:

   • Read local instructions, README.md, CONTRIBUTING.md if present, and relevant docs.
   • Identify language, package manager, build/test/lint/format commands, conventions, relevant files, and risks.
   • Find the narrowest useful validation command.

2. Plan:

   • For non-trivial work, create or update plan.md.
   • If planning files are not ignored, add plan* to .gitignore.
   • Keep the plan concise: goal, constraints, current state, phases, acceptance criteria, test plan, completion notes, deviations.

3. Implement:

   • Make the smallest useful change.
   • Prefer existing patterns and standard library/local helpers.
   • Preserve public behavior unless the task changes it.
   • Avoid broad rewrites, unrelated formatting, placeholder code, hidden network behavior, silent fallbacks, and new dependencies without justification.

4. Validate:

   • Run targeted checks first, then integration, lint/format, and full suite when practical.
   • Add focused tests when reasonable.
   • Record exact commands and results.
   • If checks cannot run, state the blocker and residual risk.

5. Close out:

   • Update user-facing docs only when behavior, commands, config, APIs, or important errors changed.
   • Remove temporary code.
   • Review the diff for unrelated changes.
   • Report changed files, behavior, tests, and risks.

Quality Rules

• Errors should state what failed, where, and what to do next.
• Refactor only when it directly supports the task, isolates risk, enables testing, or reduces blocking duplication.
• Do not claim success beyond what was actually inspected or tested.