Execute an active implementation phase against DR/IP intent, keep notes current, and surface blockers early. You MUST use this skill when implementing a delta / IP.

2026-03-040

preflight

davidlee/im

Before starting anything new, understand task, intent, and context.

2026-03-040

doctrine

davidlee/im

Understand project governance to avoid spreading heresy. you

2026-03-040

scope-delta

davidlee/im

Scope intentional change as a delta. Define applies-to specs/requirements, risks, and closure targets before implementation.

2026-03-040

shape-revision

davidlee/im

Shape a spec revision when requirements/responsibilities move. Use this before delta scoping when policy/doctrine requires revision-first flow.

2026-03-040

name	implement
description	implement a well-defined task or implementation plan

spec-driver find card $ARGUMENTS

Read the card, design doc. (if you haven't already)

read any memories which are relevant

If there's an implementation plan, read it and

if it's already begun, you don't need /preflight

NOTE: the design doc is canon; the plan is guidance. If they conflict meaningfully: /consult

Workflow alignment reminders:

Default to delta-first execution flow for implementation work.
Treat revision-first as a concession path, not the default.
Treat ceremony mode as guidance posture; do not assume runtime enforcement from ceremony alone.
For delta close-out, follow uv run spec-driver complete delta prerequisites (especially coverage readiness).

proceed with implementation.

take /notes after each complete unit of work on the task card

pay attention to doctrine, and to the decisions made in the plan. If you encounter unforeseen obstacles, /consult

if running low on context: stop before you run out of context for /continuation