ma

MA quality-gated pipeline

Coordinate call order, scope, state, approval, validation, and (optional) notification. Keep phase implementation in the corresponding ma-* skill; do not duplicate it here.

All paths in this skill resolve through the workspace config (see the plugin's config/README.md): artifacts under {contextRoot}/{domain}/, pipeline state under {stateRoot}/{key}/.

Invocation

/ma <issue-key> [--resume] [--base <branch>] [--target <branch>] [--auto]

• Require an issue key matching the configured issueKeyPattern, e.g. PROJ-123. If the workspace has no issue tracker, any key matching the pattern names the work; requirements then arrive as user-provided text.
• Default --base to the project's configured base branch (commonly develop or main).
• Default --target to feature/{key}-{slug}.
• Use --resume to continue from the first incomplete phase after validating recorded artifacts.
• Treat --auto as flag forwarding only. It does not grant implementation approval unless the user explicitly requested unattended implementation.

Examples:

Input	Action	Stop condition
/ma PROJ-123	Resolve the requested scope, initialize state, then run the gated pipeline	Selected scope terminal
/ma PROJ-123 PLAN까지만	Run PRD, design, and per-project PLAN	Phase 2.3
/ma PROJ-123 --resume	Revalidate prior results and enter the first incomplete phase	Selected scope terminal or a halt gate

References index

File	When to read
references/scope-gate.md	Phase 0 and every MA entry — terminal scope resolution (SSOT, also read by each ma-* skill)
references/accuracy.md	At the start of every ma-* step — accuracy and reporting contract

Execution contract

1. Resolve scope before work. Read references/scope-gate.md and set one of docs, plan, plan-review, or impl. Interview once when the terminal scope is materially ambiguous. Never enter Phase 3+ for scopes below impl.
2. Initialize durable state immediately after scope resolution. This preserves recovery if any later phase fails.
3. Enter phases in order. Before each phase, confirm the preceding phase is in completedPhases and its required artifact exists. If handoff moved an artifact, validate the new path recorded in state instead of requiring the old path.
4. Require implementation approval. After Phase 2.5, stop once for approval that records project, base, and target. Neither --auto nor an impl scope bypasses this gate unless unattended implementation approval was explicit.
5. Keep project writes inside the handoff worktree. Phase 4 implementation goes through /ma-dispatch; do not edit a target project's main checkout directly.
6. Complete each phase atomically. Call the phase skill, verify its artifact gate, send the optional notification, append timeline.md, update phaseResults, then add the phase to completedPhases. A failed step leaves the phase incomplete and must be repaired and rechecked.
7. Use agent return values, not polling. The /ma-dispatch STATUS block is the completion source of truth. Do not add sleep loops.
8. Preserve recoverability on halt. Record structured evidence, send the optional halt notification, and keep artifacts intact so --resume can continue safely.