Receber por email
← Voltar para o catálogo

when-gathering-requirements-use-interactive-planner

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

367estrelas
Atualizado há 4 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add aiskillstore/marketplace

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/when-gathering-requirements-use-interactive-planner/svg)](https://www.skillteca.com.br/skills/when-gathering-requirements-use-interactive-planner)

Skills relacionadas

Ver todas de Segurança →

Alerta por categoria

Receba novas skills de Segurança toda segunda

1 email curto, só com as skills novas de Segurança. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

  1. Ask open, clear questions
  2. Provide descriptive options
  3. Use multi-select for priorities
  4. Document all responses
  5. Validate with stakeholders
  6. Create actionable plans

Workflow Summary

Duration: 15-30 minutes

Deliverables:

  • Requirements specification
  • Technical architecture
  • Action plan
  • Validation report
Compartilhar X LinkedIn