requirements-documentation

Organize product requirements into a structured repository with templates and traceability.

Updated Aug 23, 2026

Search Tags:#templates #documentation #markdown #requirements #traceability #product-management

Ready to run

npx skills add https://github.com/kirillshilin/instructions --skill requirements-documentation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-documentation
Source: https://github.com/kirillshilin/instructions/tree/main/obsolete/dotgithub/skills/requirements-documentation
Command: npx skills add https://github.com/kirillshilin/instructions --skill requirements-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing and organizing product requirements can be inconsistent, hard to navigate, and difficult to trace across versions and teams. This skill provides a proven structure to standardize documentation, map relationships between requirements, and generate a coherent file layout that scales with the project.

Core Features & Use Cases

Provides a standard template for full requirement documents, a requirements map (hierarchy), and a summary README to give at-a-glance visibility.
Supports organizing files into a folder/file structure (docs/requirements/functional, non-functional, etc.) to improve traceability and collaboration.
Includes best-practice notes on IDs, acceptance criteria, and dependencies to maintain consistency across the repository.

Quick Start

Create a new requirements folder and start populating it with REQ-001.md and related files using the provided templates.

Frequently Asked Questions about requirements-documentation

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

FAQPage Schema

How do I structure product requirements documentation in a repository?▼

You can structure product requirements by generating a folder/file layout within your repository, including a requirements map, summary README, and standardized templates for functional and non-functional documents.

What is a requirements map and how does it help with traceability?▼

A requirements map is a hierarchical structure that links related product requirements together, improving traceability across versions and teams by mapping relationships and dependencies within your documentation repository.

How do I write acceptance criteria for product requirements?▼

Write acceptance criteria for product requirements by using standardized markdown templates that enforce consistent IDs and best-practice notes, ensuring each requirement has clear dependencies and verifiable conditions documented.

Can I use markdown templates to organize functional and non-functional requirements?▼

Yes, you can use markdown templates to organize functional and non-functional requirements, separating them into dedicated folders like docs/requirements/functional to maintain a coherent and scalable file layout for collaboration.

What is the best way to standardize product management documentation across teams?▼

The best way to standardize product management documentation is to apply a reusable structure with consistent requirement IDs, acceptance criteria, and a summary README, ensuring traceability and coherence across versions and teams.

Does organizing product requirements into a file layout work for scaling projects?▼

Yes, organizing product requirements into a structured folder/file layout scales with your project by maintaining consistent IDs, mapping requirement relationships, and providing at-a-glance visibility through a summary README.