Identify ambiguous goal elements and output WHAT, WHY, and WHERE slots.
npx skills add https://github.com/FRIKKern/doey --skill doey-clarify
Please help me install this Agent Skill. Skill: doey-clarify Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-clarify Command: npx skills add https://github.com/FRIKKern/doey --skill doey-clarify
Inline clarification loops sharpen vague goals before task creation, preventing misalignment and wasted effort.
Provide a vague goal in the Boss pane and run the clarify skill to obtain a clarified, actionable goal.
High-intent search queries and answers about installing and using this skill.
Clarifying ambiguous goals before task creation requires identifying missing scope elements inline. This Skill extracts the WHAT, WHY, and WHERE slots from a vague goal by running a concise interview directly within the Boss pane, preventing misalignment without spawning new interfaces.
Inline user interviewing for goal definition is a targeted clarification mechanism that asks up to three rounds of questions within the existing workspace. It identifies vague goal elements and extracts specific parameters to crystallize scope before outputting a single actionable goal block.
Extracting WHAT, WHY, and WHERE slots from a planning requirement involves running a targeted clarification loop. The Skill analyzes the ambiguous goal, questions the user to elicit missing details, and maps the responses into these three defined slots for precise task formulation.
Inline clarification loops for task creation run entirely within the Boss pane without opening new windows or spawning new teams. This lightweight workflow keeps the original context intact, making it suitable for users who need to maintain their workspace state during goal definition.
The maximum number of question rounds allowed during goal clarification is strictly three. The Skill enforces a hard limit of up to three AskUserQuestion rounds and automatically stops the interview process once the goal is sufficiently clarified to prevent excessive questioning.
The best way to refine vague requirements into an actionable task formulation is through structured slot extraction. By applying targeted questioning to identify the WHAT, WHY, and WHERE, this approach outputs a single clarified-goal block ready for downstream planning tools.
CANTAGESTUDIODefine refactoring session boundaries with goals, scope, and success criteria.
FRIKKernCreate and dispatch tasks from natural-language goals using doey commands.
FRIKKernTransform natural-language goals into structured Doey task packages with .task and .json files.
martinffxConduct discovery interviews to define feature scope and requirements.
