CodeGraphMCPServer: Command for Claude Code

SDD Requirements Command

Create EARS-format requirements specification.

---

Instructions for Claude

You are executing the /sdd-requirements [feature-name] command to create a requirements specification.

Command Format

/sdd-requirements authentication
/sdd-requirements payment-processing
/sdd-requirements user-dashboard

Your Task

Generate a comprehensive requirements specification in EARS format for the specified feature.

---

Process

1. Read Steering Context (Article VI)

IMPORTANT: Before starting, read steering files to understand project context:

# Read these files first
steering/product.md      # Business context, users, goals
steering/structure.md    # Architecture patterns
steering/tech.md         # Technology stack

Extract:

• Target users
• Product goals
• Existing architecture patterns
• Technology constraints

---

2. Gather Requirements

Methods (use as appropriate):

A. Stakeholder Interview (if user is available)

Use AskUserQuestion tool to ask:

• Who are the users of this feature?
• What problem does this solve?
• What are the critical workflows?
• What are the acceptance criteria?
• Are there any constraints (performance, security, compliance)?

B. Research Existing System (brownfield)

• Search for existing implementation: grep -r "{{feature}}" src/
• Read related code
• Identify current behavior
• Document what needs to change (delta spec)

C. Infer from Context

• Analyze steering/product.md for user types
• Review existing requirements docs
• Check for similar features in codebase

---

3. Generate Requirements Document

Use template from templates/requirements.md:

Structure:

# Requirements Specification: {{FEATURE_NAME}}

## Overview

- Purpose
- Scope (in/out)
- Business context (from steering/product.md)

## Stakeholders

[Table of roles]

## Functional Requirements

### REQ-{{COMPONENT}}-001: [Title]

[EARS Pattern - choose appropriate pattern]

**Acceptance Criteria**:

- [Testable criterion 1]
- [Testable criterion 2]

**Priority**: P0/P1/P2/P3
**Status**: Draft
**Traceability**: (leave blank for now)

[Repeat for all requirements]

## Non-Functional Requirements

### REQ-PERF-001: Performance

### REQ-SEC-001: Security

### REQ-SCALE-001: Scalability

### REQ-AVAIL-001: Availability

## Requirements Coverage Matrix

[Initial table - will be filled during design/implementation]