speckit-adlc-levelup-specify

Extract Context Directive Records from feature specifications into CDR drafts.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-adlc-levelup-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-adlc-levelup-specify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/speckit-adlc-levelup-specify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill speckit-adlc-levelup-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract Context Directive Records (CDRs) from the current feature specification to capture learnings and reuse guidelines, replacing the older /spec.levelup workflow.

Core Features & Use Cases

  • Extract CDRs from feature specs, plans, tasks, and any available traces to seed a drafts repository.
  • Enrich existing CDRs with feature-specific evidence, references, and implementation context from the spec artifacts.
  • Update and organize {REPO_ROOT}/.specify/drafts/cdr.md with new or revised CDR entries for review and future adoption.

Quick Start

Analyze the current feature spec to generate CDRs and add them to .specify/drafts/cdr.md.

Frequently Asked Questions about speckit-adlc-levelup-specify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract reusable patterns from feature specs and traces?

To extract reusable patterns, analyze feature specifications, plans, tasks, and traces to surface Context Directive Records (CDRs). This process captures learnings and implementation context into structured drafts for future project adoption.

What is a Context Directive Record and when do I need to generate one?

A Context Directive Record (CDR) is a structured entry capturing learnings and reuse guidelines from feature development. You need to generate CDRs when you want to surface reusable patterns from existing specs to seed a drafts repository for future projects.

How do I enrich existing CDRs with evidence from feature specification artifacts?

You enrich existing CDRs by processing current spec artifacts like plans, tasks, and traces. The extraction adds feature-specific evidence, references, and implementation context to the records using non-destructive enrichment techniques.

Can I organize CDR drafts without overwriting my existing feature spec evidence?

Yes, you can organize CDR drafts without overwriting existing evidence. The extraction process updates the drafts file at .specify/drafts/cdr.md using non-destructive enrichment, preserving original references while appending new or revised entries.

Does the CDR extraction process work with both plans and trace artifacts?

Yes, CDR extraction operates across multiple artifact types including specs, plans, tasks, and traces. It analyzes all available artifacts to comprehensively surface reusable patterns and implementation context for the drafts repository.