speckit-adlc-levelup-skills

Convert accepted CDRs into SKILL.md files with .skills-entry.json entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This metadata-driven Skill enables teams to convert accepted CDRs into structured, reusable skills ready for the Level Up workflow, accelerating discovery-to-implementation cycles.

Core Features & Use Cases

  • Automates extraction of input context to generate a new skill draft from accepted CDRs
  • Supports four-part anatomy generation for advanced executable standards when needed
  • Produces a SKILL.md, optional references, and a .skills-entry.json fragment for integration with team-ai-directives
  • Validates skill structure and helps prepare the skill for activation via /levelup.implement
  • Serves as a repeatable template for packaging similar CDRs into consistent skills across projects

Quick Start

Provide the desired skill identifier (CDR ID, skill name, or topic) to begin drafting a new skill from accepted modules.

Frequently Asked Questions about speckit-adlc-levelup-skills

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

FAQPage Schema
How do I convert accepted CDRs into executable AI skills?

To convert accepted CDRs into executable AI skills, you provide the CDR ID or topic to automate the generation of a SKILL.md file, optional references, and a .skills-entry.json fragment for workflow integration.

What is the Level Up workflow for packaging AI agent skills?

The Level Up workflow for packaging AI agent skills is an automated process that extracts accepted CDR context to generate structured skill drafts, ensuring standardized SKILL.md frontmatter and integration fragments for team-ai-directives.

How do I generate a SKILL.md file with correct frontmatter from a CDR?

Generating a SKILL.md file with correct frontmatter from a CDR requires providing the desired skill identifier to the automation tool, which validates the structure and ensures the name and description fields are accurately populated.

Do I need a centralized CDR registry to use automated skill packaging?

Yes, you need a centralized CDR registry to use automated skill packaging, as this process specifically applies to projects maintaining accepted CDRs and requiring standardized skill packaging for AI agents.

What is the best way to prepare a generated skill for activation via team-ai-directives?

The best way to prepare a generated skill for activation via team-ai-directives is to use the packaging tool to validate the skill structure and generate a .skills-entry.json entry, enabling seamless downstream implementation.

Can I include optional references and scripts when packaging CDRs into skills?

Yes, you can include optional references and scripts when packaging CDRs into skills, as the generation process supports creating a four-part anatomy with optional references, scripts, and assets alongside the core SKILL.md file.