agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese…
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.
$ npx -y skills add Arch1eSUN/Arcgentic --skill execute-round --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/execute-roundContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
name: execute-round description: 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.
Orchestrates the 4-commit chain for an arcgentic round per spec § 4.2.3. Reads the planned handoff (from `plan-round` skill or hand-authored), then executes Phase 1-4 via the `arcgentic` Python CLI.
Requires the `arcgentic` CLI:
Requires a planned handoff doc — run `/plan-round` first if missing.
V1 projects must resolve the session-mode gate before implementation. If `project.session_mode.mode` is already present in `.agentic-rounds/state.yaml`, use it and do not ask again:
arcgentic session-mode recommend --round=$ROUND --handoff=$HANDOFF_PATH arcgentic session-mode prompt --round=$ROUND --handoff=$HANDOFF_PATH --mode=multi-session --role=developer
Parse from `$ARGUMENTS`:
When invoked:
1. Verify the handoff doc exists at `handoff_path`. 2. Shell out:
arcgentic execute-round-impl --round=$ROUND --handoff=$HANDOFF_PATH [--dry-run]
3. The CLI orchestrates 4 phases:
4. Read CLI output for result summary (per ExecuteRoundResult.summary()):
5. Report to user: 4 commit SHAs + findings counts + handoff path.
See `docs/tech-debt.md` for the full forward-debt registry.
**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…