A specification gap is missing or incomplete intent that lets implementation diverge from what was intended. A direct code fix may solve the immediate problem while leaving the durable specification inaccurate. section 3.7
Trace the gap to where intent was lost, then repair that part of the workflow:
- Surfacing: ask better questions. Capture: use richer formats. Construction: add stronger constraints. Verification: provide deterministic evidence. section 3.7
- Correct the specification first; if gaps recur, improve the workflow that allowed intent to escape. section 3.7
- Move recurring guidance into standing context, skills, hooks, checks, or project-level constraints rather than repeating it in every feature specification. section 3.7
A direct fix that leaves a gap
A code change resolves an immediate problem, but the intent survives only in code, prompts, review comments, or memory. Update the specification so it can guide future work. section 3.7
