contract-driven-delivery 1.10.0 → 1.11.0

package/assets/agents/change-classifier.md

@@ -85,6 +85,16 @@ Note: `archive.md` is created during change close-out, not at classification tim
 ## Required Agents
 ...
 
+## Inferred Acceptance Criteria
+(List 3-8 testable acceptance criteria derived from the change request. Format: `AC-N: <criterion>`. These will be used by test-strategist to populate the Acceptance Criteria → Test Mapping table.)
+- AC-1:
+- AC-2:
+- AC-3:
+
+## Tasks Not Applicable
+(List task IDs from tasks.md that are NOT applicable to this change, using the format `2.2, 2.3, 4.2`. Main Claude will mark these as [-] in tasks.md.)
+- not-applicable:
+
 ## Clarifications or Assumptions
 ...
 ```

package/assets/agents/ci-cd-gatekeeper.md

@@ -56,6 +56,12 @@ CI/CD is mandatory. Every change must have a `ci-gates.md` plan, even if the pla
 mergeable / blocked / informational-risk
 ```
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -87,3 +93,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/contract-reviewer.md

@@ -55,6 +55,12 @@ Record dependency or migration impacts in `contracts.md` only as contract-level
 approved / changes-required
 ```
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, include an **## Agent Log** section at the end of your response with this exact structure (lines starting with `- ` are required). The calling skill will write this block to `specs/changes/<change-id>/agent-log/contract-reviewer.md`.
@@ -86,3 +92,10 @@ After completing your task, include an **## Agent Log** section at the end of yo
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/e2e-resilience-engineer.md

@@ -33,6 +33,12 @@ Your tests must prove that real user journeys and realistic failure modes behave
 
 Record test files, scenarios, fixtures/mocks, commands, screenshots/videos, and mutation checks.
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -64,3 +70,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/frontend-engineer.md

@@ -28,6 +28,12 @@ Before editing, read the change artifacts, API contract, CSS/UI contract, compon
 - Bundle size — dynamic import heavy routes; avoid full lodash / moment imports.
 - Note: avoid double-submit / rapid-action implementation bugs — but do not author monkey tests here; that is `monkey-test-engineer`'s scope.
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Handoff
 
 Report changed screens, component states covered, screenshots/videos if generated, tests added, commands run, and remaining UI risks.
@@ -68,3 +74,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/monkey-test-engineer.md

@@ -36,6 +36,12 @@ Use fuzz payloads, Playwright action sequences, property-based tests, and target
 - Adversarial corpora — common boundaries (empty, max-int, NaN, Unicode RTL, Zero-Width Joiner, surrogate pairs, BOM); SQL/JS injection strings.
 - Determinism — every monkey test must seed its randomness; record the seed on failure for replay.
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -66,3 +72,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/qa-reviewer.md

@@ -67,6 +67,12 @@ Invoke `spec-drift-auditor` at the following points (do not wait for issues to s
 approved / blocked / approved-with-risk
 ```
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, include an **## Agent Log** section at the end of your response with this exact structure (lines starting with `- ` are required). The calling skill will write this block to `specs/changes/<change-id>/agent-log/qa-reviewer.md`.
@@ -99,3 +105,10 @@ After completing your task, include an **## Agent Log** section at the end of yo
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/spec-architect.md

@@ -85,6 +85,12 @@ Your output goes into `specs/changes/<id>/design.md`. It must capture architectu
 Reference file paths instead of duplicating implementation content.
 Target: `design.md` ≤ 150 lines.
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -116,3 +122,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/stress-soak-engineer.md

