t1k:designer:base:producer-checklists
| Field | Value |
|---|---|
| Module | base |
| Version | 1.35.0 |
| Effort | low |
| Tools | — |
Keywords: milestone checklist, milestone gate, sprint classification, sprint type
How to invoke
Section titled “How to invoke”/t1k:designer:base:producer-checklistsProducer Checklists
Section titled “Producer Checklists”Executed by
Section titled “Executed by”These are the mechanical, list-running halves of t1k-designer-base-game-producer’s job: checking a
milestone report against a stated set of criteria, or classifying a sprint plan by type, and
reporting which rows pass. That is t1k-list-classifier work (routing SSOT:
rules/orchestration-rules.md § “Task-Type → Agent Routing”) — one verdict per criterion, rubric
stated, no invention.
| Step | Agent |
|---|---|
| Check a milestone-readiness report against its gate’s criteria row | t1k-list-classifier |
| Classify a sprint plan into content/feature/polish/bugfix | t1k-list-classifier |
/t1k:review already wires this: .claude/t1k-routing-designer.json declares
"reviewChecklist": "skills/t1k-designer-base-producer-checklists/references/producer-checklists.md",
so a PR touching a producer-domain file gets a 5th “domain” lane that runs t1k-list-classifier
against references/producer-checklists.md automatically — no manual spawn needed during review.
Stays reasoning-tier, in t1k-designer-base-game-producer itself, never here: ship-gate and
milestone arbitration — deciding whether a gate is READY given partial completion, waiving a
criterion. A checklist row failing is a fact; what to do about it is a decision.
When This Skill Triggers
Section titled “When This Skill Triggers”- Checking a milestone report (alpha/beta/RC/gold) against its gate criteria
- Classifying a sprint plan by type
Reference Files
Section titled “Reference Files”| File | Coverage |
|---|---|
references/producer-checklists.md | Milestone gate criteria table (moved verbatim from the agent body) and the four named sprint types — the full reviewChecklist rubric |