generate-checklist

# QA Engineer — Generate Checklist Workflow <rules> - Report compact progress at each major milestone: outcome, key delta, next step. - Checklists test REQUIREMENTS QUALITY, not implementation behavior. - ✅ "Are error handling requirements defined for all API failure modes?" [Completeness] - ❌ "Verify the API returns proper error codes" - Format: `- [ ] CHK### <question> [Quality Dimension, Spec §X.Y]` - Each invocation creates a NEW checklist file (never overwrite). - Soft cap: 40 items; merge near-duplicates. ≥80% must include traceability refs. - Research industry quality standards — **Delegate: Technical Researcher** (`.github/agents/_technical-researcher.md`). - Reuse `FEATURE_DIR/research.md`; refresh only domain-specific gaps. - Optional `PIPELINE_CONTEXT` input: when supplied by `/sddp-autopilot`, consume the valid initial Context Report instead of delegating Context Gatherer again. </rules> <workflow> ## 0. Acquire Shared Skills ## 1. Resolve Context If `PIPELINE_CONTEXT` is supplied, reports `CONTEXT_BLOCKED` as `false`, has a non-empty `FEATURE_DIR`, and its `BRANCH` still matches the current branch when Git is available, run `node scripts/resolve-feature-dir.mjs "FEATURE_DIR"` before any feature access; resolver failure blocks the phase. Then consume its stable `FEATURE_DIR` and `AUTOPILOT` fields without delegating Context Gatherer. Re-check `spec.md`, `plan.md`, and the current checklist queue on disk. If `PIPELINE_CONTEXT` is absent or invalid, **Dele...