when-gathering-requirements-use-interactive-planner
Gather project requirements interactively
Gathering project requirements can be time-consuming and incomplete when done through linear conversation. This skill uses Claude Code's interactive question tool to systematically collect all necessary information through structured multi-select questions, ensuring nothing is missed.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"when-gathering-requirements-use-interactive-planner" ์ฌ์ฉ ์ค์ ๋๋ค. Use interactive planner to gather requirements for a new e-commerce website
์์ ๊ฒฐ๊ณผ:
- โ Project goals documented
- โ Technical stack identified
- โ Feature priorities defined
- โ Timeline and milestones set
- โ Stakeholder approval obtained
- โ Action plan created with 12 tasks
"when-gathering-requirements-use-interactive-planner" ์ฌ์ฉ ์ค์ ๋๋ค. Help me clarify requirements for a mobile app feature
์์ ๊ฒฐ๊ณผ:
- โ User personas identified
- โ Functional requirements mapped
- โ Non-functional requirements documented
- โ Acceptance criteria defined
- โ Technical risks identified
"when-gathering-requirements-use-interactive-planner" ์ฌ์ฉ ์ค์ ๋๋ค. Gather stakeholder requirements for a data pipeline project
์์ ๊ฒฐ๊ณผ:
- โ Data sources documented
- โ Processing requirements specified
- โ Output formats defined
- โ Compliance requirements noted
- โ Resource estimates calculated
๋ณด์ ๊ฐ์ฌ
์์ Pure documentation skill containing only Markdown, YAML, JSON, and Graphviz files. No executable code, network calls, file system access, or command execution. All 18 static findings are false positives: backticks are markdown formatting, version strings were misidentified as crypto algorithms, and URLs are metadata references.
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (7)
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
๐ ํ์ผ ์์คํ ์ก์ธ์ค (1)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Kick off new projects
Systematically gather all stakeholder requirements before project kickoff
Clarify feature requests
Extract detailed technical requirements from vague feature descriptions
Document specifications
Create comprehensive product specifications with clear acceptance criteria
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
I need to gather requirements for a new project. Please use the interactive planner to ask me initial discovery questions about project goals and scope.
Now follow up with detailed technical questions about scale, performance requirements, and technology constraints.
Ask me about timeline expectations, resource constraints, and feature priorities using multi-select options.
Review all gathered requirements with me and create a final specifications document with action plan.
๋ชจ๋ฒ ์ฌ๋ก
- Start with open questions about project goals before diving into technical details
- Use multi-select options for priorities to surface trade-offs early
- Validate requirements with stakeholders before creating the action plan
ํผํ๊ธฐ
- Skipping the discovery phase and jumping directly to technical questions
- Using single-select when multiple priorities should be considered
- Creating action plans without stakeholder validation
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
Which AI tools support this skill?
How long does the full requirements process take?
Can I resume a partially completed session?
Is any user data stored or transmitted?
What if I get stuck or responses are unclear?
How does this compare to manual requirements gathering?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
DNYoussef๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/specialized-tools/when-gathering-requirements-use-interactive-planner์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