adlc-spec-clarify

Generate targeted clarification questions and encode answers into feature specs.

Updated Apr 21, 2026

Search Tags:#workflow #architecture #specification #clarification #governance #spec plan

Ready to run

npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-spec-clarify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: adlc-spec-clarify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/adlc-spec-clarify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill adlc-spec-clarify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

Core Features & Use Cases

Clarification generation: Proposes up to five targeted questions to resolve ambiguity in specifications.
Three-pillar validation: Validates specification completeness, constitution alignment, and architecture compatibility.
Spec augmentation: Applies accepted clarifications back into the spec as atomic updates.

Quick Start

Provide an initial Mission Brief in the active spec and run the clarification workflow to generate and apply up to five clarifying questions.

Frequently Asked Questions about adlc-spec-clarify

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

FAQPage Schema

How do I clarify underspecified feature specifications before planning?▼

To clarify underspecified feature specifications, you can generate up to five targeted clarification questions and encode the accepted answers back into the spec as atomic updates, ensuring completeness before the planning phase.

What is the best way to validate a mission brief for spec completeness and architecture alignment?▼

Validating a mission brief requires performing three-pillar checks: verifying specification completeness, confirming constitution alignment, and ensuring architecture compatibility before generating a prioritized clarifications queue.

Can I use this specification clarification workflow with any spec-kit project?▼

This specification clarification workflow specifically applies to spec-kit projects utilizing the .specify workflow, requiring an initial Mission Brief in the active spec to generate and apply clarifying questions.

How do I resolve ambiguity in software architecture specifications?▼

Resolving ambiguity in software architecture specifications involves generating a prioritized clarifications queue of up to five targeted questions, recording accepted answers, and writing atomic updates directly into the spec.

Does the spec clarification process limit the number of questions generated?▼

Yes, the spec clarification process limits generation to a maximum of five targeted questions per specification to resolve underspecified areas efficiently without overwhelming the workflow.

Why does specification governance require clarifications before a plan is created?▼

Specification governance requires clarifications before planning to ensure mission-brief validation and three-pillar alignment, preventing architectural drift by encoding resolved ambiguities directly into the spec.