Use when starting a new implementation task and an issue must be created with strict acceptance criteria gating before execution.
Create GitHub issues as the single tracking entrypoint for tasks, with a hard gate on acceptance criteria.
Core rule: no explicit, testable acceptance criteria from user => issue stays draft and execution is blocked.
draft, ready, and blocked work before execution begins.Every issue must include these sections:
draft | ready | blocked | )doneAcceptance criteria are valid only when they are testable and pass/fail checkable.
Examples:
If criteria are missing or non-testable:
Status: draftExecution Gate: blocked (missing valid acceptance criteria)Default mode is direct GitHub creation using gh issue create.
Use a body template like:
## Problem
<what is broken or missing>
## Goal
<what outcome is expected>
## Scope
- <in scope item>
## Non-Goals
- <out of scope item>
## Acceptance Criteria
- <explicit, testable criterion 1>
## Dependencies/Blockers
- <dependency or none>
## Status
draft|ready|blocked|done
## Execution Gate
allowed|blocked (<reason>)
draft: missing/weak acceptance criteria or incomplete task definitionready: acceptance criteria are explicit and testableblocked: external dependency prevents progressdone: acceptance criteria verified with evidenceNever mark an issue ready without valid acceptance criteria.
Execution workflows (for example closed-loop-delivery) may start only when:
readyallowedIf issue is draft, stop and request user-provided acceptance criteria.