yellinzero/aico
Overview
This skill resolves requirement ambiguities through a structured, one-question-at-a-time approach. It prevents overwhelming stakeholders by asking a single focused question per message, offering recommended options and the reasoning behind each choice. The goal is to surface blocking decisions so development can proceed with clear acceptance criteria.
How this skill works
The skill scans project context and requirement docs to identify ambiguous items and categorizes them by scope, behavior, data, edge cases, or error handling. For each ambiguity it poses exactly one multiple-choice question with a recommended option and concise reasoning. It limits sessions to a maximum of five questions and records answers to update documentation immediately.
When to use it
- When a user runs /pm.clarify or requests clarification in chat
- If a requirement contains conflicting or missing details
- When stories lack acceptance criteria or have unclear behavior
- If stakeholders say 'unclear', 'not sure what this means', or 'confused about'
- Before development begins and information gaps block progress
Best practices
- Ask only one focused question per message to avoid cognitive overload
- Prioritize blocking issues first: scope and security, then UX and technical details
- Provide 2–3 clear options for each question and state trade-offs
- Always include a recommended option and short reasoning to guide decision-making
- Document each resolved ambiguity immediately in project docs
Example use cases
- Clarifying whether a feature includes admin-only controls or is available to all users
- Deciding expected behavior for ambiguous edge cases (e.g., empty inputs or timeouts)
- Choosing between data retention durations when requirements omit storage rules
- Resolving conflicting acceptance criteria between product and engineering
- Filling gaps in stories so QA can write deterministic tests
FAQ
Up to five questions per clarification session, with only one question asked at a time.
What format do questions use?
Each question is multiple choice with a short context quote, ambiguity description, options with implications, and a recommended option with reasoning.
16 skills
This skill guides requirement clarification by asking one focused question at a time, offering recommended options and reasoning to prevent overload.
This skill creates a single story-task file for a given PM story, ordered by layers and ready for backend implementation.
This skill converts requirements into well-structured user stories with acceptance criteria and saves them to docs/reference/pm/stories.
This skill defines clear, testable acceptance criteria using Given/When/Then to guide QA and ensure verifiable completion.
This skill converts PRD or story into complete page and component designs with ASCII layouts, interaction flows, and frontend implementation prompts.
This skill executes a plan by dispatching subagents per task, enforcing spec compliance first and quality review second for reliable completion.
This skill initializes the PM constitution by guiding you through setup questions and generating the project document.
This skill provides structured code reviews to catch correctness, security, performance, and readability issues early and before merging.
This skill guides you through one-question-at-a-time brainstorming to transform vague ideas into clear, actionable product concepts.
This skill initializes the frontend environment by generating a design system and constraints documentation from templates.
This skill generates atomic, step-by-step backend task plans with TDD tests, exact code, and verification commands.
This skill extracts design tokens from a reference site or screenshot and generates a complete design-system.md for your project.
This skill creates isolated git worktrees for feature development, auto-detects setup, verifies gitignore, and runs baseline tests to ensure a clean start.
This skill delivers a structured competitor analysis with feature matrices, strengths/weaknesses, and actionable recommendations to guide product strategy.
This skill verifies frontend and backend story tasks are complete and updates acceptance criteria by converting all pending checkboxes to completed.
This skill defines clear, testable Given/When/Then acceptance criteria from user stories to ensure verifiable test cases.
