contract-driven-delivery 1.9.0 → 1.11.0

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,18 +10,25 @@
 ## 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:

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

@@ -1,23 +1,26 @@
-# Technical Design
+---
+change-id: <id>
+schema-version: 0.1.0
+last-changed: <date>
+---
 
-## Architecture Summary
+# Design: <change-id>
 
-## Affected Components
-
-## API Design
+## Summary
 
-## Data / Schema Design
+(1 paragraph: what changes architecturally and why)
 
-## UI / UX Design
+## Affected Components
 
-## Env / Config Design
+| component | file path(s) | nature of change |
+|---|---|---|
 
-## Error Handling
+## Key Decisions
 
-## Performance Considerations
+- **Decision**: rationale — rejected alternative: reason rejected
 
-## Security Considerations
+## Migration / Rollback
 
-## Deployment / Rollback
+(Prose description. SQL and code go in migration files, not here.)
 
-## Architecture Decision Notes
+## Open Risks

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/skills/contract-driven-delivery/templates/test-plan.md

@@ -1,31 +1,25 @@
-# Test Plan
+---
+change-id: <id>
+schema-version: 0.1.0
+last-changed: <date>
+risk: low | medium | high
+tier: 0 | 1 | 2 | 3 | 4 | 5
+---
 
-## Acceptance Criteria Mapping
-| requirement | test family | planned file/spec | expected evidence |
-|---|---|---|---|
-
-## Unit Tests
-
-## Contract Tests
-
-## Integration Tests
+# Test Plan: <change-id>
 
-## E2E Tests
+## Acceptance Criteria → Test Mapping
 
-## Visual Tests / Review
-
-## Data Boundary Tests
-
-## Resilience Tests
-
-## Fuzz / Monkey Operation Tests
+| criterion id | test family | test file path | tier |
+|---|---|---|---|
+| AC-1 | unit | tests/unit/test_xxx.py | 0 |
 
-## Stress Tests
+## Test Families Required
 
-## Soak Tests
+Mark all that apply: unit / contract / integration / e2e / data-boundary / resilience / monkey / stress / soak
 
-## Mutation Checks
+## Out of Scope
 
-## Commands
+## Notes
 
-## CI/CD Gate Mapping
+(Keep this section under 10 lines. Implementation detail belongs in the test files themselves.)

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

@@ -10,18 +10,25 @@
 ## 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:

package/assets/specs-templates/design.md

@@ -1,23 +1,26 @@
-# Technical Design
+---
+change-id: <id>
+schema-version: 0.1.0
+last-changed: <date>
+---
 
-## Architecture Summary
+# Design: <change-id>
 
-## Affected Components
-
-## API Design
+## Summary
 
-## Data / Schema Design
+(1 paragraph: what changes architecturally and why)
 
-## UI / UX Design
+## Affected Components
 
-## Env / Config Design
+| component | file path(s) | nature of change |
+|---|---|---|
 
-## Error Handling
+## Key Decisions
 
-## Performance Considerations
+- **Decision**: rationale — rejected alternative: reason rejected
 
-## Security Considerations
+## Migration / Rollback
 
-## Deployment / Rollback
+(Prose description. SQL and code go in migration files, not here.)
 
-## Architecture Decision Notes
+## Open Risks

package/assets/specs-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/test-plan.md

@@ -1,31 +1,25 @@
-# Test Plan
+---
+change-id: <id>
+schema-version: 0.1.0
+last-changed: <date>
+risk: low | medium | high
+tier: 0 | 1 | 2 | 3 | 4 | 5
+---
 
-## Acceptance Criteria Mapping
-| requirement | test family | planned file/spec | expected evidence |
-|---|---|---|---|
-
-## Unit Tests
-
-## Contract Tests
-
-## Integration Tests
+# Test Plan: <change-id>
 
-## E2E Tests
+## Acceptance Criteria → Test Mapping
 
-## Visual Tests / Review
-
-## Data Boundary Tests
-
-## Resilience Tests
-
-## Fuzz / Monkey Operation Tests
+| criterion id | test family | test file path | tier |
+|---|---|---|---|
+| AC-1 | unit | tests/unit/test_xxx.py | 0 |
 
-## Stress Tests
+## Test Families Required
 
-## Soak Tests
+Mark all that apply: unit / contract / integration / e2e / data-boundary / resilience / monkey / stress / soak
 
-## Mutation Checks
+## Out of Scope
 
-## Commands
+## Notes
 
-## CI/CD Gate Mapping
+(Keep this section under 10 lines. Implementation detail belongs in the test files themselves.)