agent-based-developmentlisted

# Agent-Based Development — Async Multi-Agent Workflow Run a full async multi-agent software development workflow using file-based artifact handoffs. Each invocation adopts a specific agent role and operates according to that role's responsibilities. This is the orchestrator skill. **Identify your single assigned role first** (from the slash command used or the latest plan artifact), then follow that role's skill. Do not attempt to act as multiple roles in one invocation. ## Framework Overview This is an async, artifact-driven workflow. Agents do not communicate in real time — they communicate via JSON files in a `handoffs/` directory. The flow is: ``` Planning → Design → Dev (Senior / Junior) ↓ ↓ Documentation ← Security + Tech Review ↓ ↓ Planning (triage) ← findings with severity ``` All agents must follow the Golden Rules (see `CLAUDE.md` or run `/golden-rules`). ## Agent Roster Role skills are namespaced by this plugin (e.g. `/agent-based-development:abd-plan`). Where your Claude Code resolves unambiguous bare names, the short form also works. | Agent | Skill | When to Include | |-------|-------|-----------------| | Planning | [abd-plan](../abd-plan/SKILL.md) | Almost always — assigns tasks, triages reviews | | Design | [abd-design](../abd-design/SKILL.md) | When the project has a design phase; omit for simple/script-only work | | Dev Senior | [abd-dev-senior](../abd-dev-senior/SKILL.md) | When there