Synaipse Harness

Build only the approved slice while preserving scope, unrelated worktree changes, and validation evidence. Use when an approved execution plan or explicit bounded task is ready for implementation.

Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers. Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification.

Plan a stuck, stale, or unsafe frame into a smaller viable direction with rollback and decision boundaries. Use when a migration, plan, PR, or implementation path is producing churn, conflicting claims, or unsafe scope.

Analyze stale or conflicting lifecycle state by separating local, PR, CI, review, tracker, artifact, and session truth. Use when status is confused, work resumed after drift, evidence lanes disagree, or a closeout claim may be stale.

Create a durable guardrail, validator, doc, eval, or skill-reference update from a verified failure or learning. Use when the user asks to capture learning, prevent recurrence, encode review feedback, or refresh stale guidance.

Analyze options and trade-offs before traceable work is ready, without pretending exploration is a plan. Use when the user wants options, alternatives, decision matrices, or a bounded ideation pass before trace planning.

Create one selected trace or tracker slice spec with acceptance criteria, constraints, validation, and exit conditions. Use when exactly one slice has been selected and needs a buildable contract before implementation planning.

Plan traceable work bullets that connect intent, evidence, acceptance, and proof gaps. Use when an idea or reframe needs decomposition into traceable work units before tracker or slice specification.

Generate closure proof with exact commands, outcomes, artifact paths, untested lanes, and residual risk. Use when work and review need a receipt before closeout, release, tracker movement, or handoff.

Plan tracker-ready slices with dependencies, labels, acceptance fields, and validation placeholders. Use when trace work needs Linear-ready or tracker-ready issue structure without actually mutating the tracker.

Plan how to implement one approved slice, including file targets, validation gates, rollback, and proof lanes. Use when a slice spec is accepted and the user needs the implementation order before code changes.