source-command-new-adr

name	source-command-new-adr
description	Generate, validate, and explicitly accept a canonical ContextDevKit ADR.

source-command-new-adr

Use this skill when the user asks to run the migrated source command new-adr.

Command Template

Create a canonical Authoritative Decision Record for: $ARGUMENTS

0. Search before creating [ADR-0027]: run node contextkit/tools/scripts/decision.mjs search --objective "<key terms from the title>" --json. If an accepted ADR already governs the choice, use it or supersede it; never create a duplicate.

0b. Deliberation is conditional [ADR-0158]. An explicit /debate, a governed needsDebate: true classification, or a requirement in the selected workflow/skill requires the council before this material decision is finalized. Outside those triggers, deliberation is optional. Routing recommends the executor; missing legacy receipt fields never cancel an activated council.

1. Resolve the fleet-safe next ADR id with node contextkit/tools/scripts/intake-collision-gate.mjs --json; use the ADR row's fleet value. Do not infer the id from one directory.

2. Classify the owner and decision before writing:

   • --context-type business + --primary-context BIZ-#### for a Business decision;
   • --context-type operation + --primary-context OP-#### for an Operation decision;
   • --context-type platform for standing platform governance.

   Choose one closed --kind and, when relevant, one closed --value-intent.

3. Preview, then create only through the canonical generator:

   node contextkit/tools/scripts/decision.mjs create --id ADR-#### --kind ARCHITECTURE --context-type operation --primary-context OP-#### --title "$ARGUMENTS" --json
   node contextkit/tools/scripts/decision.mjs create --id ADR-#### --kind ARCHITECTURE --context-type operation --primary-context OP-#### --title "$ARGUMENTS" --apply --json
   

   Never copy contextkit/memory/decisions/_TEMPLATE.md, hand-build front matter, or create a new legacy ADR. Fill the generated guidance without changing its machine schema, documentVersion, or required headings.

4. Validate the exact file with node contextkit/tools/scripts/decision.mjs validate --file <path> --json. Show the proposed ADR to the user. Only an explicit human decision authorizes: node contextkit/tools/scripts/decision.mjs accept --id ADR-#### --actor human --apply --json. Acceptance stamps the deterministic decision hash; never hand-edit it.

5. Link the accepted ADR to the governing Business, Operation, or Workflow JSON with decision.mjs link. Preview implied work with node contextkit/tools/scripts/adr-tasks.mjs <NNNN> --json; this is preview-only and never creates task authority. If implementation is accepted, add tasks only through the named canonical workflow/batch pipeline/tasks.json. ADR creation never seeds tasks or dispatches agents automatically.

6. To change an accepted ADR, generate a new one and use the canonical supersession lifecycle. Never delete or rewrite an accepted record.