use-case

Creates and decomposes structured use case artifacts using Cockburn and Jacobson UC 2.0 methodologies.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/geekatron/jerry-claude-plugin --skill use-case-geekatron
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-case
Source: https://github.com/geekatron/jerry-claude-plugin/tree/main/skills/use-case
Command: npx skills add https://github.com/geekatron/jerry-claude-plugin --skill use-case-geekatron

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns informal stakeholder descriptions into structured, schema-validated use case artifacts that can drive downstream test specification and API contract generation, eliminating ad-hoc requirements writing. ## Core Features & Use Cases - Guided Authoring: Implements Cockburn's 12-step writing process with progressive detail levels from BRIEFLY_DESCRIBED to FULLY_DESCRIBED, including goal-level classification and actor identification. - Use Case Slicing: Decomposes use cases into implementation-ready slices following Jacobson UC 2.0 Activities 2, 4, and 5, with INVEST criteria verification and a five-state slice lifecycle. - Realization Sequences: Produces interaction sequences consumed by downstream /test-spec and /contract-design skills, with all artifacts validated against a JSON schema. - Use Case: Ask it to write a use case for user authentication, elaborate it to Essential Outline level, then slice it into implementation increments with worktracker Story entities. ## Quick Start Ask the assistant to write a use case for user credential validation at USER_GOAL level in the AUTH domain and then slice it into implementation-ready increments.

Frequently Asked Questions about use-case

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

FAQPage Schema
How do I write a use case with Cockburn's methodology?

Invoke the skill with a system capability or actor goal, and the uc-author agent applies Cockburn's 12-step process: identifying goal level, scope, actors, basic flow, preconditions, extensions, and quality indicators. Output is a schema-validated Markdown artifact with YAML frontmatter.

How to decompose a use case into implementation slices?

The uc-slicer agent implements Jacobson UC 2.0 Activities 2, 4, and 5. It identifies slice candidates, applies INVEST criteria, manages a five-state lifecycle from SCOPED to VERIFIED, and produces interaction sequences for contract design.

What detail level is required before slicing a use case?

Slicing requires detail_level of ESSENTIAL_OUTLINE or higher, with a basic flow of 3-9 steps and at least one extension. Artifacts at BRIEFLY_DESCRIBED or BULLETED_OUTLINE are rejected with instructions to elaborate via uc-author first.

Can this skill generate test specifications or API contracts?

No, it only produces use case artifacts. Test specifications are generated by the /test-spec skill and API contracts by /contract-design, both of which consume the artifacts and interaction sequences this skill creates.

When should I not use this use case authoring skill?

Avoid it for BDD test generation, API contract generation, adversarial quality review, or NASA NPR 7123.1D requirements engineering. Those tasks route to /test-spec, /contract-design, /adversary, and /nasa-se respectively.