When gathering requirements use interactive planner

Skill aiskillstore/marketplace/skills/dnyoussef/when-gathering-requirements-use-interactive-planner

Security-audited skills for Claude, Codex & Claude Code. One-click install, quality verified.

Install

npx -y skills add aiskillstore/marketplace --skill when-gathering-requirements-use-interactive-planner

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Use Claude Code's AskUserQuestion tool to gather comprehensive requirements through structured multi-select questions.

SKILL.md

1.7 KB, 349 tokens by cl100k_base, as published. Nobody here has run it

Interactive Requirements Planning SOP

metadata:
  skill_name: when-gathering-requirements-use-interactive-planner
  version: 1.0.0
  category: specialized-tools
  difficulty: beginner
  estimated_duration: 15-30 minutes
  trigger_patterns:
    - "gather requirements"
    - "interactive questions"
    - "requirements gathering"
    - "clarify requirements"
  agents:
    - planner
    - researcher
    - system-architect
  success_criteria:
    - Requirements gathered
    - Specifications documented
    - Stakeholder approval
    - Action plan created

Overview

Use Claude Code's AskUserQuestion tool to gather comprehensive requirements through structured multi-select questions.

Phases

Phase 1: Discover Needs (3-5 min)

Ask initial questions about project goals and scope using AskUserQuestion tool.

Phase 2: Clarify Details (5-10 min)

Follow up with detailed technical and timeline questions.

Phase 3: Structure Requirements (3-5 min)

Organize responses into formal specifications document.

Phase 4: Validate Completeness (2-5 min)

Review with stakeholders and get approval.

Phase 5: Document Specifications (2-5 min)

Create final documentation and action plan.

Best Practices

Ask open, clear questions
Provide descriptive options
Use multi-select for priorities
Document all responses
Validate with stakeholders
Create actionable plans

Workflow Summary

Duration: 15-30 minutes

Deliverables:

Requirements specification
Technical architecture
Action plan
Validation report