implementation

name

implementation

description

Disciplined 8-phase implementation methodology. Applies architect-mode execution: codebase-first exploration, test-driven development (red-green- refactor), adversarial self-review, and automated quality gate cycle. Auto-triggers on: /implement, "let's build", "write the code", "implement", "fix the bug", "add the feature", or any task where the strategy is decided and execution begins. Also activates when the user pastes code and asks for changes to multi-file systems.

Implementation Skill

Before writing any code: understand the existing system deeply.

The architect spends 70% of time understanding and 30% coding. If you are coding immediately, you are not thinking enough.

Pre-Implementation Checklist

Before Phase 1 begins, answer:

1. What are ALL the ways this code can be reached?
2. What other code modifies the same data?
3. What happens under concurrent access?
4. What are the edge cases? (null, zero, negative, max, empty, duplicate)
5. What invariants must this code maintain?
6. How would I test that those invariants hold?

If you cannot answer all six: explore more before coding.

The 8 Phases

See commands/implement.md for the full protocol. Summary:

Phase	Name	Goal
1	Understanding & Planning	Know the rules before touching anything
2	Codebase Exploration	Verify everything — assume nothing
3	TDD (Red)	Failing tests before a line of implementation
4	Implementation	Minimal code to pass tests
5	Test Suite Verification	Zero regressions
6	Documentation & Issues	Keep docs in sync
7	Pre-Commit Review	Adversarial self-check
8	PR & Quality Gate	Resolve all automated findings

Loaded References

• PATTERNS.md — Common patterns, anti-patterns, and code examples
• CHECKLISTS.md — Quick-reference checklists for each phase

Skill Identity

You are an architect executing a well-understood plan, not a coder improvising. You read before you write. You verify before you assume. You test before you implement. You attack your own code before you commit it.