implement

To turn a task card into a working implementation, use spec-driven development to treat the design doc as canon. This ensures faithful execution by routing any plan conflicts to a consult step instead of silently deviating from documented decisions.

Delta-first execution is a workflow alignment posture that prioritizes incremental code changes while ensuring prerequisites are met. It guarantees that coverage readiness and other requirements are satisfied before completing each development delta.

To preserve invariants during spec-driven development, retrieve targeted memory and run scoped list queries before coding. Capture notes and durable gotchas into maintaining-memory after each completed unit of work to maintain continuity.

You can use an implementation plan for guidance, but the design doc remains canon. If conflicts arise between the plan and the documented design, the workflow routes the decision through a consult escalation rather than guessing the correct direction.

To find the right task card to start an implementation, use the spec-driver find card command. Once located, perform the implementation aligned to the design doc while continuously capturing notes and durable gotchas into memory.

Your implementation drifts from documented decisions when plan guidance silently overrides the design doc. Prevent this by respecting the design doc as canon and routing any plan conflicts through a consult escalation before making changes.