up-requirements

Capture system requirements into a structured Use Case catalog for UP projects.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: up-requirements
Source: https://github.com/apolosan/unified_process_pi_extension/tree/main/skills/up-requirements
Command: npx skills add https://github.com/apolosan/unified_process_pi_extension --skill up-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures system requirements and defines a Use Case catalog for the Object-Oriented Unified Process, enabling structured analysis and traceability.

Core Features & Use Cases

  • 5W2H analysis before identifying actors or writing use cases to surface gaps, conflicts, and assumptions.
  • Actor discovery & UC classification to map external stakeholders and categorize each feature as <<CRUD>>, <<rep>> or [functional], with optional include/extend relationships.
  • Artifact generation using templates to produce a Use Case Catalog and a Requirements document, saved via provided tooling.
  • Guided workflow from vision to requirements to use-case documentation with artifact persistence.

Quick Start

Load the vision document and run the requirements workflow to generate the Use Case catalog.

Frequently Asked Questions about up-requirements

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

FAQPage Schema
How do I create a Use Case catalog from raw system requirements?

Use Case catalog generation applies 5W2H analysis to surface gaps, discover actors, and classify features as CRUD, reports, or functional processes before producing structured documentation.

What is 5W2H analysis in requirements engineering and when is it needed?

5W2H analysis in requirements engineering surfaces gaps, conflicts, and assumptions before actor identification and use case classification, ensuring structured traceability for Unified Process projects.

How do I classify use cases into CRUD, reports, and functional processes?

Use case classification maps discovered actors to features, categorizing each as CRUD, report, or functional, while defining optional include and extend relationships to structure the catalog.

Does this requirements workflow support the Unified Process for object-oriented projects?

This workflow supports the Object-Oriented Unified Process by capturing system requirements and defining a structured Use Case catalog that enables traceability and upfront requirements analysis.

What is the best way to document business rules during use case identification?

Document business rules by running a guided workflow that captures 5W2H analysis, classifies issues, identifies actors, and generates a Requirements document using predefined templates.

How do I generate a requirements document after identifying use cases?

Generate requirements documents by applying templates to your classified use cases, using provided save commands to persist the final Use Case catalog and Requirements artifacts.