agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese…
Use when starting a new round (substrate-touching / fix-round / admin) to generate a complete handoff doc from scope + prior-round context. Dispatches the planner sub-agent and validates output before writing.
$ npx -y skills add Arch1eSUN/Arcgentic --skill plan-round --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/plan-roundContext preview
The summary Claude sees to decide when to auto-load this skill.
Use when starting a new round (substrate-touching / fix-round / admin) to generate a complete handoff doc from scope + prior-round context. Dispatches the planner sub-agent and validates output before writing.
name: plan-round description: Use when starting a new round (substrate-touching / fix-round / admin) to generate a complete handoff doc from scope + prior-round context. Dispatches the planner sub-agent and validates output before writing.
Generates a round handoff at `docs/superpowers/plans/{YYYY-MM-DD}-{round_name}-handoff.md` by dispatching the `planner` sub-agent with a self-contained brief, then validating its output against the corresponding handoff template (18 / 12 / 10 section).
Requires the `arcgentic` CLI installed (the Python toolkit):
The CLI runs in a subprocess; this markdown skill is the thin shim that invokes it.
For V1 rounds with external workflow inputs, first validate source/spec context:
arcgentic source-intake validate docs/source-intake/*.yaml arcgentic capability-registry build <marketplace-catalog.json> arcgentic spec-governance status <change-dir>
For projects with `project.session_mode` already set, include the inherited mode and dispatch order in the handoff instead of asking again:
arcgentic orchestrator-dispatch \ --round <round_name> \ --handoff <handoff-path> \ --mode <single-session|multi-session>
Parse from `$ARGUMENTS` (passed by Claude Code):
If any required input is missing, ASK the user before proceeding.
When invoked with all inputs:
1. Validate `round_name` matches the pattern `R<phase>[.<round>[.<fix>]]` or `R<phase>-<name>`. 2. Validate `prior_round_anchor` is a full 40-character hex SHA (NOT short). 3. Shell out to the CLI:
arcgentic plan-round-impl \
--round=<round_name> \
--type=<round_type> \
--anchor=<prior_round_anchor> \
--scope=<scope_description>4. Read the CLI's stdout — it contains either:
5. Report to the user: handoff path, section count, dispatch order, and any warnings.
6. If validation failed (exit code 1 or 2): explain the failure + suggest a fix (re-run with correct anchor, etc.).
the planner's output had unfilled placeholders. Re-run with more specific `--scope=...` OR open the handoff file at the reported path and fill the placeholders manually.
template files (templates/handoff_*) updated but skill cache stale — surface as a bug.
**Arcgentic is a harness engineering layer for AI coding agents. It turns ad-hoc prompting into a gated engineering workflow.** 中文文档 -> README.zh-CN.md Arcgentic helps Codex and Claude Code run software work as a disciplined sequence: clarify the idea, plan
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese…
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development →…
External-audit role for arcgentic rounds. Loaded when arcgentic state.yaml is in awaiting_audit or audit_in_progress, OR when the…
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through…
Use only after an arcgentic round has an external audit PASS and state.yaml is in passed. Anchors the verdict, runs strict…
Use when running Arcgentic V2 in Codex and the current thread must orchestrate fixed Planner, Developer, Test, and Auditor role…