contract-driven-delivery 1.10.0 → 1.12.0

package/assets/contracts/data/data-shape-contract.md

@@ -1,5 +1,8 @@
 ---
 contract: data
+summary: Data schema, invalid-data handling, and row-level compatibility rules.
+owner: application-team
+surface: data
 schema-version: 0.1.0
 last-changed: 2026-04-27
 breaking-change-policy: deprecate-2-minors

package/assets/contracts/env/env-contract.md

@@ -1,5 +1,8 @@
 ---
 contract: env
+summary: Environment variable inventory, secret handling, and deployment sync policy.
+owner: platform-team
+surface: runtime-config
 schema-version: 0.1.0
 last-changed: 2026-04-27
 breaking-change-policy: deprecate-2-minors

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,150 @@
+---
+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 hot sources: `contracts/`, `CLAUDE.md`, or `CODEX.md`
+
+This skill drives steps 2–3 and physically moves the change to `specs/archive/`.
+
+## Hot / Warm / Cold Data Rules
+
+- Hot data: `contracts/`, source files, tests, CI config, `CLAUDE.md`, `CODEX.md`.
+- Warm data: the active `specs/changes/<change-id>/` directory while the change is open.
+- Cold data: `specs/archive/` after close.
+
+Cold data is historical evidence, not current requirements. Do not promote claims from old specs or archive prose unless they are backed by agent-log evidence, QA evidence, changed contracts, changed tests, or passing gates from this change.
+
+## 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 only active evidence for this change:
+- `specs/changes/<change-id>/agent-log/` (all log files)
+- `specs/changes/<change-id>/qa-report.md` (if exists)
+- `specs/changes/<change-id>/ci-gates.md`
+- `specs/changes/<change-id>/context-manifest.md`
+- `specs/changes/<change-id>/tasks.md`
+
+Do not read `specs/archive/` while closing a change. Historical archives are cold data and must not be used as current requirements.
+
+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
+- **Cold Data Warning**: "This archive is historical evidence. Current requirements live in contracts/ and active project guidance."
+
+This file records the close-out evidence, but Step 3 promotion must still be evidence-gated. Archive prose alone is not enough to change hot data.
+
+---
+
+## Step 3: Promote learnings (task 7.2)
+
+Read `specs/changes/<change-id>/archive.md` section `## Lessons Promoted to Standards` and cross-check every proposed lesson against agent-log, QA report, contract/test changes, or gate evidence from this change.
+
+Classify each candidate:
+- **promote-to-contract**: stable product/system behavior, API/data/env/business/CI rule, compatibility rule, or testable invariant.
+- **promote-to-guidance**: durable workflow guidance for future agents, provider-specific operating instructions, or project-specific agent constraints. Target `CLAUDE.md` and/or `CODEX.md`.
+- **do-not-promote**: one-off implementation detail, abandoned approach, temporary workaround, historical rationale, or anything contradicted by current contracts.
+
+If there are lessons to promote, invoke `contract-reviewer` with:
+- The archive.md lessons section
+- Supporting evidence from agent-log / QA / changed contracts / changed tests
+- Instruction: "Review these lessons and propose specific additions only for evidence-backed durable rules. For each lesson, output: classification, target file, target section, proposed text (≤ 5 lines), evidence path, schema-version bump required (yes/no). Reject any cold-data-only or one-off lesson."
+
+After contract-reviewer responds:
+1. Apply each approved contract addition to the contract file (YOU write)
+2. Apply each approved guidance addition to `CLAUDE.md` and/or `CODEX.md` only if it is provider/project guidance, not product behavior
+3. Run `cdd-kit validate --contracts` to confirm contract format is preserved
+4. Run `cdd-kit context-scan` so future classifiers see updated hot context indexes
+5. Fill in `## Lessons Promoted to Standards` in archive.md with what was promoted, where, and evidence path
+6. 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/CODEX.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
+- NEVER treat `specs/archive/` as hot requirements
+- NEVER promote a lesson without an evidence path from this change
+- Product behavior belongs in `contracts/`; agent workflow guidance belongs in `CLAUDE.md` and/or `CODEX.md`
+- The archive command is irreversible without git — remind user to commit after archiving

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

