Borrowing it
Nothing to install: this file belongs to hiepdnh/Agentic-Development-Lifecycle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hiepdnh/Agentic-Development-Lifecycle/main/.claude/skills/ba-user-story/SKILL.mdgit clone --depth 1 https://github.com/hiepdnh/Agentic-Development-LifecycleWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/ba-user-story)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/ba-user-story"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/ba-user-story/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/ba-user-story"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/ba-user-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00067 | $0.00690 |
| Opus 5 | $0.00034 | $0.00345 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
ba-user-story scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Skill: /ba-user-story
Role: Business Analyst
Mục đích: Chuyển spec thành User Stories với Acceptance Criteria chuẩn, sẵn sàng để PM tạo issue.
Hướng dẫn thực hiện
Bước 1 — Đọc spec hiện có
Đọc docs/tasks/[TASK-ID]/requirements.md nếu có. Nếu chưa có, yêu cầu người dùng chạy /ba-spec trước.
Bước 2 — Gate: Xác nhận scope
## Tôi sẽ tạo User Stories từ spec: [Tên feature]
Spec có [N] Use Cases và [M] Acceptance Criteria.
Trước khi bắt đầu, tôi cần hỏi:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Granularity mong muốn? | A: Mỗi Use Case = 1 story / B: Gộp theo feature / C: Tách nhỏ hơn Use Case / D: Khác: ___ |
| 2 | Story format? | A: "As a [role], I want [action], so that [benefit]" / B: Format khác: ___ / C: Khác: ___ |
| 3 | Có Epic đã tồn tại để link vào không? | A: Có — tên/link: ___ / B: Không / C: Khác: ___ |
Chờ confirm.
Bước 3 — Tạo User Stories
Tạo mỗi User Story sử dụng template templates/user-story.md.
Bước 4 — Gate cuối: Review + Đề xuất thứ tự
## Đã tạo [N] User Stories:
| ID | Tên | Priority | Estimate | Dependencies |
|----|-----|----------|----------|--------------|
| US-001 | | | | |
**Đề xuất thứ tự implement** (dựa trên dependencies và value):
1. US-XXX — [lý do]
2. US-XXX — [lý do]
**Câu hỏi trước khi finalize**:
| # | Câu hỏi | Lựa chọn |
|---|---------|---------|
| 1 | Estimate có hợp lý không? | A: Hợp lý / B: Quá cao — sửa US-XXX: ___ / C: Quá thấp — sửa US-XXX: ___ / D: Khác: ___ |
| 2 | US-XXX có thể chia nhỏ hơn để dễ demo không? | A: Không cần / B: Có — chia như sau: ___ / C: Khác: ___ |
| 3 | Có story nào nên defer sang sprint sau không? | A: Không / B: Có — story: ___ / C: Khác: ___ |
Output files
- Cập nhật
docs/tasks/[TASK-ID]/requirements.mdvới User Stories section - Sẵn sàng để PM dùng
/pm-breakdownđể tạo GitHub Issues
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 71 lines · 67 tokens per session scan A 78395573b02d
ba-user-story is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 12d ago), licensed MIT. It adds 67 tokens to every session and 690 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.