requirement-study

Requirement Study

Purpose

Transform any input (rough notes, conversation transcripts, feature requests, existing documents) into structured, actionable software requirements. Produces a requirements document that any development team can use to plan and build.

When to Use

• User asks to "study requirements" or "analyze requirements"
• User provides rough notes/ideas and wants them formalized
• User asks for a PRD (Product Requirements Document)
• User wants to extract requirements from an existing document
• User asks "what do we need to build for X?"
• User wants to validate completeness of existing requirements

When NOT to Use

• User wants implementation details (use implementation-sketch instead)
• User wants a presentation (use deck-creator instead)
• User is asking about deployment/ops (use remote-ops instead)

Inputs

Required:

• Source material — the raw input to derive requirements from (document, notes, conversation, or verbal description)

Optional:

• Target audience — who will read this requirements doc?
• Scope constraints — any known boundaries or limitations
• Existing requirements — if this is a refinement of existing work
• Template preference — if the user's org has a standard format

Process

Step 1: Preflight Tooling Check

Run a non-blocking Mermaid check for future diagram generation:

if command -v mmdc >/dev/null 2>&1; then
  mmdc --version
else
  echo "mmdc not installed; continue with text/Markdown diagrams and add TODO entry"
fi

If mmdc is missing, add a task to agent.todo.md under Next or Blocked.

Interaction Protocol (Mandatory)

For all substantive responses while running this skill:

• Include Stage: Gx <name> and Next: <immediate next step>
• At each gate transition, ask 2-4 decision-oriented questions before advancing
• Challenge weak assumptions and propose stronger alternatives with rationale

Step 2: Understand the Domain

Read the source material completely. Identify:

• The domain/industry context
• Key stakeholders mentioned
• The problem being solved
• Any existing system or process being replaced/enhanced