use-case-writer

Convert feature briefs into 13-field Use Case Markdown specifications.

119|46|Updated May 14, 2026
One-click install
npx skills add https://github.com/phucnt-bazone-vietnam/use-case-writer --skill use-case-writer-phucnt-bazone-vietnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-case-writer
Source: https://github.com/phucnt-bazone-vietnam/use-case-writer/tree/main
Command: npx skills add https://github.com/phucnt-bazone-vietnam/use-case-writer --skill use-case-writer-phucnt-bazone-vietnam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IT business analysts and product teams often struggle to convert vague feature descriptions, BRDs, or PRDs into formal Use Case specifications. This Skill provides a structured, repeatable workflow that yields English Markdown artifacts aligned to the standard IT BA 13-field template, improving clarity and traceability.

Core Features & Use Cases

  • 4-step, sequential workflow: Classify input, Scope the UC, Write the UC, and Validate against a 20-point checklist.
  • 4 operating modes: write new, split a feature into a UC list, refine an existing UC, or write a specific section (Normal Course / Alternatives / Exceptions).
  • Enforces Cockburn's scoping rules (coffee-break test, 3 goal levels, system boundary) to ensure user-goal level UCs.
  • Outputs 13-field Markdown artifacts (Actor, Description, Pre/Postconditions, Priority, Frequency, Normal/Alternative Courses, Exceptions, Includes, Special Requirements, Assumptions, Notes).
  • Progressive disclosure: only SKILL.md is always loaded; supporting references/assets are loaded on demand.

Quick Start

Provide a feature description and ask me to write a Use Case from it.

Frequently Asked Questions about use-case-writer

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

FAQPage Schema
How do I convert a feature brief into a formal Use Case specification in Markdown?

To convert a feature brief into a Use Case specification, the Skill applies a 4-step workflow that classifies input, scopes the UC, writes the document, and validates it. It outputs an English Markdown artifact using a standard 13-field template.

What is the standard template for writing a Use Case document for business analysis?

A standard Use Case template for business analysis includes 13 fields: Actor, Description, Preconditions, Postconditions, Priority, Frequency, Normal Course, Alternative Courses, Exceptions, Includes, Special Requirements, Assumptions, and Notes. This Skill enforces this exact structure.

How do I split a large feature into multiple user-goal level Use Cases?

Splitting a large feature into user-goal level Use Cases requires applying Cockburn's scoping rules, including the coffee-break test and system boundary identification. This Skill provides a dedicated operating mode to decompose features into a structured UC list.

Can I refine an existing Use Case or write specific sections like exceptions and alternatives?

Refining an existing Use Case or writing specific sections like Normal Course, Alternatives, and Exceptions is supported through a targeted operating mode. This allows you to update individual parts of the 13-field Markdown artifact without rewriting the entire document.

How do I validate a Use Case document against a quality checklist?

Validating a Use Case against a quality checklist involves running the document through a 20-point validation process. This Skill automatically performs this validation step to ensure your UC meets formal business analysis standards and traceability requirements.

Does this Use Case writer support progressive loading to minimize context usage?

Progressive loading is supported to minimize context usage by only loading the main SKILL.md file by default. Supporting references and assets are loaded on demand during the UC writing workflow when specific analysis context is required.