clarifying-scenarios
Evaluates whether a user's modernization/rewrite request provides enough scenario context to proceed (e.g., target component library, screenshots, design system for frontend; API contract policy, data migration strategy for backend). Produces a deterministic clarity score, emits the complete question set at once as an on-disk clarification-questions.json (the source of truth for the Q&A round; rendered externally into a webview/markdown, answers come back as a markdown document), and writes a canonical clarification.md artifact consumed by all downstream agents.
Triggers: "clarification gate", "scenario clarification", "elicit missing context", "evaluate prompt completeness", "ask user for screenshots / target library / design system".
NOT for: feature specification (use feature-inventory), planning (use creating-implementation-plan), implementation (use implementing-code), or resolving spec-time [NEEDS CLARIFICATION] markers (those remain owned by feature-inventory).
Pinned to revision a9c9469d86e9, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/clarifying-scenarios/SKILL.md
- skills/clarifying-scenarios/references/kit-backend.md
- skills/clarifying-scenarios/references/kit-frontend.md
- skills/clarifying-scenarios/references/kit-generic.md
- skills/clarifying-scenarios/references/scoring-rubric.md
- skills/clarifying-scenarios/templates/clarification-form.md
- skills/clarifying-scenarios/templates/clarification.md
Every link opens the file at its source, pinned to the revision this page describes.