[Extension]: Add MAQA — Multi-Agent & Quality Assurance (v0.1.6, catalog update) #4233

Extension ID

maqa

Extension Name

MAQA — Multi-Agent & Quality Assurance

Version

0.1.6

Description

Coordinator → feature → QA agent workflow with parallel worktree-based implementation. Language-agnostic. Auto-detects installed board plugins (Trello, Linear, GitHub Projects, Jira, Azure DevOps).

Author

GenieRobot

Repository URL

https://github.com/GenieRobot/spec-kit-maqa-ext

Download URL

https://github.com/GenieRobot/spec-kit-maqa-ext/releases/download/maqa-v0.1.6/maqa.zip

License

MIT

Homepage (optional)

https://github.com/GenieRobot/spec-kit-maqa-ext

Documentation URL (optional)

https://github.com/GenieRobot/spec-kit-maqa-ext/blob/main/README.md

Changelog URL (optional)

https://github.com/GenieRobot/spec-kit-maqa-ext/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.3.0

Required Tools (optional)

• git (with worktree support) - required
• python3 - required (JSON parsing in coordinator scripts)

Number of Commands

4

Number of Hooks (optional)

1

Tags

multi-agent, orchestration, quality-assurance, workflow, tdd

Key Features

• Coordinator agent: assesses specs/ for ready features, creates isolated git worktrees, returns a SPAWN plan for parallel feature agents
• Feature agent: implements one feature in one worktree, feature/<name> branch, configurable no-tests / tests-after / TDD (write-test-first, red assumed, no pre-run) cycle, commit is mandatory before returning
• QA agent: 8-point static analysis gate (test-suite trust, checklist completeness, text/grammar/placeholder copy, link/route verification, security grep pass, WCAG 2.1 AA accessibility, responsive layout, empty/error states) — all configurable per-project via maqa-config.yml
• Auto-detects an installed board companion (Trello, Linear, GitHub Projects, Jira, Azure DevOps) for kanban-style state tracking; falls back to local .maqa/state.json
• Optional CI gate via the maqa-ci companion — blocks QA handoff until the pipeline is green
• On Claude Code, /speckit.maqa.setup deploys coordinator/feature/QA as true native parallel subagents

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Tested on: Linux, Spec Kit CLI v0.13.2, Claude Code integration.

Test project: a Rails 8.1 app (private), spec-kit initialized via specify init --here --integration claude.

Test scenarios:

1. Installed via specify extension add maqa --from <release-zip-url>
2. Ran /speckit.maqa.setup — deployed .claude/agents/{coordinator,feature,qa}.md
3. Verified deployed subagents resolve their workflow file correctly (this surfaced the bug fixed in v0.1.6 — see below)
4. Reviewed all four command bodies (coordinator, feature, qa, setup) end to end against maqa-config.yml

v0.1.6 specifically fixes a real bug found during this testing: the setup command's deployed subagent templates referenced .claude/commands/speckit.maqa.*.md, which does not exist under current spec-kit Claude integrations (command bodies install under .specify/extensions/maqa/commands/, and Claude Code uses skills, not a .claude/commands/ directory). Native subagents could not previously locate their own instructions. Also bumps the coordinator and QA subagents from haiku to sonnet, since both do branching orchestration / semantic judgment rather than mechanical work.

Example Usage

# Install
specify extension add maqa --from https://github.com/GenieRobot/spec-kit-maqa-ext/releases/download/maqa-v0.1.6/maqa.zip

# (Claude Code only) deploy native subagents once per project
/speckit.maqa.setup

# Run the coordinator
/speckit.maqa.coordinator

Proposed Catalog Entry

{
  "maqa": {
    "name": "MAQA — Multi-Agent & Quality Assurance",
    "id": "maqa",
    "description": "Coordinator → feature → QA agent workflow with parallel worktree-based implementation. Language-agnostic. Auto-detects installed board plugins (Trello, Linear, GitHub Projects, Jira, Azure DevOps). Optional CI gate.",
    "author": "GenieRobot",
    "version": "0.1.6",
    "download_url": "https://github.com/GenieRobot/spec-kit-maqa-ext/releases/download/maqa-v0.1.6/maqa.zip",
    "repository": "https://github.com/GenieRobot/spec-kit-maqa-ext",
    "homepage": "https://github.com/GenieRobot/spec-kit-maqa-ext",
    "documentation": "https://github.com/GenieRobot/spec-kit-maqa-ext/blob/main/README.md",
    "changelog": "https://github.com/GenieRobot/spec-kit-maqa-ext/blob/main/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.3.0"
    },
    "provides": {
      "commands": 4,
      "hooks": 1
    },
    "tags": ["multi-agent", "orchestration", "quality-assurance", "workflow", "parallel", "tdd"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-03-26T00:00:00Z",
    "updated_at": "2026-08-20T00:00:00Z"
  }
}

Additional Context

This is a version update, not a new submission (maqa is already in the community catalog at a stale v0.1.3 — see closed PR #4232, where @mnriem asked that catalog updates go through this issue template instead of a direct PR). I'm the extension author.