メニュー
Run all tests - unit tests in parallel, then acceptance tests with backend. Use when user wants to run the full test suite or mentions /test-all command.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review the latest work unit with fresh, unnarrowed eyes and surface any problem it contains as follow-ups. Use after a work-unit commit, or when the user runs /agent-review.
Continue working on a story or task by reading progress.md, executing the next work unit, and updating progress. Use when user wants to resume story/task work or mentions /continue command.
Run a Selenium test in visible (non-headless) mode with slowdown so the user can watch it. Use when user wants to demo or visually watch a Selenium test or mentions /demo command.
Preview the planned design for a scenario before writing tests. Shows domain model changes, usecase patterns, and key design choices. Use before red-usecase to get user approval on the implementation approach. If the user rejects the design, offers to discuss inline or escalate to /architecture for a full ADR.
Write a journey summary capturing noteworthy moments (predictions, decisions, surprises, mistakes, quirks). Runs automatically the moment the agent observes something worth noting during work, and manually before /clear or /compact as a final sweep. Idempotent — skips entries already recorded. Use when the agent observes a noteworthy moment, before clearing context, or when the user mentions /handoff.
Re-explain the last thing in plain words. Use ONLY when the user explicitly types /plain or asks to "explain that simply / in plain words / like I'm not an expert". Never invoke on your own initiative — this is a manual button the user presses when something was hard to follow.
| name | test-all |
| description | Run all tests - unit tests in parallel, then acceptance tests with backend. Use when user wants to run the full test suite or mentions /test-all command. |
Runs the complete test suite: unit tests in parallel, then acceptance tests.
Read ProductSpecification/technology.md Conventions table for:
Discover backend adapter modules by listing directories under backend/adapters/.
Run ALL of these commands in parallel using multiple Bash tool calls in a single message:
{Backend test command} with module = usecase{Backend test command} per adapter module discovered{Frontend test command}Wait for all to complete. If any fail, report failures and STOP.
Use the Skill tool to invoke /run-backend:
Skill tool: skill="run-backend"
Wait for backend to start.
{Acceptance test command} for backend tests
Use the Skill tool to invoke /stop-backend:
Skill tool: skill="stop-backend"
Report summary: