القائمة
Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
Interview one clear question before planning/building ideas, features, codebase maps, specs, UI flows, prototypes, or final plans.
| name | he-plan |
| description | Use for /he:plan; stage 1 readiness with Treehouse, Grill Me, owner, proof path, PASS/FAIL. |
Stage 1/5. Use for /he:plan before implementation. Finish the gate; do not timebox it.
Read ../workflow-help/references/route-map.md, ../treehouse/SKILL.md, and ../grill-me/SKILL.md before acting. Also read existing PRODUCT.md, DESIGN.md, and the project token/design-system owner when present.
he-state.json; every internal step updates steps[]; every concern/failure updates findings[]; validate it before any ready-yes handoffPASS, run check-project-context-gates.mjs --require-all; ensure PRODUCT.md, DESIGN.md, and the token/design-system owner exist and are current. Product changes update PRODUCT.md; design/UI/token changes update DESIGN.md and the token owner. Put their paths/status in the plan artifact and he-state.json.contexthe-state.json as the resume source. Record only current state, receipts, open findings, guardrails, artifacts, and next-stage readiness; do not depend on transcript memoryensure-worktree-ready.sh gate non-trivial work; skip only small clear workgrill-me when outcome, scope, proof, risk, UI flow, or visual direction is unclear; do not duplicate its workflow. Let Grill Me own session_state.md, stage map, and one-question loop, then record only the decision, blocker, or artifact path in he-state.jsonatomic-ui + impeccable; ask as many one-by-one Qs as needed until aligned or explicitly parkedto-prd, to-issues, or both only after Grill Me/artifact needs are resolvedhe-plan until missing owner, scope, proof, or risk is resolvedNext: ready for /he:implement: yes/no. No transcript dump; next stage can start a fresh thread from state