Implementation Prompt
# Implementation Prompt - PDCA Do Phase
Use this prompt to execute the plan following strict TDD discipline.
## Working Agreements (Quick Reference)
**Core Principles:**
- ✅ **Test-First**: Failing tests before production code (behavioral failures, not compilation errors)
- ✅ **Small Commits**: <100 lines, <5 files, one logical change
- ✅ **Follow Patterns**: Search and reuse existing abstractions
- ✅ **You Own It**: Review AI reasoning, intervene early, commit only what you understand
**Key Interventions:** "Where's the failing test first?" • "Is this commit too large?" • "Does this follow our patterns?" • "Are we staying on plan?"
## When to Use
- After the plan is approved and ready to implement
- At the start of the Do phase of PDCA cycle
## Implementation Promptwhen to use it
Community prompt sourced from the open-source GitHub repo MarcherGA/pdca-ai-coding-skill (NOASSERTION). A "Implementation Prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
MarcherGA/pdca-ai-coding-skill · NOASSERTION
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions