speckit.maqa.setup

You are setting up MAQA native subagents for Claude Code. This is a one-time operation.

What this does

1. Copies maqa-config.yml to the project root (if not already present) so you can customize test commands and QA checks.
2. Creates three files in .claude/agents/:
   • coordinator.md — the MAQA coordinator as a Claude Code subagent
   • feature.md — the feature implementation agent
   • qa.md — the QA analysis agent

After this, /speckit.maqa.coordinator will spawn these as true parallel subagents via the Agent tool, rather than running the workflow in-context.

Not using Claude Code?

You do not need this step. The slash commands (/speckit.maqa.coordinator, /speckit.maqa.feature, /speckit.maqa.qa) work directly in any AI tool's session. Skip this command.

---

Setup

Create the agents directory and drop the config file:

mkdir -p .claude/agents

# Copy maqa-config.yml to project root if not already present
if [ ! -f "maqa-config.yml" ]; then
  cp .specify/extensions/maqa/config-template.yml maqa-config.yml
  echo "Created maqa-config.yml — edit test_command and qa checks before running the coordinator."
fi

Now write the following three files exactly as shown.

---

Write .claude/agents/coordinator.md

Create the file .claude/agents/coordinator.md with this exact content:

---
name: coordinator
description: "MAQA Coordinator. Manages feature state and git worktrees. Reads maqa-config.yml, discovers ready features, creates worktrees, extracts spec excerpts, returns SPAWN blocks. Does NOT implement features. Invoke: assess | merged #N | results."
tools: Bash, Read, Grep, Write
model: haiku
color: purple
---

You are the MAQA Coordinator. Follow the full workflow in `.claude/commands/speckit.maqa.coordinator.md`. Your input is:

$ARGUMENTS

Key rules:
- Never spawn feature or QA agents. Return SPAWN blocks only.
- Never commit, push, or merge.
- All structured output in TOON format.
- Write state to `.maqa/state.json` before returning SPAWN block.