メニュー
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | session-mode |
| description | Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed. |
Resolves project-level single-session vs multi-session execution and prints
role-specific identity prompts. Once project.session_mode is present in
.agentic-rounds/state.yaml, do not ask again per round.
Read .agentic-rounds/state.yaml and the round handoff.
If project.session_mode.mode is already set, treat it as fact and skip the
recommendation/choice step.
If no project-level mode exists, generate a recommendation:
arcgentic session-mode recommend \
--round <round-id> \
--handoff <handoff-path>
Print recommendation, confidence, reasons, suggested role identities, and override instructions before asking the user to choose.
Print only the identity handoff prompt needed for the next role:
arcgentic session-mode prompt \
--round <round-id> \
--handoff <handoff-path> \
--mode multi-session \
--role developer
V1 valid roles: developer, auditor, closeout.
For V2 Codex-native orchestration, generate the fixed-role host plan instead of per-round role prompts:
arcgentic v2-session-plan \
--state .agentic-rounds/state.yaml \
--host codex
V2 session roles are fixed to Orchestrator, Planner, Developer, and
Auditor. close-round is an orchestrator-owned command, not a session
role.
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
Use when running Arcgentic V2 in Codex and the current thread must orchestrate fixed Planner, Developer, Test, and Auditor role threads.
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
Main-session orchestrator for arcgentic rounds. Use when in single-session mode, when a project-level session mode must drive dispatch order, or when manually advancing the state machine. Dispatches role sub-agents, verifies structured outputs, and owns PASS-only close-round execution.
Detect recurring P2/P3 audit patterns across recent rounds and promote them into lesson cards. Use after round boundaries or when repeated findings appear.
Use when a planned round handoff exists and needs to be implemented end-to-end via the 4-commit chain (entry-admin → BA design → dev body with inline CR + SE → state refresh + self-audit). Dispatches ba-designer / developer / cr-reviewer / se-contract sequentially.