Plugin
ba-zone-user-story-ac-…
Skill Claude AI giúp BA/PO viết User Story và Acceptance Criteria đạt chuẩn INVEST + Given-When-Then, sẵn sàng cho dev estimate và QA viết test case.
1 skill192
@phucnt-bazone-vietnamWriting
Plugin
use-case-writer
use-case-writer is a Claude Code plugin with 1 hand-picked skill, indexed on Flowy in the Writing category.
Plugin Signal42/100Fair
maintained32
capable14
documented100
adopted46
Install
$ npx -y skills add phucnt-bazone-vietnam/use-case-writer --agent claude-code
Stats
152
Stars
57
Forks
Maintained
Maintenance
5mo ago
Last commit
5mo ago
Created
1h ago
Added
What's inside
README
Use Case Writer · BA Zone
English | Tiếng Việt
English
A Claude AI skill that helps IT Business Analysts scope, analyze, and document Use Cases in English Markdown, following the industry-standard 13-field template (Karl Wiegers / IIBA style) with best practices from Alistair Cockburn's Writing Effective Use Cases.
Developed by Phúc NT for the BA Zone — Vietnam's Business Analyst & Product Owner community.
Why this skill?
Writing a high-quality Use Case spec is harder than it looks. BAs commonly struggle with:
- Wrong scope: writing UCs that are too big (entire workflows) or too small (sub-functions like "Verify OTP")
- Vague actors: using "User" instead of specific roles like Learner, Mentor, or HR Manager
- Embedded logic: stuffing if/else and loops into the Normal Course
- Missing failure modes: only writing the happy path
- Confusing Preconditions with Business Rules
This skill enforces the discipline by:
- Scoping first — applying Cockburn's coffee-break test, goal levels, and system boundary rules before writing anything
- Generating sequentially — section by section, stopping for confirmation so issues are caught early
- Validating with a 20-point checklist — every UC is reviewed before handover
Features
- ✅ English Markdown output following the standard 13-field template
- ✅ Sequential workflow — 5 section groups, with confirmation gates between them
- ✅ 4 modes: write new, split feature into UC list, refine existing, or write a specific section
- ✅ Scoping rules based on Alistair Cockburn (coffee-break test, goal levels, one-actor-one-goal-one-session, system boundary)
- ✅ 3 identification techniques for breaking down large features: goal-driven, event-driven, CRUD-driven
- ✅ 20-point quality checklist auto-run before handover
- ✅ Bilingual interaction — chat in Vietnamese or English, produce the UC artifact in English
- ✅ 2 complete EdTech UC examples included as reference (Course Enrollment, Mentor Session Approval)
Repository structure
ba-zone-use-case-writer/
├── SKILL.md # Main workflow (loaded into Claude's context)
├── references/ # Reference docs (loaded on demand)
│ ├── template-guide.md # How to fill each of the 13 fields, with Digital School examples
│ ├── writing-style.md # Active voice rules, numbering conventions, 10 anti-patterns
│ ├── quality-checklist.md # 20-point validation checklist with pass/fail examples
│ └── examples-edtech.md # 2 full EdTech UC examples (Course Enrollment, Mentor Approval)
├── assets/
│ └── uc-template.md # Copy-ready Markdown template
├── README.md # This file
├── LICENSE # MIT
├── CHANGELOG.md # Version history
└── .gitignore
The skill follows the progressive disclosure pattern: only SKILL.md is always loaded into Claude's context. The references/ and assets/ files are loaded only when needed, keeping context usage efficient.
Installation
Option 1: Claude Code CLI — User-level skill (recommended)
Install once and the skill is available across all your projects.
Step 1 — Clone the repository
# Mac / Linux
git clone https://github.com/ba-zone/ba-zone-use-case-writer.git ~/.claude/skills/ba-zone-use-case-writer
# Windows (PowerShell)
git clone https://github.com/ba-zone/ba-zone-use-case-writer.git "$env:USERPROFILE\.claude\skills\ba-zone-use-case-writer"
Step 2 — Verify the structure
After cloning, the skills directory should look like this:
~/.claude/skills/ # Mac/Linux
%USERPROFILE%\.claude\skills\ # Windows
└── ba-zone-use-case-writer/
├── SKILL.md ← main entry point (loaded by Claude Code)
├── references/
│ ├── template-guide.md
│ ├── writing-style.md
│ ├── quality-checklist.md
│ └── examples-edtech.md
└── assets/
└── uc-template.md
Step 3 — Use the skill in Claude Code
Open Claude Code CLI (or VS Code / JetBrains extension) and type:
/use-case-writer
Or just describe what you need — Claude Code will detect and activate the skill automatically based on trigger phrases.
Option 2: Claude Code CLI — Project-level skill
Install inside a specific project so only that project's Claude Code sessions load it.
# Mac / Linux — run from your project root
git clone https://github.com/ba-zone/ba-zone-use-case-writer.git .claude/skills/ba-zone-use-case-writer
# Windows (PowerShell) — run from your project root
git clone https://github.com/ba-zone/ba-zone-use-case-writer.git .claude\skills\ba-zone-use-case-writer
The .claude/skills/ directory sits alongside your project's .claude/settings.json. Claude Code picks it up automatically on next launch within that project.
Option 3: Upload to a Claude Project (claude.ai web)
For users who work on claude.ai instead of the CLI:
- Download or clone this repository
- In claude.ai, go to Projects → Create new project
- Upload all files (drag-and-drop the entire folder into the project knowledge base)
- Start chatting — the skill activates automatically on relevant prompts
Option 4: Use as a one-shot prompt template
Paste the contents of SKILL.md at the start of any Claude chat and say:
"Follow this workflow whenever I ask you to write a use case."
Skills directory paths — quick reference
| Platform | User-level (global) | Project-level |
|---|---|---|
| Mac / Linux | ~/.claude/skills/ | .claude/skills/ (project root) |
| Windows | %USERPROFILE%\.claude\skills\ | .claude\skills\ (project root) |
Tip (Windows): Open the skills folder quickly with
explorer "$env:USERPROFILE\.claude\skills"in PowerShell.
Usage
Trigger phrases
English:
- "Write a use case for [feature]"
- "Draft a UC for [functionality]"
- "Split this feature into a UC list"
- "Review my UC"
- "Write the Normal Course for this UC"
Vietnamese (skill responds in Vietnamese, UC artifact in English):
- "Viết use case cho [tính năng]"
- "Viết UC cho chức năng này"
- "Tách feature này thành UC list"
- "Review UC này giúp tôi"
- "Đặc tả use case cho [tính năng]"
Example interaction
User: Viết UC cho tính năng đặt lịch mentor 1-on-1
Claude:
[Step 1] Mode: A (write new from feature description).
[Step 2] Xác nhận scope:
Primary actor: Learner (Digital School Premium subscriber)
Goal: Book a 1-on-1 mentor session
System boundary: BA Zone Platform
Scope confirmed ✅. Confirm để tiến hành Step 3 (sinh UC theo từng nhóm)?
User: yes
Claude:
[Group 1: Identification + Actor + Description]
| Use Case ID: | UC-MENTOR-01 |
| Use Case Name: | Book 1-on-1 mentor session |
| ...
Group 1 done. Confirm to proceed to preconditions, postconditions, priority, frequency?
[... continues section by section ...]
The 4 workflow steps
Step 1: CLASSIFY INPUT → identify which of the 4 modes the user is in
Step 2: SCOPE THE UC → apply 4 scoping rules + coffee-break test
Step 3: WRITE THE UC → fill 13 fields, ONE SECTION GROUP AT A TIME
Step 4: VALIDATE → run 20-point checklist before handover
The 13 fields covered
| Field | Purpose |
|---|---|
| Use Case ID | Unique identifier (e.g. UC-LEARN-01) |
| Use Case Name | Action verb + Object |
| History | Created By / Date, Last Updated By / Date |
| Actor | Primary + Secondary actors (specific roles) |
| Description | 2-3 sentences: WHY + WHAT + OUTCOME |
| Preconditions | Verifiable conditions before UC starts |
| Postconditions | System state after successful completion |
| Priority | High / Medium / Low with justification |
| Frequency of Use | Quantified (X times / time unit) |
| Normal Course | Numbered, alternating Actor / System steps |
| Alternative Courses | Different paths to success (AC.1, AC.2…) |
| Exceptions | Failure modes (EX.1, EX.2…) |
| Includes | Sub-UCs called for common functionality |
| Special Requirements | Non-functional requirements |
| Assumptions | Beliefs not yet verified |
| Notes and Issues | TBDs with owner + due date |
The 20-point quality checklist
Every UC is validated before handover:
| Group | Items | What it checks |
|---|---|---|
| A. Scope & Identification | C1-C5 | Name format, goal level, ID uniqueness, single primary actor, system boundary |
| B. Actor & Context | C6-C8 | Specific actor role, complete description, quantified frequency |
| C. Pre/Post Conditions | C9-C11 | Verifiable preconditions, complete postconditions, no Pre/Assumption mix |
| D. Normal Course | C12-C15 | Numbered steps, Actor/System alternation, no embedded logic, complete flow |
| E. Alternative & Exception | C16-C18 | AC format, exception structure, common failure modes covered |
| F. Completeness | C19-C20 | Valid Includes, non-functional Special Requirements |
See references/quality-checklist.md for full details.
What this skill does NOT do
- ❌ Agile User Stories — use
ba-zone-user-story-ac-writerfor that - ❌ Full PRD / URD / SRS documents — UC is one section, not the whole doc
- ❌ UML Use Case Diagrams — this skill produces text specs, not diagrams
- ❌ Wireframes or UI mockups — UC describes interaction, not visual design
- ❌ Business Process Models — BP covers multi-actor multi-system processes; UC is 1 actor + 1 system
Examples included
Two complete, validated EdTech UCs ship with the skill in references/examples-edtech.md:
-
UC-LEARN-01: Enroll in a Digital School course
- Learner-facing UC with payment integration and async LMS fallback
- 9-step Normal Course, 2 Alternative Courses, 4 Exceptions
- Demonstrates: voucher payment AC, capacity race condition, async retry on LMS failure
-
UC-MENTOR-03: Approve learner 1-on-1 mentor session request
- Mentor-facing admin UC with concurrency, quota enforcement, and calendar integration
- 10-step Normal Course, 2 Alternative Courses, 4 Exceptions
- Demonstrates: concurrency conflict, quota exhaustion at approval time, calendar service degraded-mode handling
References & inspiration
- Alistair Cockburn, Writing Effective Use Cases (Addison-Wesley, 2000)
- Karl Wiegers & Joy Beatty, Software Requirements (Microsoft Press, 3rd ed.)
- IIBA, BABOK Guide v3 — Use Case and Scenarios technique
- Ivar Jacobson, Object-Oriented Software Engineering — origin of use case modeling
Contributing
Contributions welcome! If you have:
- Additional UC examples from your domain (insurance, healthcare, e-commerce, EdTech…)
- New anti-patterns you've encountered in the field
- Improvements to the 20-point checklist
- Translations or localization notes
Please open a Pull Request or Issue. When contributing UC examples, ensure they pass the full 20-point checklist first.
License
MIT License — see LICENSE for details.
File tree
More plugins by @phucnt-bazone-vietnam.
View @phucnt-bazone-vietnam’s profile@phucnt-bazone-vietnamFAQ
use-case-writer is a Claude Code plugin with 1 hand-picked skill, indexed on Flowy in the Writing category. Install it with the command on its page. It includes use-case-writer. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
- What is use-case-writer?
- This Claude AI Skill for Business Analysts & Product Owners, Use Case Writer scope, analyze, and document Use Case Specifications in English Markdown following the 13-field Karl Wiegers / IIBA template
- How do I install use-case-writer?
- Run these in Claude Code: npx -y skills add phucnt-bazone-vietnam/use-case-writer --agent claude-code. Then prompt normally.
- Does use-case-writer auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin. Request auto-invocation on its page and Flowy will route its skills for you as you prompt.
- Is use-case-writer free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it