Requirements Risk Analyser

An AI-powered requirements risk analysis pipeline built with TypeScript, Claude API, and MCP.

Finds gaps, ambiguities, and missing acceptance criteria in user stories and PRDs — before a single line of code is written.

Architecture

Three specialised agents run in sequence:

1. Agent 1 — Requirements Analyst: Extracts structured data from raw requirement text — acceptance criteria, user roles, business rules, third-party dependencies, integrations, and data fields

2. Agent 2 — Risk Identifier: Analyses the structured requirement and identifies gaps across 10 risk categories with HIGH / MEDIUM / LOW severity

3. Agent 3 — Report Generator: Produces a quality score /100, a markdown risk report, and posts a comment on the Jira ticket if applicable

Related MCP server: Gigaspec

Risk Categories

MCP Tools

• analyse_requirement — full 3-agent pipeline (file or Jira input)

• extract_requirements — Agent 1 only

• identify_risks — Agent 2 only

• get_risk_report — read last generated report

Tech Stack

• TypeScript + Node.js

• Anthropic Claude API (Sonnet 4.6 + Haiku 4.5)

• Ollama (local LLM support — toggle via USE_OLLAMA)

• Model Context Protocol (MCP) SDK

• Jira REST API v3

Setup

git clone https://github.com/abchahal/requirements-risk-analyser.git
cd requirements-risk-analyser
npm install
cp .env.example .env
# Add your ANTHROPIC_API_KEY to .env

Running the pipeline

Via terminal

# Analyse input/requirement.md
npm run pipeline

# Analyse a Jira ticket
npm run pipeline -- --jira PROJ-123

# Analyse inline text
npm run pipeline "As a user I want to reset my password..."

Via Claude Desktop / Claude Code

Analyse the requirement in input/requirement.md

Analyse Jira ticket PROJ-123 for requirement risks

Input

Output

output/
├── risk_report.md          ← full risk report with score
└── archive/
    └── 2025-xx-xx/
        └── risk_report.md  ← previous runs archived automatically

Model Strategy

MCP Setup via CLI

Step 1 — Update start-mcp.bat with your path

@echo off
cd /d "C:\path\to\requirements-risk-analyser"
node --loader ts-node/esm src/server.ts

Step 2 — Register the MCP server

claude mcp add -s user requirements-risk-analyser "C:\path\to\requirements-risk-analyser\start-mcp.bat"

Step 3 — Verify

claude mcp get requirements-risk-analyser

Switching between Ollama and Claude API

# Claude API
USE_OLLAMA=false
ANTHROPIC_API_KEY=sk-ant-...

# Ollama
USE_OLLAMA=true
OLLAMA_MODEL=qwen2.5-coder:7b

Restart MCP server after changing .env.

Environment Variables