levelup-specify

Extract Context Directive Records from feature specifications and link them to artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract Context Directive Records (CDRs) from current feature specifications to capture reusable patterns and guidelines for future work.

Core Features & Use Cases

  • Extract and catalog CDRs from active feature specs to build reusable guidance.
  • Link CDRs to artifacts (spec.md, plan.md, tasks.md, trace.md) for traceability.
  • Prepare enriched drafts in .specify/drafts/cdr.md for review and integration.

Quick Start

Run the extractor on the active feature spec to generate and draft all CDR entries.

Frequently Asked Questions about levelup-specify

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

FAQPage Schema
How do I extract reusable patterns from feature specifications?

You can extract reusable patterns from feature specifications by analyzing artifacts like spec.md, plan.md, and tasks.md to identify and catalog Context Directive Records for future project reuse.

What is a Context Directive Record and when do I need to catalog it?

A Context Directive Record captures reusable guidelines and patterns from feature specs. You need to catalog CDRs when you want to preserve team AI directives and structured knowledge for ongoing or future projects.

How do I generate CDR drafts in the .specify workspace?

To generate CDR drafts in the .specify workspace, run the extractor on your active feature specification to analyze linked artifacts and prepare enriched drafts at .specify/drafts/cdr.md for review.

Can I link extracted CDRs to trace.md and other spec artifacts?

Yes, extracted CDRs can be linked to feature artifacts including spec.md, plan.md, tasks.md, and trace.md, ensuring full traceability between the captured directives and their source specification documents.

Do I need structured evidence linking to enrich feature spec CDRs?

Yes, structured evidence linking is required to enrich feature spec CDRs, as the extractor relies on analyzing interconnected artifacts to accurately identify, catalog, and draft reusable team AI directives.

What's the best way to build a reusable knowledge base from feature specs?

The best way to build a reusable knowledge base from feature specs is to systematically extract and catalog CDRs from active projects, linking them to source artifacts and preparing enriched drafts for team integration.