Skip to content
Skills Library
Programming · Automation

execute-round

/execute-round

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.

Repository
arcgentic ↗
Licence
MIT
Last repository change
02.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 02.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author 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.

How it works

  1. When to invoke
  2. Prerequisites
  3. Inputs
  4. Workflow
  5. Known limitations (forward-debts)
  6. Failure modes
  7. See also
Original SKILL.md headings · 83 lines, 479 words
SKILL.md preview
---
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.
---

# execute-round

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.

## When to invoke

- User says "let's execute round R{N}" or "run the 4-commit chain for the handoff at ..."
- User runs `/execute-round <round_name>` slash command
- A handoff doc exists at `docs/superpowers/plans/...` and dev work is ready to start

## Prerequisites

Requires the `arcgentic` CLI:
- Stable: `pipx install arcgentic`
- Dev: `cd toolkit && pip install -e ".[dev]"`

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:

```bash
arcgentic session-mode recommend --round=$ROUND --handoff=$HANDOFF_PATH
arcgentic session-mode prompt --round=$ROUND --handoff=$HANDOFF_PATH --mode=multi-session --role=developer
```

## Inputs

Parse from `$ARGUMENTS`:
- `round_name` (e.g. "R10-L3-aletheia")
- `handoff_path` (defaults to most recent `docs/superpowers/plans/{date}-{round}-handoff.md`)
- `--dry-run` flag (optional; skip all commits and pushes)

## Workflow

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:
   - **Phase 1 — Entry-admin commit**: commit handoff + state-row updates
   - **Phase 2 — BA design pass**: dispatch ba-designer → write design doc → commit
   - **Phase 3 — Dev body**: dispatch developer → run pre-audit quality gates (mypy / pytest / ruff) → inline CR step → inline SE step (MANDATE #20: NO BA design in SE brief) → commit
   - **Phase 4 — State refresh + self-audit handoff**: compose self-audit handoff doc with stable artifact/fixed-anchor facts → run `arcgentic audit-check --strict-extended` → write → commit

4. Read CLI output for result summary (per ExecuteRoundResult.summary()):
   - 4 phase results with commit SHAs
   - CR + SE findings counts
   - Quality gate statuses
   - Self-audit handoff path

5. Report to user: 4 commit SHAs + findings counts + handoff path.

## Known limitations (forward-debts)

- **ER-RETRY**: no retry-with-context loops; if any sub-agent dispatch fails, the run aborts. Re-invoke after fixing the failure manually.
- **ER-AUDIT-FACTS-RICH**: self-audit facts avoid mutable current-state / moving-HEAD assertions, but rich commit-chain / changed-file fact generation is future work.
- **ER-STATE-ROW**: Phase 1's CLAUDE.md state-row update is a NO-OP (project-agnostic).

See `docs/tech-debt.md` for the full forward-debt registry.

## Failure modes

- **Missing handoff doc**: re-run `/plan-round` first.
- **CLI not installed**: instruct user to `pipx install arcgentic`.
- **Sub-agent dispatch failure**: re-invoke after fixing (no automatic retry in v0.2.0 P0).
- **Quality gate FAIL**: developer output had errors; review BA design + fix dev output manually; re-invoke.

## See also

- `agents/ba-designer.md` / `developer.md` / `cr-reviewer.md` / `se-contract.md` — agents dispatched
- `templates/ba_design.md` / `self_audit_handoff.md` — output structure templates
- `toolkit/src/arcgentic/skills_impl/execute_round.py` — Python algorithm
- `skills/session-mode/SKILL.md` — V1 pre-dev identity gate
- spec § 4.2 — full skill specification

Versions

The database has no other skills named execute-round.

Database snapshot: 13.11.2026 · package version 281654277c62 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100plan-round
    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.
  • 100autopilot-run
    Execute a planned Linear project autonomously over a long unattended session, ticket by ticket, about one commit per ticket. The coordinator (this session) only orchestrates. Every ticket is planned by the coordinator (Tier 1), plan-reviewed by a Tier 1 model of another vendor,…
  • 100dev-issue
    Implements GitHub issues end-to-end. Use to turn an issue into a merge-ready PR.
  • 90execute
    Execute one active project end to end - read it, confirm the code matches, implement phase by phase, pass each gate, test, commit each chunk and complete it. Use for a single project; /caddis:build runs this across many.
  • 100execute-plan
    Use when a plan or spec file exists on disk (any markdown with task headings — .mma/plans/*.md, a TODO list, a spec doc) and you need to implement one or more tasks from it sequentially in one worker session
  • 81task_implement
    Implement one existing task file end to end. Use when the user asks to build, do, or implement the work described by a task. Edit code and tests, run verification, stamp implemented, and leave audit and finish to sibling skills.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.