requirements-elicitation
Gather requirements with structured interviews
Poor requirements lead to project failures and wasted development effort. This skill provides structured question templates and techniques to systematically gather complete, unambiguous requirements from stakeholders through proven elicitation methods.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"requirements-elicitation" ์ฌ์ฉ ์ค์ ๋๋ค. Help me gather requirements for a new customer portal from the marketing team.
์์ ๊ฒฐ๊ณผ:
- Functional Requirements: User registration, profile management, content access, communication preferences
- Non-Functional Requirements: 99.9% uptime, page load under 3 seconds, GDPR compliance
- Priority: Must Have - User registration, profile management
- Priority: Should Have - Communication preferences
- Stakeholder concerns: Data privacy, brand consistency
๋ณด์ ๊ฐ์ฌ
์์ All 25 static findings are false positives. This skill is pure documentation containing only markdown templates for requirements gathering. No executable code, no network calls, no file system access, and no command execution capabilities exist. The scanner incorrectly flagged compliance terminology, markdown formatting syntax, and the FURPS+ model acronym as security patterns.
์ํ ์์ธ
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (7)
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Conduct stakeholder interviews
Use structured question templates to gather complete requirements from stakeholders during discovery phase.
Define MVP scope
Apply prioritization techniques to identify must-have features for minimum viable product releases.
Validate requirements quality
Check gathered requirements against SMART and INVEST criteria before development begins.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Help me conduct a requirements gathering interview. The stakeholder is [role] and we are discussing [project]. Start with open-ended questions to understand their needs.
What are the main functional requirements for [system]? Ask me about user actions, data processing, business rules, and expected outputs.
Help me gather non-functional requirements using the FURPS+ model. Ask me about performance, security, usability, reliability, and supportability needs.
We have gathered [list requirements]. Help me apply the MoSCoW method to prioritize each one as Must Have, Should Have, Could Have, or Won't Have.
๋ชจ๋ฒ ์ฌ๋ก
- Start interviews with open-ended questions before moving to specific details
- Validate understanding by summarizing requirements back to stakeholders
- Use follow-up patterns (specific examples, break down complexity) when answers are vague or incomplete
ํผํ๊ธฐ
- Asking leading questions that suggest expected answers
- Skipping validation questions to confirm understanding
- Accepting requirements without checking for ambiguity or conflicts
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What tools does this skill work with?
How many questions should I ask in one session?
Can I customize the question templates?
Is my interview data stored anywhere?
Why use FURPS+ instead of other NFR frameworks?
How does this differ from requirements management tools?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
DoubleslashSE๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/DoubleslashSE/claude-workflows/tree/main/Plugins/business-analyst/skills/requirements-elicitation์ฐธ์กฐ
main
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md