How does the Requirements Clarifier help avoid 'wrong work'?

It detects when a prompt is missing critical context—like scope, constraints, or environment details—and pauses implementation until those points are clarified.

Can I tell Claude to ignore the questions and just code?

Yes. If you explicitly ask to proceed, the skill will list its assumptions for your confirmation before starting the work.

What kind of questions does it ask?

It focuses on 'must-have' info like project scope, compatibility targets, edge cases, and safety risks (e.g., data migrations).

Does this skill work automatically?

Based on its configuration, it is designed to be invoked when clarity is needed, ensuring it doesn't interrupt straightforward tasks.

Will this skill make my workflow slower with too many questions?

No, it is designed for efficiency. It limits itself to 1-5 scannable questions and offers 'fast-path' defaults so you can approve a plan with a single word.

Requirements Clarifier

Name: Requirements Clarifier
Author: prateek

byprateek

生産性とワークフロー

Ensures project requirements are fully understood by prompting for specific clarifications before code implementation begins.

概要

The Requirements Clarifier skill optimizes the AI development workflow by identifying underspecified requests and pausing execution to ask critical clarifying questions. It prevents wasted effort and incorrect implementations by focusing on defining objectives, scope, constraints, and success criteria through structured, low-friction multiple-choice options. By enforcing a 'clarify-then-act' workflow, it ensures that every line of code written aligns perfectly with the user's technical environment and functional expectations.

主な機能

Generates structured, multiple-choice questions to minimize response friction.
0 GitHub stars
Identifies ambiguous or underspecified development requests automatically.
Enforces a pause on high-risk actions until critical requirements are defined.
Provides 'fast-path' defaults allowing users to skip detailed configuration.
Restates confirmed requirements and assumptions before starting implementation.

ユースケース

Validating project scope and 'definition of done' before starting major refactors.
Refining vague feature requests into actionable, scoped development plans.
Setting technical constraints like versioning and style guides for new components.

概要

主な機能

Generates structured, multiple-choice questions to minimize response friction.
0 GitHub stars
Identifies ambiguous or underspecified development requests automatically.
Enforces a pause on high-risk actions until critical requirements are defined.
Provides 'fast-path' defaults allowing users to skip detailed configuration.
Restates confirmed requirements and assumptions before starting implementation.

ユースケース

Validating project scope and 'definition of done' before starting major refactors.
Refining vague feature requests into actionable, scoped development plans.
Setting technical constraints like versioning and style guides for new components.