Elicit intent and constraints from underspecified product requests into structured specs.
npx skills add https://github.com/chriswch/praxis --skill clarifying-intent
Please help me install this Agent Skill. Skill: clarifying-intent Source: https://github.com/chriswch/praxis/tree/main/skills/clarifying-intent Command: npx skills add https://github.com/chriswch/praxis --skill clarifying-intent
Underspecified requests from stakeholders lead to misaligned scope and wasted effort; this skill guides teams to a shared understanding by eliciting intent, constraints, unknowns, risks, and success criteria to produce precise artifacts.
Provide a vague requirement and the skill will ask targeted questions and generate a Feature Brief or Story-Level Behavioral Spec.
High-intent search queries and answers about installing and using this skill.
To turn vague product requests into actionable specs, you provide the raw requirement to elicit intent, constraints, and risks, generating a structured Story-Level Behavioral Spec with Given/When/Then acceptance criteria for shared understanding.
The best way to clarify underspecified requirements for large features is to triage the input and generate a Feature Brief, which captures goals, unknowns, and constraints to hand off to downstream slicing-stories workflows.
Writing a story spec that reduces ambiguity involves eliciting success criteria and constraints from underspecified tasks, directly producing a Story-Level Behavioral Spec with structured Given/When/Then acceptance criteria and handoff notes.
Yes, you can use this approach for both large feature briefs and single tasks, as it triages input scale to output either a Feature Brief for slicing-stories or a direct Story-Level Behavioral Spec with acceptance criteria.
You should generate a Feature Brief instead of a Story-Level Behavioral Spec when the input is a large feature idea requiring slicing, whereas single smaller tasks directly produce a Story-Level Behavioral Spec with Given/When/Then criteria.
MazenMradTranslate vague business needs into actionable product requirements and market research.
FernanSuozaGenerate US-* and HUS-* backlog stories with dependencies and acceptance criteria.
AlteriomBreak down complex tasks into interdependent subtasks with verification criteria.
suwandreCapture requirements using structured user stories with acceptance criteria.
