grounded-implement

Phase 4 — IMPLEMENT: Build to the Spec

Generate and write code governed by the specification and the test suite. Use AI tools for speed, but speed is directed by the spec, not by intuition.

Standards for every line shipped

• AI-generated code is reviewed against the spec before acceptance.
• All code passes the full test suite before delivery.
• Inline assertions enforce invariants at runtime.
• No code is delivered that the team cannot explain in plain English.
• Code is annotated with documentation tied to specific requirements.
• Review notes record key decisions and trade-offs.

Engineering quality bar

• Lint and run static analysis; keep complexity and duplication low.
• Validate all inputs; encode all outputs.
• Manage secrets via environment, never in code.
• Handle every failure mode named in the spec and architecture.
• Keep commits small, reviewable, and traceable to a requirement or test.

Mandatory cross-cutting reviews during build

• Load grounded-security-review on every engagement — run the checklist before Phase 5.
• Load grounded-ui-review if there is a user interface.
• Load grounded-ai-guardrails if there is an LLM, agent, RAG, or generative feature.

Gate C

Build is complete only when all tests pass, code is reviewed against the spec, security and data handling are reviewed, and every part is explainable. Then proceed to grounded-verify.