https://github.com/bostonaholic/team
Drive a feature from idea to PR with a team of Claude Code agents.
https://github.com/bostonaholic/team
agent-orchestration agent-skills agentic-ai agentic-workflow claude-code
Last synced: 5 days ago
JSON representation
Drive a feature from idea to PR with a team of Claude Code agents.
- Host: GitHub
- URL: https://github.com/bostonaholic/team
- Owner: bostonaholic
- License: mit
- Created: 2026-03-28T04:52:45.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2026-06-12T13:10:32.000Z (10 days ago)
- Last Synced: 2026-06-12T14:23:27.674Z (10 days ago)
- Topics: agent-orchestration, agent-skills, agentic-ai, agentic-workflow, claude-code
- Language: TypeScript
- Homepage: https://team.bostonaholic.dev
- Size: 1.59 MB
- Stars: 4
- Watchers: 0
- Forks: 1
- Open Issues: 39
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE
- Agents: AGENTS.md
Awesome Lists containing this project
README
# Team
A Claude Code plugin that orchestrates specialized agents to autonomously implement entire features end-to-end, driven by the **QRSPI** workflow. The orchestrator is the main Claude Code session; it persists pipeline state as artifacts in `docs/plans/` and tracks live progress with TodoWrite.
📖 **Documentation:** [team.bostonaholic.dev](https://team.bostonaholic.dev)
## Design Philosophy
Each agent does work and returns an artifact. The orchestrator dispatches the next agent based on a phase table. Agents remain decoupled — they know nothing about each other.
## Pipeline (QRSPI)
```
QUESTION → RESEARCH → DESIGN → STRUCTURE → PLAN → WORKTREE → IMPLEMENT → PR
```
- **Question** — Decompose intent into a full task record (`task.md`) and neutral research questions (`questions.md`). The questioner is the only agent that ever sees the user's original description.
- **Research** *(isolated)* — Parallel agents (file-finder + researcher) consume only `questions.md`. They never see the task. This structurally prevents opinion-bias in research findings.
- **Design** *(human gate)* — Design author asks open questions interactively, then drafts a ~200-line alignment doc. Humans review here.
- **Structure** — Break the design into vertical slices with verification checkpoints. Produced autonomously; advances to Plan with no human gate.
- **Plan** — Tactical implementation plan derived from the structure. Read by the implementer; not human-gated.
- **Worktree** — Orchestrator prepares an isolated git worktree.
- **Implement** — Test-first (test-architect writes failing tests, mechanical gate confirms) → slice execution (implementer commits each vertical slice atomically) → adversarial verification (5 parallel reviewers + typed failure-class retry loop, max 5 rounds).
- **PR** — Update changelog, commit, open pull request, surface the tracking item.
## Usage
```
/team Add rate limiting middleware to all API endpoints
```
For well-understood bugs, skip the QRSPI ceremony:
```
/team-fix Users see stale cache after profile update
```
Or run individual phases:
```
/team-question Add rate limiting middleware to all API endpoints
/team-research docs/plans//
/team-design docs/plans//
/team-structure docs/plans//
/team-plan docs/plans//
/team-worktree docs/plans//
/team-implement docs/plans//
/team-pr docs/plans//
```
Each command after `/team-question` takes the artifact directory printed by
the previous step (`docs/plans//`) as its single argument.
## Install
```
claude plugin add /path/to/team
```
## Architecture
See [docs/architecture.md](docs/architecture.md) for the full architecture, the artifact frontmatter schema, and the phase-inference rules.
## Components
- **13 agents** in `agents/` — decoupled workers that read predecessor artifacts from `docs/plans/` and write their outputs there
- **30 entry-point + methodology skills** in `skills/` — slash commands, the standalone `/shipit` land utility, and shared methodologies
- **4 hooks** in `hooks/` — safety guards and `docs/plans/`-aware compaction resilience
- **1 registry** at `skills/team/registry.json` — phase-tagged inventory of the 13 agents
- **State** lives in `docs/plans//*.md` — `` is `-` or `-`. Each artifact carries YAML frontmatter (`topic`, `date`, `phase`; gated artifacts also carry `approved`, `approved_at`, `revision`). Live in-session coordination uses TodoWrite.