メニュー
This skill should be used when the user runs "/jahns-workflow:status", asks "what's the status across my projects", "show the project dashboard", "which tasks are active/blocked", or wants a cross-project overview of branches, rounds, and task progress.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user runs "/jahns-workflow:brain-tempest", has a new or half-formed project idea, says things like "I want to build X but haven't thought it through", "help me figure out what I'm actually building", "let's scope/shape this project", "brainstorm the direction", or asks to "write a design doc / SSOT" — especially at the very start, before any design document exists. It draws a project's north-star out of the user through Socratic questioning and writes it as a ready-to-adopt SSOT.md that the rest of the workflow anchors to.
This skill should be used when the user runs "/jahns-workflow:init", asks to "initialize the workflow harness", "set up jahns-workflow", "adopt the workflow in this project", or "re-sync the workflow setup". One-click setup for new projects and non-destructive retrofit for projects already in progress.
This skill should be used when the user runs "/jahns-workflow:review", pastes an external review reply (e.g. from web ChatGPT / GPT reviewer) to be processed, or asks to "ingest the review", "process the reviewer feedback", "record the external review". Preserves the review verbatim and triages findings into the task registry.
This skill should be used when the user runs "/jahns-workflow:round", says to "close the round", "wrap up this round", "finish the work cycle", or when an autonomous work round (implement → verify → push) reaches its end and the project CLAUDE.md mandates round closeout. Updates the task registry, PROGRESS, roadmap, SSOT views, and writes the round's markdown review request.
| name | status |
| description | This skill should be used when the user runs "/jahns-workflow:status", asks "what's the status across my projects", "show the project dashboard", "which tasks are active/blocked", or wants a cross-project overview of branches, rounds, and task progress. |
| argument-hint | [project-name] (optional filter) |
| allowed-tools | ["Bash","Read"] |
Show the cross-project dashboard. Zero-LLM rendering: run the script, relay its output.
Plugin root = two directories above this skill's base directory.
uv run <plugin-root>/scripts/jw_dashboard.py # all registered projects
uv run <plugin-root>/scripts/jw_dashboard.py --project <name>
Relay the output verbatim in a code block (it is pre-formatted). Add at most 1–3 sentences
in the user's configured language only when something needs flagging: blocked tasks whose
dependencies are all done (stale blocked status), projects with ✗ path missing, or
pending decision/... tasks awaiting the user. Otherwise add nothing.
Projects appear here after /jahns-workflow:init registers them. Projects without a local
clone on this machine can be tracked remotely: add { "name": "...", "repo": "owner/name" }
to ~/.claude/jahns-workflow/projects.json and the dashboard fetches their tasks.yaml via
gh api (default branch). Each project's visual dependency graph is its ROADMAP.md
(rendered by GitHub as Mermaid).