adlc-levelup-init

Scan brownfield codebases to generate draft Context Directive Records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scan brownfield codebases to uncover latent Context Directive Records (CDRs) that can feed team-ai-directives.

Core Features & Use Cases

  • Scan existing repositories to surface potential CDRs
  • Generate draft CDRs with status "Discovered" for team review
  • Produce a concise summary and handoff options to proceed

Quick Start

Provide a brownfield repository path to initiate CDR discovery.

Frequently Asked Questions about adlc-levelup-init

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

FAQPage Schema
How do I discover existing patterns in a brownfield codebase for AI context directives?

To discover patterns in a brownfield codebase for AI context directives, you can scan the repository to identify latent Context Directive Records (CDRs). This process analyzes the project structure and detects potential sub-systems to surface draft CDRs for team review.

What are Context Directive Records and when do I need to generate them from my code?

Context Directive Records (CDRs) are patterns extracted from a codebase to feed team-ai-directives. You need to generate them when you want to establish structured AI context from an existing project, ensuring AI tools understand your established architectural conventions.

How do I scan my repository to extract draft CDRs for team review?

To scan your repository and extract draft CDRs, provide the brownfield repository path to initiate pattern discovery. The scan analyzes the project structure and outputs draft CDRs with the status "Discovered" to the designated drafts area for refinement.

Do I need a specific directory structure to scan a codebase for CDRs?

Yes, you need a valid .specify project structure with a .specify/ directory to scan a codebase for CDRs. The tool outputs the discovered draft CDRs directly to {REPO_ROOT}/.specify/drafts/cdr.md for your team to review.

What is the best way to identify sub-systems in an existing codebase for AI directives?

The best way to identify sub-systems in an existing codebase for AI directives is to run an automated pattern discovery scan. This detects potential sub-systems within the project structure and generates a concise summary with handoff options to proceed with your team.

Can I use team-ai-directives with a codebase that has no existing CDRs?

Yes, you can use team-ai-directives with a codebase lacking CDRs by running a pattern discovery scan. It surfaces latent patterns from your existing repository and produces draft CDRs, providing a baseline for your team to review and refine into formal directives.