菜单
Report progress on the current plan. Reads plan.md and tasks.json, shows status of each task and overall progress. Use when user says 'show progress', 'where are we', 'status', or 'what's done'. Not for running tests — use /validate.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Full build workflow — plan, build, test, validate. Manages tasks.json throughout every step. Use when user says 'build this', 'start building', 'implement this feature', or 'make this'. Not for single-file fixes — use /build-aos, /build-device, or /build-module directly.
Run in-memory AOS tests (legacynet units). Fast unit testing — no server needed. Use when testing AOS scripts or after code changes. Not for HyperBEAM integration tests — use /test-hb instead.
Write AOS scripts and comprehensive in-memory tests. Iterates until all tests pass 100%. Use when user says 'build the AOS script', 'write the Lua code', or 'implement the handler'. Not for scaffolding — use /create-aos.
Write HyperBEAM Erlang device with eunit tests. Iterates until compilation and tests pass 100%. Use when user says 'build the device', 'write the Erlang code', or 'implement the device'. Not for scaffolding — use /create-device.
Write Vite + React frontend components with comprehensive vitest tests. 100% pass required. Use when user says 'build the frontend', 'write the UI', or 'implement the components'. Not for dev server — use /dev.
Build custom WASM64 (Rust) or standalone Lua modules with HyperBEAM integration tests. Iterates until all tests pass 100%. Use when user says 'build the module', 'write the WASM', 'custom Lua module', or 'implement the module'. Not for AOS scripts — use /build-aos.
| name | report |
| description | Report progress on the current plan. Reads plan.md and tasks.json, shows status of each task and overall progress. Use when user says 'show progress', 'where are we', 'status', or 'what's done'. Not for running tests — use /validate. |
| disable-model-invocation | true |
| allowed-tools | Read, Bash, Grep, Glob |
Report the current progress of the build plan.
Check if plan.md and tasks.json exist. If not, report "No active plan. Run /plan first."
Read plan.md for the feature name and components.
Read tasks.json and count tasks by status:
For each task, show a one-line summary:
## Progress: {feature name}
✔ Task 1: Build AOS Lua handlers
✔ Task 2: Write in-memory AOS tests
▶ Task 3: Write AOS HyperBEAM integration tests
· Task 4: Build frontend components
· Task 5: Write frontend vitest tests
· Task 6: Write frontend Playwright integration tests
· Task 7: Validate all gates
Progress: 2/7 done, 1 in progress
Components:
AOS: ██████░░░░ tests passing
Device: ░░░░░░░░░░ not started
Frontend: ░░░░░░░░░░ not started
If any task is in_progress, run a quick check on its "done when" condition:
yarn test and report pass/fail countrebar3 eunit --module=dev_{name} and report (eunit tests are inline)yarn test test/{name}-module.test.js and reportcd frontend && npm run test:unit and reportReport any blockers or issues found.