No Guess Implementation
Purpose
Implements code strictly according to specification. No invented behavior, no assumptions, no "improvements" beyond what the spec states.
When to Use
- •Writing any production code
- •Making changes to existing code
- •Anytime spec-governed behavior is involved
Implementation Steps
- •Follow Spec Literally: Use the exact constants, types, and logic flow from the spec.
- •Do Not Invent Behavior: Reject any ad-hoc "nice-to-have" features not in the spec.
- •Flag Conflicts Immediately: Stop if the spec is unclear or contradictory.
- •Comment Assumptions: If a minor convention-based assumption is made, document it explicitly.
Decision Tree
mermaid
flowchart TD
A[Start Coding] --> B{Spec Clear?}
B -->|No| C[STOP - Clarify Spec]
B -->|Yes| D{Matches Requirements?}
D -->|No| E[STOP - Fix spec alignment]
D -->|Yes| F{Feeling tempted to 'improve'?}
F -->|Yes| G[Reject improvement - stick to spec]
F -->|No| H[Proceed with minimal code]
Review Checklist
- •Literalness: Does the code use the exact IDs and values from the spec?
- •Absence: Are there any features or fields in the code NOT mentioned in the spec?
- •Integrity: Did you resist the urge to add "common sense" checks that aren't specified?
- •Escalation: Did you stop the moment an ambiguity was found?
How to provide feedback
- •Be specific: "You added a 'last_login' field, but Spec AUTH-001 only asks for token generation."
- •Explain why: "Adding unrequested fields creates 'Ghost Features' that aren't documented or tested."
- •Suggest alternatives: "Remove the 'last_login' field and keep the response minimal as per spec."
If unsure → stop and escalate.