Clarify ambiguous feature requests into structured requirements documents.
npx skills add https://github.com/linenoize/topia --skill idea-linenoize
Please help me install this Agent Skill. Skill: idea Source: https://github.com/linenoize/topia/tree/main/skills/idea Command: npx skills add https://github.com/linenoize/topia --skill idea-linenoize
This Skill prevents AI coding agents from jumping into implementation before the problem is understood. It turns vague feature requests into clear requirements so teams avoid building the wrong thing, missing constraints, or skipping important edge cases.
Use the idea skill to turn a vague feature request into a structured requirements document before any code is written.
High-intent search queries and answers about installing and using this skill.
Requirement elicitation for a vague feature request requires structured questioning to identify the target user, desired outcome, underlying purpose, and applicable constraints. This process clarifies ambiguous requests by scoring ambiguity and discovering hidden requirements before any code is written.
Defining scope and acceptance criteria for product features involves separating in-scope work from out-of-scope ideas and checking for contradictions. This structured approach surfaces hidden requirements and produces implementation-ready artifacts for downstream planning and build steps.
To stop AI coding agents from rushing into implementation, use a structured requirement clarification skill that intercepts vague requests. It enforces focused questioning, scope boundary definition, and risk control to ensure the problem is fully understood before generating code.
Requirement elicitation supports product features, integrations, greenfield work, and refactors. It captures user intent, scope boundaries, and constraints across all these contexts, ensuring that the specific objectives and limitations of each task type are properly documented.
A requirements document for handoff to planning should include clarified requirements, defined scope boundaries, and structured acceptance criteria. It must also surface hidden requirements and resolve contradictions to produce an implementation-ready artifact for the build phase.
avav25Convert raw feature ideas into structured PRDs with goals, user stories, and acceptance criteria.
xiaoweidotnetDecompose software requirements into executable tasks with acceptance criteria and dependency mapping.
OmexITConvert PRD or design docs into epics, tickets, and acceptance criteria.
tuandzungClarify user ideas into detailed specifications via Socratic questioning.
