Activation Contract

Use when drafting the single change.md artifact for an SDD change whose kickoff recorded Depth: light. Loaded inline by the sdd orchestraitor; the interview and decisions already happened there. No drafting subagents are involved.

Hard Rules

One artifact: .ai/orchestrator/changes/{change}/change.md. No proposal.md, design.md, delta files, or tasks.md at light depth.
The first line is the kickoff line: Mode: … | TDD: … | Judgment: … | Depth: light.
Keep under 800 words total: roughly 150 for Why / What, 450 for Spec Deltas, 200 for Tasks.
Spec Deltas use the same semantics as sdd-draft-spec delta files: requirements use RFC 2119, scenarios use WHEN/THEN, MODIFIED restates the full replacement requirement, REMOVED and RENAMED carry Reason and Migration. Describe WHAT, not HOW. New capability behavior goes under ADDED. Omit empty ADDED/MODIFIED/REMOVED/RENAMED subsections.
At archive, each capability block under ## Spec Deltas merges into canonical specs/{capability}/spec.md exactly like a delta file; never edit canonical specs while drafting.
Tasks are small, dependency-ordered - [ ] X.Y checkboxes naming real files, sized for sdd-implement waves; testing tasks reference a Spec Deltas scenario.
Artifacts default to English; summaries and gates use the user's language.

sdd-draft-light

Activation Contract

Hard Rules

Decision Gates