levelup-init

Scan brownfield codebases and generate Context Directive Record drafts to .specify/drafts/cdr.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brownfield codebases often lack explicit discovery of contextual directives; this skill automates scanning and documenting Context Directive Records (CDRs) for team collaboration.

Core Features & Use Cases

  • Scans an existing repository to surface Context Directive Records (CDRs) for team-ai-directives.
  • Generates structured draft entries in .specify/drafts/cdr.md for review and refinement.
  • Supports organizing discoveries into contextual modules (rules, personas, examples, skills) for later mapping.

Quick Start

Run levelup-init to scan your repository and generate initial CDR drafts at .specify/drafts/cdr.md

Frequently Asked Questions about levelup-init

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

FAQPage Schema
How do I document implicit patterns in a brownfield codebase for AI context?

To document implicit patterns in a brownfield codebase, you scan the repository to identify rules and generate Context Directive Records. This process surfaces implicit directives as structured draft entries for team collaboration and codebase analysis.

What are Context Directive Records and how do they map codebase modules?

Context Directive Records are structured documents capturing implicit codebase patterns and organizing discoveries into contextual modules like rules, personas, and skills. They map multiple modules into sub-systems to guide codebase analysis and team AI directives.

Do I need a .specify directory to scan my repository for team AI directives?

Yes, a ready .specify directory in your project root is required. The scanning process uses this directory structure to output generated Context Directive Records directly into .specify/drafts/cdr.md for subsequent review and refinement.

How do I start automating context directive discovery for an existing project?

You start automating context directive discovery by running a brownfield scan workflow against your repository. This automatically surfaces team AI directives and generates initial CDR drafts at .specify/drafts/cdr.md in your project root.

What is the best way to organize discovered rules and personas in a brownfield codebase?

The best way to organize discovered rules and personas is mapping them into contextual modules during the CDR generation process. This structures discoveries into categories like rules, personas, examples, and skills for later subsystem mapping.