levelup-clarify

Validate and refine Context Directive Records in .specify/drafts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill resolves ambiguity in discovered or proposed Context Directive Records (CDRs) by guiding users through a structured validation and refinement process, ensuring project documentation remains consistent and actionable.

Core Features & Use Cases

  • Interactive Validation: Systematically reviews CDRs against a quality checklist including scope, evidence, and module path validity.
  • Gap Identification: Automatically detects missing context or potential conflicts with existing team directives.
  • Use Case: When a team discovers multiple new architectural patterns, use this skill to clarify which are project-specific versus team-wide, ensuring only high-quality directives are accepted for implementation.

Quick Start

Run the levelup-clarify skill to review and refine all pending CDRs in the current repository.

Frequently Asked Questions about levelup-clarify

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

FAQPage Schema
How do I validate architectural directives for consistency and scope?

To validate architectural directives, use an interactive refinement process that systematically reviews Context Directive Records against a quality checklist, automatically detecting missing context and resolving scope or validity gaps.

What is the best way to resolve ambiguity in project documentation?

Resolving ambiguity in project documentation involves systematically reviewing pending drafts and cross-referencing them against team-wide directives to identify conflicts, ensuring only high-quality and actionable architectural patterns are accepted.

Do I need a spec-kit project structure to refine context directive records?

Yes, you need a spec-kit project structure to refine context directive records. The validation process requires this setup to access pending drafts and team-ai-directives for cross-reference validation.

How do I check if discovered architectural patterns are project-specific or team-wide?

To check if discovered architectural patterns are project-specific or team-wide, run a validation skill that cross-references pending directives against existing team-ai-directives to clarify scope and resolve content gaps.

Why does context directive validation fail when team-ai-directives are missing?

Context directive validation fails without team-ai-directives because the cross-reference checking mechanism relies on them to detect conflicts, verify module path validity, and ensure architectural completeness across the project.