skills.rest
ttmouse
ttmouseCOMMUNITY
Explore all skills by this author →
𝕏@ttmouseGitHub

requirements-clarifier

Classifies request types and generates structured Definition Cards with validation plans.

35|10|Updated Dec 29, 2025
Search Tags:#requirements#validation#clarification#scope management#project definition#ask analysis
One-click install
npx skills add https://github.com/ttmouse/skills --skill requirements-clarifier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-clarifier
Source: https://github.com/ttmouse/skills/tree/main/requirements-clarifier
Command: npx skills add https://github.com/ttmouse/skills --skill requirements-clarifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill transforms ambiguous or underspecified requests into clear, actionable definitions, ensuring that projects are well-defined, executable, and verifiable from the outset.

Core Features & Use Cases

  • Request Classification: Identifies the type of ask (Delivery, Diagnosis, Decision, Research) to tailor the clarification process.
  • Structured Definition: Creates a concise "Definition Card" using a 6-slot framework (Goal, Audience/System, Scope, Constraints, Inputs, Acceptance).
  • Gap Identification: Pinpoints missing information and generates a minimal set of targeted questions.
  • Default Assumptions: Provides sensible defaults to keep projects moving when information is scarce.
  • Validation Planning: Outlines a low-cost plan to validate the defined requirements.
  • Use Case: A stakeholder asks for "a new feature for the app." This Skill will prompt for details, define the feature's scope, identify what's needed, and ask specific questions to clarify requirements before development begins.

Quick Start

Use the requirements clarifier skill to clarify the request: "We need a new dashboard for sales data."

Frequently Asked Questions about requirements-clarifier

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

FAQPage Schema
How do I clarify ambiguous project requirements before development starts?▼

Clarifying ambiguous project requirements involves classifying the ask type and defining scope, constraints, and acceptance criteria using a structured Definition Card. This ensures requests are actionable and verifiable before execution begins.

What is the best way to define project scope when stakeholder requests are underspecified?▼

Defining project scope with underspecified requests requires identifying gaps, generating minimal targeted questions, and applying sensible default assumptions. This approach keeps projects moving while ensuring the defined scope remains verifiable.

How do you identify missing information and gaps in a feature request?▼

Identifying missing information in a feature request requires classifying the ask type and mapping inputs against a structured 6-slot Definition Card. This process instantly pinpoints gaps to generate targeted clarification questions.

Can I use default assumptions for scope management when stakeholder information is scarce?▼

Default assumptions can be used for scope management when stakeholder information is scarce. The system provides sensible defaults to keep projects moving while simultaneously outlining a low-cost validation plan.

How do I create a validation plan for actionable project definitions?▼

Creating a validation plan for actionable project definitions involves outlining a low-cost approach to verify the defined requirements. This ensures the finalized request is executable and meets the established acceptance criteria.

Does request classification help with diagnosing project definition issues?▼

Request classification helps with diagnosing project definition issues by identifying the ask type, whether Delivery, Diagnosis, Decision, or Research. This tailored classification ensures the clarification process targets the correct scope.

Related Skills

Explore More Product & Management Skills→
andreaswasitaandreaswasita
33

clarify-the-ask

Restates ambiguous requests with audience, decision, and deliverables before drafting.

Community
Basic
Adelie-SquadAdelie-Squad
17

idea-refiner

Refine vague ideas into executable concepts with structured deliverables.

Official
Advanced
ngocsangyemngocsangyem
14

meow:plan-creator

Draft gate-driven planning documents with YAML frontmatter and acceptance criteria for MeowKit implementations.

Community
Advanced
hitoshisekihitoshiseki

aiox-sm

Automate scrum workflows including user story creation from product requirements documents.

Community
Advanced