vague
Vague: Requirement Clarification
Transform vague requirements into precise, actionable specifications through hypothesis-driven questioning.
When to Use
- Ambiguous feature requests ("add a login feature")
- Incomplete bug reports ("the export is broken")
- Underspecified tasks ("make the app faster")
For strategy/planning blind spot analysis, use unknown. For content-vs-form reframing, use metamedium.
Core Principle: Hypotheses as Options
Use AskUserQuestion for clarification. Do not ask open-ended free-text questions when options can represent plausible hypotheses.
- Bad:
What kind of login do you want? - Good:
OAuth / Email+Password / SSO / Magic link
More from october-academy/agent-plugins
sync
Quick remote sync shortcut. Use when user says "/sync", "동기화", "pull", "git pull", or wants to pull latest changes from remote. Defaults to pulling from origin main.
1.2Kinterview-spec
Start iterative requirement clarification loop. Use this skill when the user has a vague requirement and wants to clarify it through structured questioning. Transforms unclear requirements into precise, actionable specifications.
18ship
Team-orchestrated implement → verify → fix → archive cycle
16frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
16wrap
Session wrap-up workflow. Use when user asks to "wrap up session", "end session", "/wrap", or wants to analyze completed work before ending.
15unknown
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "what am I missing", "뭘 놓치고 있지", "전략 점검", "가정 점검", "quadrant analysis". For requirement clarification use vague; for content-vs-form reframing use metamedium.
14