quality-gates

User Input

You MUST consider the user input before proceeding (if not empty).

Output

Reports and checkpoints are written under your task's Artifact path: (from task metadata).

checklists/requirements.md           ← spec-quality gate
checkpoints/spec-to-plan.yaml        ← spec-to-plan gate
traceability-matrix.yaml             ← completeness gate
migration-summary.md                 ← completeness gate

Input

type = spec-quality | spec-to-plan | plan-to-tasks | completeness

Workflow

Step 1: Load Context

Load from cwd:

• constitution.md — non-negotiable; violations are always CRITICAL
• spec.md, plan.md, tasks.md, checkpoints/ (as relevant for the gate type)

Step 2: Gate Routing

Load the checklist reference for the selected gate:

Step 3: Execute Gate

Follow the process defined in the referenced gate file.

Step 4: Verdict

• PASS: all checklist items pass → ✓ [gate] PASSED.
• FAIL: any CRITICAL → ✗ [gate] FAILED. N critical issues. + remediation steps

Rules

• READ-ONLY: never modify source code; only write checklists, checkpoints, reports.
• Max 50 findings per gate.
• Deterministic: rerunning without changes = same results.
• Never hallucinate: if artifact is missing, report it.

Severity

Resources

• references/gate-spec-quality.md — spec quality checklist and process
• references/gate-spec-to-plan.md — spec-to-plan checklist and process
• references/gate-plan-to-tasks.md — plan-to-tasks checklist and process
• references/gate-completeness.md — completeness checklist and process (includes plan coverage)
• templates/report-template.md — migration summary structure