Issue ready checklist
Skill muqian2026-rgb/qian-public/skills/issue-ready-checklist
Book-learn-distill + Cursor Skills for PM workflow. Fork to clone PRD gates, issue-ready checks, and skill factory patterns.
npx -y skills add muqian2026-rgb/qian-public --skill issue-ready-checklistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Definition of Ready for GitHub Issues: AC, design link, no architecture blockers. Triggers on "issue ready", "ready for dev", "definition of ready", "check this issue".
SKILL.md
2.0 KB, as published. Nobody here has run it
Issue Ready Checklist
Ready for dev = AC complete + design linked + TL sign-off on architecture blockers.
Pairs with issue-prd-architecture-workflow for full end-to-end flow.
When to use
- Before moving an Issue to "In Progress"
- Product marks Ready for dev
- Sprint planning or async gate before IC picks up work
Minimum Ready criteria
| # | Item | Required |
|---|---|---|
| 1 | Context / Goal | Why this issue exists |
| 2 | Acceptance Criteria (AC) | Testable bullets; Given–When–Then OK |
| 3 | Design link | Frame or export path tied to this issue |
| 4 | Architecture | No open blocker from TL (comment or checkbox) |
| 5 | Dependencies | Linked issues or "none" stated |
Recommended flow (short)
Epic → Issues with AC draft → TL feasibility / arch sketch → Design by issue → Ready gate → PR
Key order: architecture sketch after issue breakdown, before full design lock.
Agent workflow
- Read Issue body + comments.
- Score each Ready row: ✅ / ⚠️ / ❌
- If any ❌ on AC, design, or blocker → Not Ready + fix list
- Suggest AC additions if vague ("works well" → concrete checks)
Three things to adopt first (MVP switch)
- Every large request: Epic + child Issues + AC each — no AC, no dev
- Ready gate: AC + design link + TL no blocker
- Before release: master PRD revision log aligns with merged PRs
Negative constraints
- Do not approve Ready if AC is empty or "TBD"
- Do not skip arch review because PRD is long
- Do not treat meeting verbal OK as Ready without Issue update
Reference
Detailed checklist: references/checklist.md