adlc-levelup-specify

Extract reusable patterns from feature specifications by reading artifacts like spec.md, plan.md, and trace.md to generate Context Directive Records. This process captures architectural patterns into a searchable library within .specify/drafts/cdr.md.

Context Directive Records in software engineering workflows are structured artifacts that capture reusable implementation patterns and decisions from feature specs. They link specifications to commits and tasks, forming a systematic knowledge library for team reuse.

Enrich existing CDRs by applying this skill to your current feature context, which reads trace artifacts and links to commits. It updates the .specify/drafts/cdr.md file with feature-specific evidence blocks and enrichment metadata for better traceability.

CDR extraction requires a spec-kit style project structure to function correctly. It specifically relies on the specs/*, .specify/, and trace artifact directories to read feature specifications and output the enriched draft records.

You can link feature specifications to commits and tasks during CDR extraction when those references are available in the context. The skill reads plan.md and trace.md artifacts, pulling available commit and task links into the output evidence blocks.

Limitations of extracting Context Directive Records include strict reliance on a spec-kit project structure and the presence of populated spec.md, plan.md, and trace.md artifacts. Without these structured inputs, the skill cannot generate meaningful enrichment metadata.