sdlc-plan-change-recordkeeping

What problem does it solve?

It standardizes how plan-change records (PC-NNN) are created, stored, and updated so that coordinator and planner produce consistent, filesystem-auditable artifacts instead of drifting or corrupting each other’s logs.

Core Features & Use Cases

• Defines a shared per-PC directory contract: standard layout under .sdlc/plan-changes/PC-NNN/ with coordinator-owned and planner-owned files.
• Enforces immutable audit anchors: request.md and decision.md are immutable after creation, while triage.md is planner-written once and artifacts-changed.md is append-only.
• Provides dispatch-lock schema and lifecycle states: a pc.yaml YAML schema with status transitions (open, triaged, approved, applying, closed, abandoned) and fields like affected_planned_stories used for dispatch refusal.
• Use case: when a coordinator triggers a plan change for a specific story, this skill ensures the routing pass can reliably track what changed and prevents concurrent dispatches to locked stories until the PC is closed or abandoned.

Quick Start

Load this skill in the COORDINATOR or PLANNER when opening, updating, or closing a plan-change record so that every change is written to .sdlc/plan-changes/PC-NNN/ using the required schema and conventions.