@@ -64,13 +64,15 @@ 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.
 
 The 5 always-required artifacts are: `change-request.md`, `change-classification.md`, `test-plan.md`, `ci-gates.md`, `tasks.md`.
 
-## Step 1: Generate change-id and scaffold
+## Step 1: Generate change-id, scaffold, and scan context
 
 Derive a `change-id` from the description:
 - kebab-case, max 5 words
@@ -78,9 +80,28 @@ Derive a `change-id` from the description:
 
 Check that `specs/changes/<change-id>/` does not already exist. If it does, append `-2` (or next available suffix).
 
-**Create all scaffold files using Write (do NOT run a Python script; do NOT use Edit on pre-existing files):**
+Create the scaffold with the CLI so every provider gets the same templates:
+
+```bash
+cdd-kit new <change-id>
+```
+
+Then build deterministic context indexes before invoking any classifier:
+
+```bash
+cdd-kit context-scan
+```
+
+Verify these files exist:
+- `specs/changes/<change-id>/context-manifest.md`
+- `specs/context/project-map.md`
+- `specs/context/contracts-index.md`
 
-Create `specs/changes/<change-id>/change-request.md` with the user's description filled in:
+Do not use broad search or ad hoc reads to classify the change before `context-scan` has completed.
+
+The generated scaffold contains the artifacts below. Fill `change-request.md` with the user's request before invoking the classifier.
+
+Update `specs/changes/<change-id>/change-request.md` with the user's description filled in:
 ```
 # Change Request: <change-id>
 
@@ -102,7 +123,7 @@ Create `specs/changes/<change-id>/change-request.md` with the user's description
 as soon as possible
 ```
 
-Create `specs/changes/<change-id>/change-classification.md` with blank template:
+`specs/changes/<change-id>/change-classification.md` starts from this blank template:
 ```
 # Change Classification
 
@@ -116,18 +137,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:
@@ -154,28 +182,26 @@ Create `specs/changes/<change-id>/change-classification.md` with blank template:
 ## Assumptions / Clarifications
 ```
 
-Create `specs/changes/<change-id>/test-plan.md` with blank template:
+`specs/changes/<change-id>/test-plan.md` starts from this blank template:
 ```
 # Test Plan: <change-id>
 
-## Scope
-
-## Unit Tests
-
-## Contract Tests
-
-## Integration Tests
+## Acceptance Criteria → Test Mapping
+| criterion id | test family | test file path | tier |
+|---|---|---|---|
 
-## 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:
+`specs/changes/<change-id>/ci-gates.md` starts from this blank template:
 ```
 # CI Gates: <change-id>
 
@@ -188,8 +214,17 @@ Create `specs/changes/<change-id>/ci-gates.md` with blank template:
 ## Promotion Policy
 ```
 
-Create `specs/changes/<change-id>/tasks.md` with ALL checkboxes unchecked:
+`specs/changes/<change-id>/tasks.md` starts with ALL checkboxes unchecked:
 ```
+---
+change-id: <change-id>
+status: in-progress
+context-governance: v1
+depends-on: []
+---
+
+<!-- [x]=done [-]=N/A [ ]=pending -->
+
 # Tasks: <change-id>
 
 ## 1. Preparation
@@ -241,16 +276,30 @@ Create `specs/changes/<change-id>/tasks.md` with ALL checkboxes unchecked:
 
 Invoke `change-classifier` agent with:
 - The user's change description
