iic-checklist-generator {Metacognition} (v1.0)

"A checklist is a contract between phases. Pass all or don't advance."

Purpose

Generates phase-specific QA validation checklists. Each item is linked to spec IDs (FR-XXX, US-X) and has binary pass/fail status. [EXPLICIT]

When to use:

• Before any quality gate evaluation (G0-G3)
• When validating phase readiness

---

Core Principles

1. Law of Linkage: Every checklist item links to at least one FR-XXX or US-X. [EXPLICIT]
2. Law of Binary: Items are pass or fail. No partial credit. [EXPLICIT]
3. Law of Phase: Checklist criteria match the specific gate (G0/G1/G2/G3). [EXPLICIT]

Core Process

Phase 1: Identify Gate

1. Read current stage from context.json. [EXPLICIT]
2. Select gate criteria from R-005. [EXPLICIT]

Phase 2: Generate Checklist

1. Create items from gate criteria. [EXPLICIT]
2. Link each to spec IDs. [EXPLICIT]
3. Format: - [ ] [FR-001] {criterion}

3. Inputs / Outputs

Input	Type	Required	Description
Gate ID	Enum	Yes	G0, G1, G2, G3
spec.md	File	Yes	For ID linking

Output	Type	Description
checklist.md	File	Pass/fail checklist

Validation Gate

• All items linked to spec IDs
• Binary pass/fail for each item
• Gate-specific criteria complete

5. Self-Correction Triggers

[!WARNING] IF checklist item has no spec ID link THEN add link or flag as orphan.

Usage

Example invocations:

• "/iic-checklist-generator" — Run the full iic checklist generator workflow
• "iic checklist generator on this project" — Apply to current context

Assumptions & Limits

• Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
• Requires English-language output unless otherwise specified [EXPLICIT]
• Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate