skills.rest
VictorHueni
VictorHueniCOMMUNITY
Explore all skills by this author →
GitHub

spec-use-case

Create and manage software use cases with Cockburn, UML, and Use-Case 2.0 methodologies.

Updated Apr 8, 2026
Search Tags:#methodology#use case#uml#software requirements#use-case 2.0
One-click install
npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill spec-use-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-use-case
Source: https://github.com/VictorHueni/homemade-claude-kit/tree/main/skills/spec-use-case
Command: npx skills add https://github.com/VictorHueni/homemade-claude-kit --skill spec-use-case

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the creation and management of use cases, essential for software requirements definition, ensuring clear, comprehensive, and actionable specifications.

Core Features & Use Cases

  • Use Case Creation: Offers various modes for crafting use cases, including fully-dressed, casual, and slice formats.
  • Methodology Synthesis: Combines Alistair Cockburn's, UML, and Ivar Jacobson's Use-Case 2.0 methodologies.
  • Quality Assurance: Provides a review mode to ensure use cases meet quality standards.

Quick Start

Create a new use case for 'Order Processing' using the fully-dressed mode.

Frequently Asked Questions about spec-use-case

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

FAQPage Schema
How do I write use cases for software requirements using UML and Use-Case 2.0?▼

Use cases for software requirements are structured here by combining UML, Cockburn, and Use-Case 2.0 methodologies, offering fully-dressed, casual, and slice formats to ensure clear and actionable specifications.

What is the difference between fully-dressed and casual use case formats?▼

Fully-dressed use cases provide highly detailed, step-by-step specifications for software requirements, whereas casual use cases offer a lighter, more brief format for scenarios needing less formal documentation.

Do I need project personas and FBS before creating use cases?▼

Yes, you need project personas and a Feature Breakdown Structure (FBS) to provide essential context before creating use cases, ensuring the generated specifications align with your software requirements.

How can I review use cases to ensure they meet quality standards?▼

You can review use cases to ensure they meet quality standards by using the built-in review mode, which evaluates the generated specifications against the combined Cockburn, UML, and Use-Case 2.0 methodologies.

What is the best way to manage use cases using Cockburn's methodology?▼

The best way to manage use cases using Cockburn's methodology is to synthesize it with UML and Use-Case 2.0 practices, leveraging creation modes and quality review features for comprehensive software requirements.

When should I use use-case slices instead of fully-dressed use cases?▼

You should use use-case slices instead of fully-dressed use cases when you need to break down software requirements into smaller, manageable increments aligned with Use-Case 2.0 practices for iterative development.

Related Skills

Explore More Software Engineering Skills→
VictorHueniVictorHueni

plan-delivery-roadmap

Construct a delivery roadmap from Feature Breakdown Structure, value streams, and personas.

Community
Advanced
sebc-devsebc-dev

to-issues

Convert project plans and specifications into individual issues for issue trackers.

Community
Intermediate
josavicentevwjosavicentevw
1

product-owner

Defines requirements and manages Agile backlogs for product teams.

Community
Basic
faionfaionfaionfaion
4

faion-ba-modeling

Model system requirements with use cases, user stories, BPMN, and ERDs.

Community
Intermediate