@@ -60,6 +60,12 @@ Use realistic load profiles rather than arbitrary request loops.
 ...
 ```
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -91,3 +97,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/agents/test-strategist.md

@@ -64,6 +64,12 @@ Your output goes into `specs/changes/<id>/test-plan.md`. It must answer WHAT to
 Implementation detail belongs in the test files, not in test-plan.md.
 Target: `test-plan.md` ≤ 100 lines.
 
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, and the change directory provided in `CURRENT_CHANGE_ID` at the top of your prompt
+- **Before reading any file**: confirm the CURRENT_CHANGE_ID from your prompt header. If not provided, ask the caller: "What is the current change-id?" before proceeding.
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
 ## Machine-Verifiable Evidence
 
 After completing your task, write or append to `specs/changes/<change-id>/agent-log/<your-agent-name>.md`
@@ -95,3 +101,10 @@ with this exact structure (lines starting with `- ` are required):
 - Evidence must be concrete: file:line, command name + last-10-line stdout,
   contract path + section, test name, etc. NEVER write "verified" or "OK"
   without a pointer.
+
+## Read scope
+
+- Allowed: `contracts/`, `tests/`, `src/`, `specs/changes/<current-change-id>/`
+- Forbidden: other `specs/changes/` directories, `specs/archive/`
+
+Read only the current change's directory. Do NOT glob `specs/changes/**` — it pulls historical data into context and wastes tokens.

package/assets/hooks/pre-commit

@@ -14,7 +14,7 @@ change_ids=$(echo "$staged" | grep -oE '^specs/changes/[^/]+' | sort -u | sed 's
 
 for id in $change_ids; do
   echo "[cdd-kit] running gate for change: $id"
-  if ! cdd-kit gate "$id"; then
+  if ! cdd-kit gate "$id" --strict; then
     echo "[cdd-kit] gate failed for $id — commit rejected."
     echo "[cdd-kit] fix issues above; --no-verify bypasses but defeats the kit."
     exit 1

package/assets/skills/cdd-close/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: cdd-close
+description: Close and archive a completed change. Confirms all tasks are done, promotes durable learnings, then runs cdd-kit archive. Args: <change-id>
+---
+
+# cdd-close — Close and Archive a Change
+
+## Purpose
+
+A change is "done" when:
+1. Gate has passed (`cdd-kit gate <change-id>` exits 0)
+2. PR is merged (or change is abandoned)
+3. Durable learnings have been promoted to `contracts/` or `CLAUDE.md`
+
+This skill drives steps 2–3 and physically moves the change to `specs/archive/`.
+
+## Input
+
+The skill argument is the change-id (e.g., `add-jwt-auth`).
+
+If not provided, ask: "Which change-id do you want to close?"
+
+---
+
+## Abandon path
+
+If the user wants to **abandon** this change (not close as complete):
+
+```
+cdd-kit abandon <change-id> --reason "<reason>"
+```
+
+This marks `tasks.md` as `status: abandoned` and records it in `specs/archive/INDEX.md`. The directory is preserved for git history. Do NOT run the rest of this skill after abandoning.
+
+---
+
+## Step 1: Confirm gate status
+
+Run: `cdd-kit gate <change-id>`
+
+If gate fails: stop and report failures. Do NOT archive a change that hasn't passed gate.
+
+Exception: if `tasks.md` contains `status: gate-blocked`, ask the user: "This change was gate-blocked. Abandon it? (yes/no)". If yes, run `cdd-kit abandon <change-id> --reason "gate-blocked after 3 attempts"` and stop.
+
+---
+
+## Step 2: Review tasks.md section 7
+
+Read `specs/changes/<change-id>/tasks.md`.
+
+Check section 7:
+- `7.1 Archive change` — will be ticked after Step 4
+- `7.2 Promote durable learnings to contracts or CLAUDE.md` — must be done NOW
+
+If `7.2` is `[ ]`, proceed to Step 2.5. If already `[x]` or `[-]`, skip Steps 2.5 and 3.
+
+---
+
+## Step 2.5: Create archive.md
+
+Read `specs/changes/<change-id>/agent-log/` (all log files) and `specs/changes/<change-id>/qa-report.md` (if exists).
+
+Synthesize a `specs/changes/<change-id>/archive.md` file with:
+- **Change Summary**: 1 paragraph what was changed and why
+- **Final Behavior**: what the system now does differently
+- **Final Contracts Updated**: list from agent-log evidence
+- **Final Tests Added / Updated**: list from agent-log evidence
+- **Final CI/CD Gates**: list from ci-gates.md
+- **Production Reality Findings**: any surprises or deviations from the plan (from qa-reviewer agent-log)
+- **Lessons Promoted to Standards**: (leave blank — to be filled in Step 3)
+- **Follow-up Work**: any known issues deferred
+
+This file is the source for Step 3's learning promotion.
+
+---
+
+## Step 3: Promote learnings (task 7.2)
+
+Read `specs/changes/<change-id>/archive.md` section `## Lessons Promoted to Standards`.
+
+If there are lessons to promote, invoke `contract-reviewer` with:
+- The archive.md lessons section
+- Instruction: "Review these lessons and propose specific additions to the relevant contract files. For each lesson, output: target file, target section, proposed text (≤ 5 lines), schema-version bump required (yes/no)."
+
+After contract-reviewer responds:
+1. Apply each proposed addition to the contract file (YOU write)
+2. Run `cdd-kit validate --contracts` to confirm format is preserved
+3. Fill in `## Lessons Promoted to Standards` in archive.md with what was promoted
+4. Tick `7.2` in tasks.md
+
+If there are no lessons to promote, mark `[-]` for 7.2 with rationale.
+
+---
+
+## Step 4: Archive
+
+Run: `cdd-kit archive <change-id>`
+
+If successful, tick `7.1` in tasks.md (the file is now in specs/archive/, update it there):
+`specs/archive/<year>/<change-id>/tasks.md` — change `7.1` from `[ ]` to `[x]`.
+
+---
+
+## Step 5: Report
+
+```
+## /cdd-close complete
+
+Change ID: <change-id>
+Archived to: specs/archive/<year>/<change-id>/
+Learnings promoted: <list what was added to contracts/CLAUDE.md, or "none">
+
+specs/changes/<change-id>/ has been removed from the active surface.
+Token cost of future sessions reduced by ~<N> files.
+```
+
+---
+
+## Rules
+
+- NEVER archive before gate passes (unless user explicitly confirms abandoned)
+- NEVER skip Step 3 — lessons rot if not promoted
+- The archive command is irreversible without git — remind user to commit after archiving

package/assets/skills/cdd-new/SKILL.md

@@ -64,7 +64,9 @@ If no description is provided, ask the user: "Please describe the change you wan
 
 ## Artifact opt-in policy
 
-Only create optional artifacts (`current-behavior.md`, `proposal.md`, `spec.md`, `design.md`, `qa-report.md`, `regression-report.md`, `archive.md`) when the classifier's `change-classification.md` explicitly marks them as `yes`.
+Only create optional artifacts (`current-behavior.md`, `proposal.md`, `spec.md`, `design.md`, `qa-report.md`, `regression-report.md`) when the classifier's `change-classification.md` explicitly marks them as `yes`.
+
+Note: `archive.md` is created during `/cdd-close`, not during `/cdd-new` — it is not part of the classifier's opt-in surface.
 
 If the classifier marks an artifact as `no` or leaves it blank, **do not create the file** — even if a review agent could contribute to it.
 
@@ -116,18 +118,25 @@ Create `specs/changes/<change-id>/change-classification.md` with blank template:
 ## Impact Radius
 - isolated / module-level / cross-module / system-wide
 
+## Tier
+- 0 / 1 / 2 / 3 / 4 / 5
+
+## Architecture Review Required
+- yes / no
+- reason: (fill only if yes)
+
 ## Required Artifacts
-| artifact | required | reason |
-|---|---:|---|
-| current-behavior.md | | |
-| proposal.md | | |
-| spec.md | | |
-| design.md | | |
-| contracts.md | | |
-| test-plan.md | yes | every implementation change requires test planning |
-| ci-gates.md | yes | every implementation change requires CI/CD gate planning |
-| qa-report.md | | |
-| regression-report.md | | |
+Always required: change-request.md, change-classification.md, test-plan.md, ci-gates.md, tasks.md
+
+## Optional Artifacts (default: no — set yes only with explicit reason)
+| artifact | create? | reason |
+|---|---|---|
+| current-behavior.md | no | |
+| proposal.md | no | |
+| spec.md | no | |
+| design.md | no | |
+| qa-report.md | no | |
+| regression-report.md | no | |
 
 ## Required Contracts
 - API:
@@ -158,21 +167,19 @@ Create `specs/changes/<change-id>/test-plan.md` with blank template:
 ```
 # Test Plan: <change-id>
 
-## Scope
-
-## Unit Tests
-
-## Contract Tests
+## Acceptance Criteria → Test Mapping
+| criterion id | test family | test file path | tier |
+|---|---|---|---|
 
-## Integration Tests
-
-## E2E Tests
-
-## Resilience / Data-Boundary Tests
-
-## Stress / Soak Tests
+## Test Families Required
+| family | tier | notes |
+|---|---|---|
+| (unit / contract / integration / e2e / data-boundary / resilience / monkey / stress / soak) | | |
 
 ## Out of Scope
+
+## Notes
+(Keep under 10 lines. Implementation detail belongs in the test files themselves.)
 ```
 
 Create `specs/changes/<change-id>/ci-gates.md` with blank template:
@@ -190,6 +197,13 @@ Create `specs/changes/<change-id>/ci-gates.md` with blank template:
 
 Create `specs/changes/<change-id>/tasks.md` with ALL checkboxes unchecked:
 ```
+---
+change-id: <change-id>
+status: in-progress
+---
+
+<!-- [x]=done [-]=N/A [ ]=pending -->
+
 # Tasks: <change-id>
 
 ## 1. Preparation
@@ -252,6 +266,8 @@ Invoke `change-classifier` agent with:
 
 Wait until these three writes are done before continuing.
 
+**After writing change-classification.md**: read the classifier's `## Tasks Not Applicable` list. For each listed task ID (e.g., `2.2`, `4.2`), update `tasks.md` to change that item from `[ ]` to `[-]`. Do this before invoking any other agent.
+
 ---
 
 ## Step 3: Read the tier and commission agents
@@ -264,6 +280,13 @@ Read `change-classification.md` to determine the tier. Then invoke agents **in t
 
 If any agent sets `status: blocked` in its log, halt immediately and report the agent's `next-action` to the user — do not proceed to subsequent agents.
 
+**When invoking any agent, always begin the prompt with:**
+```
+CURRENT_CHANGE_ID: <change-id>
+Change directory: specs/changes/<change-id>/
+```
+This ensures the agent's Read scope restriction points to the correct directory.
+
 ---
 
 ### Tier 4–5 (low risk: docs, prompts, config-only, no behavior change)
@@ -286,6 +309,7 @@ If any agent sets `status: blocked` in its log, halt immediately and report the
 
 2. **`test-strategist`** (write-capable) — writes `specs/changes/<change-id>/test-plan.md` directly.
    - YOU tick: applicable items in section 3 based on what test families were planned
+   - Provide the classifier's `## Inferred Acceptance Criteria` list to test-strategist. These become the `criterion id` column in the Acceptance Criteria → Test Mapping table.
 
 3. **`spec-architect`** (write-capable) — only if `change-classification.md` contains `Architecture Review Required: yes`.
    - YOU tick: `1.3` (if it produced a gate plan)
@@ -422,3 +446,5 @@ Please review the above items and re-run: cdd-kit gate <change-id>
 ## After Completion
 
 The `/cdd-new` workflow is now complete. **Return to normal assistant mode immediately.** Answer any question the user asks — including questions unrelated to this change, new feature discussions, debugging help, or general conversation — without requiring them to use a specific command. The git commit shown in the report is a suggestion, not a required next step; do not wait for it before resuming normal behavior.
+
+When the change is merged and ready to close, run `/cdd-close <change-id>` to promote learnings and archive the change directory.

package/assets/skills/cdd-resume/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: cdd-resume
+description: Resume an in-progress change across sessions. Reads tasks.md and agent-log/ to determine where to continue. Args: <change-id>
+---
+
+# cdd-resume — Resume a Change
+
+## Purpose
+
+Use when returning to a change after a session break, or when `/cdd-new` was interrupted.
+
+## Input
+
+Provide the `change-id`. If unsure, run `cdd-kit list` to see active changes.
+
+---
+
+## Step 0: Detect format version
+
+Before reading state, check if `specs/changes/<change-id>/tasks.md` starts with `---` (YAML frontmatter).
+
+If it does NOT start with `---`, this change was created with a pre-v1.11 version of cdd-kit. Run:
+
+```
+cdd-kit migrate <change-id>
+```
+
+Then commit the migration:
+```
+git add specs/changes/<change-id>/tasks.md specs/changes/<change-id>/change-classification.md
+git commit -m "chore: migrate <change-id> to v1.11 format"
+```
+
+If there are many mid-flight changes, suggest `cdd-kit migrate --all` instead.
+
+---
+
+## Step 1: Read current state
+
+Read `specs/changes/<change-id>/tasks.md`:
+- Identify all `[x]` (done) items
+- Identify all `[-]` (N/A) items  
+- Identify all `[ ]` (pending) items
+
+Read `specs/changes/<change-id>/agent-log/` to list which agents have already run.
+
+Read `specs/changes/<change-id>/change-classification.md` to recall the tier and required agents.
+
+---
+
+## Step 2: Report state and ask to continue
+
+Output a resume summary:
+
+```
+## Resume: <change-id>
+
+Tier: <tier>
+Status: <in-progress | gate-blocked>
+
+Completed agents: <list from agent-log/>
+Pending tasks: <list of [ ] items>
+
+Next agent to run: <agent-name> (based on tier flow and what's missing)
+```
+
+Ask the user: "Continue from <next-agent>? (yes/no)"
+
+---
+
+## Step 3: Continue the flow
+
+If user confirms, resume from the next agent in the Tier sequence (refer to `/cdd-new` Step 3 for the agent order). 
+
+**Critical**: Inject `CURRENT_CHANGE_ID: <change-id>` at the start of every agent prompt. Do NOT re-run agents that already have a `status: complete` agent-log.
+
+Continue until all required agents are done, then run `cdd-kit gate <change-id>`.
+
+---
+
+## Rules
+
+- Never re-run an agent that already has `status: complete` in its agent-log
+- Never start from Step 1 of `/cdd-new` — only resume from the next pending agent
+- If tasks.md has `status: abandoned`, report to user and stop
+- If tasks.md has `status: gate-blocked`, go directly to gate retry (max 3)

package/assets/skills/contract-driven-delivery/templates/change-classification.md

@@ -10,14 +10,18 @@
 ## Impact Radius
 - isolated / module-level / cross-module / system-wide
 
-## Required Artifacts
+## Tier
+- 0 / 1 / 2 / 3 / 4 / 5
 
-The following 5 artifacts are always required for implementation changes:
-`change-request.md`, `change-classification.md`, `test-plan.md`, `ci-gates.md`, `tasks.md`
+## Architecture Review Required
+- yes / no
+- reason: (fill only if yes)
 
-Optional artifacts — only create when explicitly needed:
+## Required Artifacts
+Always required: change-request.md, change-classification.md, test-plan.md, ci-gates.md, tasks.md
 
-| artifact | create? (yes / no) | reason |
+## Optional Artifacts (default: no — set yes only with explicit reason)
+| artifact | create? | reason |
 |---|---|---|
 | current-behavior.md | no | |
 | proposal.md | no | |
@@ -25,9 +29,6 @@ Optional artifacts — only create when explicitly needed:
 | design.md | no | |
 | qa-report.md | no | |
 | regression-report.md | no | |
-| archive.md | no | |
-
-Default is **no**. Change classifier must explicitly set `yes` with a reason.
 
 ## Required Contracts
 - API:

package/assets/skills/contract-driven-delivery/templates/tasks.md

@@ -1,3 +1,10 @@
+---
+change-id: <change-id>
+status: in-progress
+---
+
+<!-- [x]=done [-]=N/A [ ]=pending -->
+
 # Tasks
 
 ## 1. Preparation

package/assets/specs-templates/change-classification.md

@@ -10,14 +10,18 @@
 ## Impact Radius
 - isolated / module-level / cross-module / system-wide
 
-## Required Artifacts
+## Tier
+- 0 / 1 / 2 / 3 / 4 / 5
 
-The following 5 artifacts are always required for implementation changes:
-`change-request.md`, `change-classification.md`, `test-plan.md`, `ci-gates.md`, `tasks.md`
+## Architecture Review Required
+- yes / no
+- reason: (fill only if yes)
 
-Optional artifacts — only create when explicitly needed:
+## Required Artifacts
+Always required: change-request.md, change-classification.md, test-plan.md, ci-gates.md, tasks.md
 
-| artifact | create? (yes / no) | reason |
+## Optional Artifacts (default: no — set yes only with explicit reason)
+| artifact | create? | reason |
 |---|---|---|
 | current-behavior.md | no | |
 | proposal.md | no | |
@@ -25,9 +29,6 @@ Optional artifacts — only create when explicitly needed:
 | design.md | no | |
 | qa-report.md | no | |
 | regression-report.md | no | |
-| archive.md | no | |
-
-Default is **no**. Change classifier must explicitly set `yes` with a reason.
 
 ## Required Contracts
 - API: