Skill: Pragmatism
"Perfect is the enemy of shipped."
The Standard
- Rules Are Guidelines: Know when to break them deliberately.
- Context Matters: Startup vs enterprise require different rigor.
- Shipping Wins: A working system beats a perfect design doc.
- Technical Debt Is A Tool: Borrow consciously, pay back deliberately.
The Check
Ask yourself:
- Am I gold-plating this feature?
- Is this abstraction solving a real problem or a hypothetical one?
- Would a simpler solution work for the next 6 months?
- Am I delaying shipping for theoretical purity?
The Protocol
- Make It Work: First priority is functioning code.
- Make It Right: Refactor when you understand the problem better.
- Make It Fast: Optimize only what you've measured.
- Document Shortcuts: Leave TODO with ticket number for known debt.
Real-World Examples
See examples.md.