Menu
Use to turn a PRD, plan, or resolved feature discussion into agent-ready vertical-slice issues.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
Use for UI components, design systems, atomic design, tokens, themes, hardcoded visuals, or missing design SSOT.
Use for module boundaries, public APIs, ownership, abstractions, wrappers, test seams, or architecture review.
Use for visual PDFs: create, polish, export, verify decks, reports, proposals, one-pagers, or HTML-to-PDF.
Use for hard bugs, failing behavior, flaky tests, exceptions, regressions, or unexplained slowness before fixing.
Use for real UI E2E smoke/regression proof across web, Flutter, browser, Chrome, or device flows, with artifacts.
| name | to-issues |
| description | Use to turn a PRD, plan, or resolved feature discussion into agent-ready vertical-slice issues. |
Use this after a PRD, plan, or final grill-me synthesis exists.
If the source plan is still ambiguous, route through grill-me or to-prd
first.
Load references/vertical-slices.md before drafting issues.
Coordinate with nearby skills:
codebase-design when slices depend on ownership or interface choicestest-quality for acceptance and verification wordingDo not create external tracker issues unless the user explicitly asks to publish.