requirements-spec

Convert a confirmed PROJECT.md into a structured SPEC.md with use cases and acceptance criteria.

1|Updated Apr 2, 2026

Search Tags:#planning #architecture #requirements #spec #traceability #acceptance-criteria #use-cases

Ready to run

npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill requirements-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-spec
Source: https://github.com/AnjinMeili/Claude-ITIL-Planner/tree/main/planitil/skills/requirements-spec
Command: npx skills add https://github.com/AnjinMeili/Claude-ITIL-Planner --skill requirements-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert a confirmed PROJECT.md into a structured SPEC.md that defines use cases, acceptance criteria, non-functional requirements, and external dependencies for traceable planning.

Core Features & Use Cases

Produces SPEC.md as a single structured contract containing Use Cases, Feature Acceptance Criteria, Non-Functional Requirements, and External Dependencies, all traceable to PROJECT.md.
Enforces prerequisites: requires a confirmed PROJECT.md and aligns with the Target Audience and Success Metrics defined there.
Provides a SPEC.md.template and reference guidance to standardize the documentation across teams.

Quick Start

Provide a confirmed PROJECT.md and run requirements-spec to generate SPEC.md and its planning artifacts.

Frequently Asked Questions about requirements-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a SPEC.md with acceptance criteria and use cases from a project brief?▼

To generate a SPEC.md with acceptance criteria and use cases, you provide a confirmed PROJECT.md to the requirements-spec process, which converts it into a structured contract defining 3–10 use cases, feature acceptance criteria, non-functional requirements, and external dependencies.

What is the best way to structure non-functional requirements and external dependencies before architecture design?▼

The best way to structure non-functional requirements and external dependencies before architecture design is to consolidate them into a single SPEC.md artifact, ensuring they are directly traceable to the success metrics defined in your PROJECT.md.

How do I ensure traceability between my project success metrics and feature acceptance criteria?▼

To ensure traceability between project success metrics and feature acceptance criteria, you enforce a documented artifact contract where every use case and non-functional requirement in the SPEC.md aligns with the Target Audience and Success Metrics established in the PROJECT.md.

Do I need a confirmed PROJECT.md before planning architecture and defining software specifications?▼

Yes, you need a confirmed PROJECT.md before planning architecture and defining software specifications, because the requirements-spec process enforces this prerequisite to align use cases and non-functional requirements with your project's foundational goals.

Can I use a requirements spec template to standardize use cases and NFRs across multiple teams?▼

Yes, you can use a provided SPEC.md.template and reference guidance to standardize use cases and NFRs across multiple teams, which enforces a uniform artifact contract before design and enables reliable handoffs to architecture planning.

What to do when architecture planning begins and you need to define 3 to 10 use cases for development?▼

When architecture planning begins and you need to define 3 to 10 use cases for development, you run requirements-spec against your confirmed PROJECT.md to produce a structured SPEC.md that covers use cases, acceptance criteria, NFRs, and dependencies.