implement-spec

Implement Spec

Use coding-orchestration as the only router, including its governed execution and run selection sections. Read the approved spec and resolve all linked authorized tickets and dependencies. Missing ticket content is unresolved scope, not permission to omit the ticket. Use the pure orchestration-plan operation when dependencies or disjoint ownership need an explicit frontier. Load the governed execution recipe before dispatch. Preserve settled definition; do not repeat the original interview.

The user's request may authorize a named spec and its scoped tickets; the user need not recite IDs or repeat retained authorization. Astra authors the plan and a different fresh Astra reviews it. Jev checks coverage before and after review. The runtime enforces eligible dispatch; planning itself grants no authority. Before dispatch, the parent verifies that the repository, revision, ticket IDs, owned surfaces, protected boundaries, and requested operation still match the current user instruction.

Run eligible disjoint work in parallel within the available host/provider capacity. Use isolated worktrees when needed for safe ownership, not as a mandatory worktree per ticket. Each writer gets an exact root, bounded scope, focused checks and terminal state. Carry approved visual references through design-direction before UI dispatch. Recompute an explicit frontier after integration when used. The parent owns integration, conflicts, applicable integration checks, corrections and final judgment.

Preserve operation-specific authority for publication, merge, release, production, external writes, paid services and destructive cleanup. Use current and retained user authorization with the repository policy; do not request a settled approval again. Prepare reversible local work and the reviewable candidate before stopping for a genuinely missing external-operation authorization.

This adapter preserves the useful task-graph pattern from Matt Pocock's upstream implement-spec snapshot while replacing its delivery semantics with the Development System contract.

Governed spec and ticket handoff

Use the shared definition contract for stable criteria, linked tickets, dependencies, rules and required evidence. Astra XHigh authors definition and the implementation plan; a different fresh Astra XHigh reviews that plan. Fast researchers supply bounded source facts. When implementation is authorized, use coding-orchestration and its governed Jev recipe across the complete feature, including nonvisual behavior. Retrieve all tickets linked by the spec; preserve settled decisions across threads.