Menü
Answer "what's next?" by surfacing open deferred/follow-up work for the current repo from the forge task board, ranked. Use when asked what to work on next, what's outstanding, or to resume work.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Force a Ferrosa Memory consolidation pass at the end of a productive session so the dream cycle (edges, scenes, profiles) runs now instead of on the idle timer. Use at wrap-up, when the user says "that's it for now", or before a long break.
Capture deferred/follow-up work to the forge task board so it isn't lost. Use when you surface work you won't do now — out-of-scope items, prerequisites, follow-ups, "leave for later", known gaps. Pairs with /whats-next and /roadmap.
Restore working context from Ferrosa Memory at the start of a session (or after /clear) before doing anything else. Use at session start, after compaction, or when resuming work on a repo.
Build a roadmap for a repo by combining deferred work from the forge task board with a live TODO/FIXME scan of the repo, synthesized into themed, prioritized Now/Next/Later. Use when asked for a repo's roadmap, backlog, or debt plan.
Declare a time-bounded fact or temporary constraint in Ferrosa Memory (valid_from / valid_until). Use when something only holds for a window — a deadline, code freeze, deprecation, or planned-future change — so search surfaces it only while it is valid.
| name | whats-next |
| description | Answer "what's next?" by surfacing open deferred/follow-up work for the current repo from the forge task board, ranked. Use when asked what to work on next, what's outstanding, or to resume work. |
Read the deferred-work inbox (forge task board) and present what to do next. Companion
to /defer (capture) and /roadmap (synthesize). Tagging contract:
../defer/references/deferred-work-conventions.md.
Invocation shape: /whats-next [repo-path] [--all-status] [--global] [--limit N].
Supporting reference: ../defer/references/deferred-work-conventions.md.
Resolve the repo. Positional arg if given, else
git -C <cwd> rev-parse --show-toplevel. --global = across all repos (skip filter).
Fetch open work. mcp__forge__task_board (or task_list). Open = status in
triage, ready, in_progress, blocked (exclude complete/archived). With
--all-status, include everything.
Filter to the repo (unless --global): keep tasks where
workspace_path == repo OR the body's first line is repo=<repo> (the hook/CLI
path). See the conventions' "belongs to repo" rule.
Rank & group. Order by status (in_progress → blocked → ready → triage), then
priority desc, then oldest created_at. Show ≤ --limit (default 15) per group.
Present compactly — per item: task_id · title · priority · age (days) ·
source (created_by). Lead with a one-line count summary
(e.g. "3 in progress, 5 ready, 12 triage"). Then offer next actions: promote a
triage item (task_update --status ready), start one, or run /roadmap for the
full themed view.
/whats-next
/whats-next ~/src/ferrosa-suite/ferrosa --limit 10
/whats-next --global
triage items are the unreviewed deferred inbox — skim them first; promote real ones
to ready, archive noise.