-- The project profile at `specs/project-profile.md` (if it exists)
-- The existing contracts in `contracts/` (if any)
+- `specs/changes/<change-id>/change-request.md`
+- `specs/changes/<change-id>/context-manifest.md`
+- `specs/context/project-map.md`
+- `specs/context/contracts-index.md`
+
+Do not authorize the classifier to read `contracts/`, `src/`, `tests/`, or broad repository search during initial classification. It must use the context indexes to propose candidate paths.
+
+The classifier must include a `## Context Manifest Draft` section with:
+- affected surfaces
+- allowed paths for each required agent work packet
+- required contracts
+- required tests
+- any context expansion requests that must be approved before implementation
 
 **change-classifier is read-only** — it will return its output as text. After it responds:
 
 1. **YOU write** `specs/changes/<change-id>/change-classification.md` — replace the blank template with the classifier's classification output.
 2. **YOU write** `specs/changes/<change-id>/agent-log/change-classifier.md` — copy the Agent Log block from the classifier's response.
-3. **YOU tick** `tasks.md` item `1.1`.
+3. **YOU update** `specs/changes/<change-id>/context-manifest.md` from the classifier's `## Context Manifest Draft`.
+4. **YOU tick** `tasks.md` item `1.1`.
 
-Wait until these three writes are done before continuing.
+Wait until these four 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.
 
 ---
 
@@ -264,6 +313,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 +342,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 +479,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,114 @@
+---
+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 only these state files first:
+- `specs/changes/<change-id>/tasks.md`
+- `specs/changes/<change-id>/context-manifest.md` if present
+- `specs/changes/<change-id>/agent-log/*.md`
+- `specs/changes/<change-id>/change-classification.md`
+
+Do not run broad repository search during resume. Do not read `src/`, `tests/`, or `contracts/` unless the current `context-manifest.md` authorizes that path or an approved expansion lists it.
+
+From `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.
+
+Read `specs/changes/<change-id>/context-manifest.md`:
+- Identify allowed paths and approved expansions.
+- Identify pending Context Expansion Requests.
+- If any request has `status: pending`, stop before invoking agents. Report the request id, requested paths, and reason; ask the user to approve, reject, or narrow it.
+- If `context-manifest.md` is missing on a legacy change, run `cdd-kit migrate <change-id>` before continuing. For context-governed changes, missing manifest is blocking.
+
+---
+
+## 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>
+Pending context expansions: <none | list request ids and paths>
+Allowed context: <short summary from context-manifest.md>
+
+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 this block at the start of every agent prompt:
+
+```
+CURRENT_CHANGE_ID: <change-id>
+Change directory: specs/changes/<change-id>/
+Context manifest: specs/changes/<change-id>/context-manifest.md
+Read only paths allowed by the context manifest and approved expansions.
+If more context is needed, stop and output a Context Expansion Request instead of reading outside the manifest.
+```
+
+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
+- Never use broad search to reconstruct state; resume from `tasks.md`, `context-manifest.md`, and `agent-log/`
+- Never continue past pending Context Expansion Requests
+- 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:

package/assets/specs-templates/context-manifest.md

@@ -0,0 +1,49 @@
+# Context Manifest
+
+This manifest defines the approved context boundaries for agents working on this change.
+
+## Affected Surfaces
+-
+
+## Allowed Paths
+- specs/changes/<change-id>/
+
+## Forbidden Paths
+- .claude/worktrees/**
+- .git/**
+- node_modules/**
+- dist/**
+- build/**
+- assets/**
+- specs/archive/**
+- specs/changes/* except specs/changes/<change-id>/
+
+## Required Contracts
+-
+
+## Required Tests
+-
+
+## Agent Work Packets
+
+### change-classifier
+- allowed:
+  - specs/changes/<change-id>/
+  - specs/context/project-map.md
+  - specs/context/contracts-index.md
+
+## Context Expansion Requests
+
+<!--
+Agents must request context expansion instead of reading outside their work packet.
+Use this format only for real requests:
+
+- request-id: CER-001
+  requested_paths:
+    - src/example.ts
+  reason: why this file is required
+  status: pending
+-->
+
+## Approved Expansions
+-

package/assets/specs-templates/tasks.md

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