Skill: SDD Contract Templates

Purpose

ALDC is spec-driven: every phase produces a document that follows an immutable template. This skill bundles those 14 templates as assets/ so they travel with the APM package and resolve after apm install — instead of living at a docs/templates/ path that APM never deploys to a consumer project.

Templates are Just-In-Time resources: load the specific one only when you are about to produce its document. Never read all of them at once.

How agents consume these

Some templates are read at runtime (an agent copies/fills/renders them); the ALDC agents reference those by their asset path skill-sdd-contracts/assets/<file>. The rest are human reference — their format is already inlined in the agent/prompt that owns them, so they are bundled here for completeness but are not read during a run.

Asset	Consumed
assets/architecture-template.md	runtime
assets/bcquality-task-context.md	runtime
assets/code-review-template.md	runtime
assets/delivery-template.md	reference
assets/memory-template.md	reference
assets/mkdocs-site-prompt.md	reference
assets/phase-complete-template.md	reference
assets/plan-complete-template.md	reference
assets/plan-template.md	reference
assets/planning-findings-template.md	runtime
assets/skill-template.md	reference
assets/spec-template.md	reference
assets/technical-spec-template.md	reference
assets/test-plan-template.md	runtime

Usage rule

1. Identify the document you are about to write (architecture, spec, test plan, …).
2. LOAD skill-sdd-contracts/assets/<template>.md — read the matching template from this skill.
3. Copy it to the target path (e.g. .github/plans/{req_name}/…) and fill every section. Never edit the template in place.

This file is generated by scripts/build-apm.mjs from the canonical docs/templates/ directory. Do not edit it by hand — edit the canonical templates and re-run the generator.