pm-requirement

Derive atomic, testable requirements with acceptance criteria from feature descriptions.

Updated Oct 17, 2025
One-click install
npx skills add https://github.com/x85446/claudecodetricks --skill pm-requirement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-requirement
Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-requirement
Command: npx skills add https://github.com/x85446/claudecodetricks --skill pm-requirement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Derive atomic, testable requirements from features to enable precise verification and traceability.

Core Features & Use Cases

  • Converts complex features into small, testable requirements with title, description, and acceptance criteria.
  • Supports iterative refinement through interactive modes and versioning to track changes over time.

Quick Start

Feed a feature description to the system and require the AI to produce a set of atomic, testable requirements ready for implementation.

Frequently Asked Questions about pm-requirement

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

FAQPage Schema
How do I derive testable requirements from features for precise verification?

To derive testable requirements from features, you feed a feature description into the system to generate atomic requirements containing a title, description, and acceptance criteria for precise verification.

What are atomic requirements in product management and when do I need them?

Atomic requirements in product management are small, testable units converted from complex features. You need them to enable precise verification, establish traceability, and prepare clear implementation targets.

Can I use interactive iteration to refine acceptance criteria during requirement generation?

Yes, you can iteratively refine acceptance criteria during requirement generation using interactive modes that support human approval, tracking changes over time with versioning and base_version alignment.

What is the best way to break down complex product features for development teams?

The best way to break down complex product features is to crawl feature descriptions and generate small, testable requirements with titles, descriptions, and acceptance criteria ready for implementation.

Do I need any specific dependencies or environment setup to generate acceptance criteria?

No specific dependencies or environment setup are required to generate acceptance criteria. You simply provide a feature description to the system to produce atomic, testable requirements.

Why does my product requirement lack traceability during the verification phase?

Your product requirement lacks traceability because it is not broken down into atomic, testable units with defined acceptance criteria, a structure necessary to enable precise verification and version tracking.