psychology

chevp-ai-framework
Lifecycle Gates Guidelines Commands Agents Templates
looks_3 Step 3 of 3

Production

Build, verify, ship — nothing more, nothing less.

Execute the approved plan. No new plans, no scope changes.

build

Goal

Write production-ready code that follows the plan, validate it against spec and prototype, deliver cleanly.

schedule

When

After Exploration is complete (G2 passed). Plan/spec approved, prototype confirmed.

input

Inputs

Approved feature plan/spec, UX prototype, confirmed acceptance criteria.

Stable Plan Rule

If the approved plan has not changed since G2 — execute directly

Do not re-analyze goals, re-evaluate alternatives, or re-justify the approach during Production. That work happened in Exploration and was already approved.

If implementation reveals the plan is incomplete, or a constraint makes the approach unviable, the AI must fall back to Exploration — not silently patch the plan or improvise.

Activities

In order — each step is gated by a build / validation / approval

  1. Produce Production-Plan (PRD) referencing the approved G2 plan
  2. Obtain human approval of Production-Plan before writing code
  3. Step-by-step implementation according to plan
  4. Build verification after each step
  5. Visual validation against prototype (where applicable)
  6. Spec comparison: all acceptance criteria checked
  7. Tests executed
  8. Commit with meaningful message
  9. Documentation updated

The 6 Decisions Toward G3

Each surfaced via AskUserQuestion

  1. Approve start of PRD execution against the approved plan
  2. Approve any scope change or fallback to Exploration when triggered
  3. Approve commits / PR at boundary points (not every file)
  4. Confirm acceptance criteria fulfilled (each criterion: pass / fail)
  5. Confirm insights.md updated with implementation surprises
  6. Pass G3 → Done (approve / reject / revise)

Quality Gate G3

Production is complete when G3 is fully passed

check_circleProduction-Plan exists and was approved by human before implementation
check_circleCode compiles / build successful
check_circleOnly changes specified in the plan — no scope expansion
check_circleExisting patterns followed
check_circleNo over-engineering, no extra features
check_circleAll acceptance criteria from spec fulfilled
check_circleVisual result matches prototype (if applicable)
check_circleNo regressions
check_circleTests pass (if test suite exists)
check_circlePlans moved to finished/ (PRD + EXP)
check_circleDocumentation up to date (CLAUDE.md, ADRs)
check_circleinsights.md updated with implementation surprises
check_circleNo open TODOs
check_circleGatekeeper-G3 verdict recorded
check_circleHuman has given final approval

Roles Active in This Step

Six roles operate in Production

SDLC

Implementation, validation, delivery rules.

AI-Plans

Plan execution tracking, finalization.

UX-Tooling

Visual validation, preview comparison.

DevOps

Build verification, commit workflow, CI.

Software-Architecture

Pattern enforcement, anti-patterns.

Context-Engineering

Post-delivery: update CLAUDE.md, docs.

arrow_back Step 2: Exploration Lifecycle overview arrow_forward
menu_book

Read the source

03-production/README.md open_in_new