adlc-levelup-clarify

Clarify underspecified CDRs through targeted questions and structured decisions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve ambiguities in discovered or proposed CDRs by guiding targeted clarifications, ensuring decisions are complete, consistent, and ready for implementation.

Core Features & Use Cases

  • Sequential clarification workflow: loads pending CDRs, identifies gaps, and processes them one at a time with guided prompts.
  • Quality gate & traceability: validates context, decision, and evidence, recording clarification history for audits.
  • Actionable outcomes: outputs accepted, rejected, or deferred statuses and updates the source CDR file immediately.

Quick Start

Start a clarification session with /levelup.clarify to review pending CDRs and answer one question at a time.

Frequently Asked Questions about adlc-levelup-clarify

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

FAQPage Schema
How do I clarify ambiguities in CDRs before implementation?

To clarify CDR ambiguities, you can run a sequential clarification workflow that loads pending CDRs, identifies gaps, and asks targeted questions one at a time to refine decisions. It validates context, decision, and evidence to ensure decisions are ready for implementation.

What is the best way to track decision clarifications for team directives?

Tracking decision clarifications involves recording the clarification history directly within the CDR file. This provides quality gate traceability for audits by immediately updating the source CDR records with accepted, rejected, or deferred statuses after each decision.

How do I validate CDR quality and completeness for a spec-kit workflow?

Validating CDR quality requires analyzing the draft CDR file alongside team directives to identify underspecified records. The skill checks for complete context, decision, and evidence, then outputs structured guidance to accept, reject, or defer the item.

Can I process multiple CDRs at once during a clarification session?

No, you cannot process multiple CDRs simultaneously. The skill operates in a sequential, one-CDR-at-a-time mode with a session limit. It loads pending records, processes a single CDR with guided prompts, and updates the file immediately before moving on.

Why does my CDR clarification workflow require immediate updates to the source file?

Immediate updates to the source CDR file are required to maintain quality gate traceability and ensure audit readiness. Recording clarifications and actionable outcomes directly in the file prevents data loss and keeps team directives synchronized.