Ship Spec

Drive one approved spec to completion. Keep the parent agent as orchestrator; give implementation and review to separate fresh subagents.

Define <terse-output-contract> once and apply it to every human-readable artifact and message created by this run: tracker comments, commit messages, pull-request text, blocker reports, and completion reports.

Write concise, normal prose. State only the outcome, required evidence, and next action. Use short headings and bullets. Preserve required identifiers, links, test results, review outcomes, and blockers. Express context once at the narrowest useful level.

Keep internal evidence exhaustive. Terseness changes presentation, not gates or legwork.

1. Gate on required skills

Build the available-skill set by unioning every repository-local/project and global/user-installed catalog exposed by the active harness. Check that set for these Matt Pocock skills under Engineering: