agentcorp

AgentCorp

English | 简体中文

A multi-agent software-delivery pipeline packaged as Agent Skills. A Delivery Orchestrator classifies each task, routes every phase to a specialized role — planning, implementation, independent code review, and layered verification — and enforces explicit gates between phases.

Built on the Agent Skills SKILL.md standard, so the same skills install in both Claude Code and Codex from one repository.

Features

• 27 specialized skills covering the full delivery flow: requirements, test plan, design, implementation, code review, verification, acceptance, and delivery.
• Author/reviewer separation — an artifact's author never reviews or approves it.
• Independent re-verification — code-review findings are re-checked one by one by a separate role before any fix, filtering out false positives.
• Parallel fixes — fixes are partitioned by file ownership and applied concurrently without overlap.
• Structured artifacts — every phase emits a Markdown file with YAML frontmatter, forming a traceable record.
• One source, two tools — installs in both Claude Code and Codex with no duplicated content.

Workflow

The orchestrator classifies each task into one of four paradigms — dev/architecture-first, enhancement/delta-design, bugfix/hypothesis-driven, or addition/simple — and runs it through a phased lifecycle in which the author of an artifact never approves it.

1. Delivery lifecycle

Each paradigm runs a subset of the same phases. Review phases (red) and the human gate (yellow) sit between work phases; request changes and reject return work to an earlier phase.

2. Roles

Each phase has a dedicated skill. Review roles stay independent of the work they assess, and the orchestrator does not approve its own output.

3. Review → research → fix

Code-review findings are not fixed directly. An independent review-researcher re-verifies each finding before any fix, filtering out false positives. Confirmed fixes then run in parallel, partitioned by file ownership so no two workers modify the same file.

4. Handoff and gates

Delegated phases move over assignment/receipt files. Each receipt is first checked mechanically (does the artifact exist; do the paths, author, and phase match) and only then judged against the phase's quality gate — the two checks are kept separate.

Workflow modes

Mode	Default	How it runs	When
direct	no	No subagents at all; the orchestrator runs every phase itself, review phases produce drafts adjudicated by the sponsor at the human gate	small low-risk changes, or hosts without subagent support; requires explicit sponsor confirmation
partial-delegation	yes	The orchestrator runs non-review phases itself; reviews are still delegated	regular, small-to-medium tasks
full-delegation	no	Every phase is delegated to its owner via assignment/receipt	large or parallel work, or when independent authorship is required

Output artifacts

Every phase writes a Markdown artifact (with YAML frontmatter) to a fixed path, so a completed task leaves a traceable, reviewable record. Delegated phases use an assignment → receipt pair; each receipt is checked mechanically (validate-handoff.py — does the artifact exist, do the paths/author/phase match) before its quality gate, and manifest.md records every phase, owner, gate result, and artifact path.

All artifacts live under teamspace/ in the work directory. This is local coordination state and is never committed (add it to .git/info/exclude if it appears); only the subdirectories a task needs are created.