القائمة
Use when a Make It Real run needs a read-only status summary of setup, hooks, Kanban state, active work, blockers, or verification evidence.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when a feature request needs Make It Real PRD, architecture, responsibility boundaries, contracts, design-pack artifacts, or Kanban work decomposition before implementation.
Use when a feature request needs Make It Real PRD, architecture, responsibility boundaries, contracts, design-pack artifacts, or Kanban work decomposition before implementation.
Use when an approved Make It Real plan should advance into gated Kanban execution, agent orchestration, verification, and live-wiki synchronization.
Use when an approved Make It Real plan should advance into gated Kanban execution, agent orchestration, verification, and live-wiki synchronization.
Use when a Make It Real run needs manual verification, blocked-gate diagnosis, contract checks, evidence review, or Done-readiness inspection.
Use when a Claude Code project needs Make It Real initialization, hook setup, run-state wiring, or first-time harness configuration before planning or launch.
استنادا إلى تصنيف SOC المهني
| name | status |
| description | Use when a Make It Real run needs a read-only status summary of setup, hooks, Kanban state, active work, blockers, or verification evidence. |
Summarize the current harness state without changing implementation.
The browser dashboard is read-only observability. It may show the next recommended Claude Code command, evidence paths, and Kanban status. State changes belong to Claude Code conversation, Make It Real hooks, and internal engine gates. Do not add browser buttons for approval, launch, retry, reconcile, or Done transitions.
makeitreal-engine status "${CLAUDE_PROJECT_DIR:-$PWD}" when the plugin binary is available.preview/ dashboard artifacts when config enables dashboard refresh, but it must not mutate board/run/approval/config/evidence state.dashboardRefresh.dashboardUrl is present and dashboard auto-open is enabled, run makeitreal-engine dashboard open "$RUN_DIR" --project-root "${CLAUDE_PROJECT_DIR:-$PWD}" so the browser dashboard appears for the operator.phase, blueprintStatus, headline, blockers, nextAction, evidenceSummary, dashboardRefresh, and dashboardUrl.Lead with the operator-facing phase, blockers, evidence summary, dashboard URL, and next public action. Keep raw engine fields, JSON envelopes, run ids, hashes, contract ids, and HARNESS codes in an advanced diagnostic note only when the user asks or troubleshooting requires it. Do not lead with raw engine fields.
Status is the operator's zoom-out surface. It should answer:
When plan generation failed with responsibility ambiguity, surface suggestedBoundaries as review guidance: proposed owner, allowed paths, contract ID, and verification command. Do not convert those suggestions into board mutations from status.
Status may report planning-required, approval-required, launch-ready, running, verifying, human-review, failed-fast, rework-required, blocked, or done.
Use only public next actions in the user-facing report:
/makeitreal:setup/makeitreal:plan <request>/makeitreal:config/makeitreal:plan approve as the explicit/scriptable control/makeitreal:launch/makeitreal:status/makeitreal:verify/makeitreal:doctorKeep the report short: current phase, completed items, active blockers, and the next command to run.