Requirements gathering and elicitation techniques for business analysis. Use when conducting stakeholder interviews, gathering functional/non-functional requirements, or identifying gaps in requirements.
Provides structured techniques for gathering and analyzing software requirements from stakeholders. Use during stakeholder interviews to ask adaptive questions, extract requirements from documents, and validate gaps using MoSCoW prioritization and SMART criteria.
/plugin marketplace add DoubleslashSE/claude-marketplace/plugin install business-analyst@doubleslash-pluginsThis skill is limited to using the following tools:
question-templates.mdThis skill provides structured techniques for gathering, analyzing, and documenting software requirements from stakeholders and existing systems.
Use predefined question sets organized by category:
Dynamically adjust questions based on:
Extract requirements from existing:
Understand requirements by observing:
What the system must DO:
How the system must BEHAVE:
Limitations on the solution:
Conditions assumed to be true:
High Value + Low Effort = Do First (Quick Wins)
High Value + High Effort = Do Second (Major Projects)
Low Value + Low Effort = Do Later (Fill-ins)
Low Value + High Effort = Don't Do (Time Wasters)
Each requirement should be:
For each stakeholder identify:
| ID | Category | Description | Priority | Status |
|----|----------|-------------|----------|--------|
| FR-001 | Functional | User can login with email | Must | Confirmed |
| NFR-001 | Performance | Page load < 3 seconds | Should | Pending |
As a [role]
I want [capability]
So that [business value]
Acceptance Criteria:
- Given [context]
- When [action]
- Then [outcome]
Business Objective -> Requirement -> User Story -> Test Case
See question-templates.md for structured interview questions.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.