implement-spec

Implement a ticket DAG with parallel frontier lanes and dual-axis review.

SKILL.md

GitHub
<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

implement-spec

Run the implement-task-graph skill, then dual-axis-review. Deliver tracer-bullet tickets on one integration branch with sparse context per lane and a standards-versus-spec review at the end.

This prompt follows Misbah Khursheed's Build Like This workflow: establish the user outcome and reasoning before generating implementation, then preserve that reasoning in contracts, boundaries, tests, and documentation.

Project identity and sources of truth

The repository where this prompt is installed is the host project being built. Build Like This is the engineering method used to build it, while mstack only installs and reconciles the method's resources. Do not mistake mstack or Build Like This for the host product unless project-owned sources explicitly say this repository develops mstack itself.

Project-owned docs/, decisions, executable code, and tests are the sources of truth. .mstack/templates/ are reference scaffolds that may be copied and adapted into project-owned documents; they are not requirements and do not replace docs/.

Treat the invocation arguments and current repository state as task input. Discover local instructions and relevant product, architecture, decision, contract, and test context before making material assumptions.

Method

  1. Load the ticket graph and parent spec; claim the unblocked frontier.
  2. Assign non-overlapping ownership to parallel lanes when subagents exist; otherwise run sequential specialist passes.
  3. Verify each ticket against its acceptance criteria before merge into the integration branch.
  4. Recompute the frontier after merges; serialize shared contracts and migrations.
  5. Finish with dual-axis-review and exact verification evidence.

Deliverables

  • Integrated implementation with per-ticket verification.
  • Dual-axis review summary and residual risks.
  • Updated ticket states.

Constraints

  • Do not unbounded-fan-out agents; keep one integration lead.
  • Do not mark tickets done without checks.
  • Do not expand beyond the spec without new tickets.

Delegation and parallel safety

  • For a material lifecycle task, the active lead must delegate at least one bounded specialist lane when subagents are available; prefer two or more concurrent lanes only when their evidence or file ownership is independent.
  • The active lead owns acceptance criteria and final integration. Supporting agents must not recursively delegate unless explicitly promoted to lead a named lane.
  • Give each delegate distinct inputs, outputs, and ownership. Serialize shared documents, contracts, schemas, migrations, deployments, external writes, and overlapping file edits.
  • If subagents are unavailable, perform the named specialist passes sequentially and report the limitation; do not imply parallel verification.
  • Delegation does not authorize outreach, paid resources, destructive changes, consequential external writes, or production deployment.

Finish with what changed or was decided, exact verification evidence, remaining risks, and the next decision only if one is genuinely required.

User arguments: $ARGUMENTS