Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.
Now that we have a spec and tasks list ready for implementation, we will proceed with orchestrating implementation of each task group by a dedicated agent using the following MULTI-PHASE process.
Turn an ambiguous request into an evidence-backed recommendation via discovery, adaptive specialist review, one challenge round, and chair synthesis. Use for high-uncertainty or high-impact decisions. Output: a decision record; stops for approval, then hands to /spec.
Summarize the current Claude Code session into a structured vault note saved to VAULTDIR/. Follows the established naming and linking conventions of the vault.
Orchestrate multi-agent PR workflows with git worktrees. Uses the herdr MCP when available; falls back to git-native worktrees + opencode subagents when not.
Refresh the managed Codument standards and installed skill shells in an existing workspace while preserving project-owned tracks, attractors, behaviors, modeling, engineering, decisions, and memory. The command creates a full backup first, then migrates legacy tracks/ / directories to tracks/active/ / and legacy…
A pair of commands for sending questions to an external advisor and checking the advisor's response later. The consultation runs asynchronously, meaning the request returns before the answer is ready.
A command for taking the next task from a Kanban board, working on it in the right code repository, and submitting the result for review. A Kanban board is a task list organised by workflow stages.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: