foundation-implementation-validation

name	foundation-implementation-validation
description	Foundational skill for no-code-until-validated workflow: packet decomposition, 3-role review gates, evidence capture, and GO/STOP control.

Foundation Implementation Validation

Use When

• Planning implementation from approved design packets.
• Running pre-code validation gates.
• Auditing readiness for coding tasks.

Outcomes

• Implementation readiness is decided via explicit GO/STOP evidence.
• Review roles and acceptance gates are consistent across tasks.
• Validation artifacts are preserved for auditability.

Required Rules

• Require explicit review outcomes from architecture, implementation, and validation perspectives.
• Any non-approval produces STOP status with remediation tasks.
• GO requires complete evidence links and reproduction/verification notes.
• Validation gate must reference pinned docs and current scope constraints.

Workflow

1. Assemble work packet with scope, assumptions, and risk statements.
2. Run architecture, implementation, and QA/docs review checks.
3. Record findings with file references and expected remediation.
4. Resolve blocking findings and rerun gate checks.
5. Emit final GO/STOP decision with evidence trail.

Validation

• Gate artifact includes reviewer outcomes and timestamped decision.
• STOP decisions include actionable remediation and owner.
• GO decisions include verification commands/steps for next phase.

Failure Modes

• Coding starts before unresolved STOP findings are cleared.
• Review criteria vary by contributor and produce inconsistent quality.
• Decisions are made verbally without durable evidence.

Local Doc Anchors

• godot-docs/tutorials/best_practices/introduction_best_practices.rst
• godot-docs/tutorials/editor/command_line_tutorial.rst
• godot-docs/tutorials/scripting/debug/overview_of_debugging_tools.rst