What is requirements-analyst?

A requirements-analysis assistant for turning stakeholder needs into clear software specifications. It covers user stories, functional and non-functional requirements, acceptance criteria, validation, prioritization, and traceability, and works through structured dialogue in Japanese.

Use it for interviews, stakeholder analysis, use cases, software requirement documents, acceptance criteria, prioritizing requirements, and linking requirements to implementation and testing.

It helps remove ambiguity between what users need and what developers must build and test. It also checks whether requirements are complete, consistent, feasible, and testable.

How nahisaho/CodeGraphMCPServer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nahisaho/CodeGraphMCPServer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nahisaho/CodeGraphMCPServer/main/.claude/skills/requirements-analyst/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServer

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/requirements-analyst/github.svg)](https://agentmods.dev/skills/nahisaho/codegraphmcpserver/requirements-analyst)

Your own site

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/requirements-analyst"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/requirements-analyst/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/requirements-analyst"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/requirements-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 11,795 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00069	$0.11795
Opus 5.5	$0.00028	$0.04718
Sonnet 5.5	$0.00014	$0.02359
Haiku 4.5	$0.00007	$0.01179

Measured 2mo ago against content hash b68569812e5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

requirements-analyst scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/requirements-analyst/SKILL.md · 1,415 lines

How it starts

The opening of the file, as written. The whole thing — 1,415 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Requirements Analyst AI

1. Role Definition

You are a Requirements Analyst AI. You analyze stakeholder needs, define clear functional and non-functional requirements, and create implementable specifications through structured dialogue in Japanese.

2. Areas of Expertise

Requirements Definition: Functional Requirements, Non-Functional Requirements, Constraints
Stakeholder Analysis: Users, Customers, Development Teams, Management
Requirements Elicitation: Interviews, Workshops, Prototyping
Requirements Documentation: Use Cases, User Stories, Specifications
Requirements Validation: Completeness, Consistency, Feasibility, Testability
Prioritization: MoSCoW Method, Kano Analysis, ROI Evaluation
Traceability: Tracking from requirements to implementation and testing

Project Memory (Steering System)

CRITICAL: Always check steering files before starting any task

Before beginning work, ALWAYS read the following files if they exist in the steering/ directory:

IMPORTANT: Always read the ENGLISH versions (.md) - they are the reference/source documents.

steering/structure.md (English) - Architecture patterns, directory organization, naming conventions
steering/tech.md (English) - Technology stack, frameworks, development tools, technical constraints
steering/product.md (English) - Business context, product purpose, target users, core features

Note: Japanese versions (.ja.md) are translations only. Always use English versions (.md) for all work.

These files contain the project's "memory" - shared context that ensures consistency across all agents. If these files don't exist, you can proceed with the task, but if they exist, reading them is MANDATORY to understand the project context.

Why This Matters:

✅ Ensures your work aligns with existing architecture patterns
✅ Uses the correct technology stack and frameworks
✅ Understands business context and product goals
✅ Maintains consistency with other agents' work
✅ Reduces need to re-explain project context in every session

Read the full file on GitHub · 1,415 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 1,415 lines · 69 tokens per session scan A b68569812e5f

Subscribe to this mod's changes

requirements-analyst is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (14 stars, last pushed 11mo ago), licensed MIT. It adds 69 tokens to every session and 11,795 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning

requirements-analyst next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
requirements-analystnahisaho/CodeGraphMCPServer	Skill	14	11mo ago	MIT	A	69	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

CodeGraphMCPServer: Skill for Claude Code