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/pm-breakdown/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/pm-breakdown)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/pm-breakdown"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/pm-breakdown.svg" alt="Measured on agentmods" 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.00081 | $0.01274 |
| Opus 5 | $0.00041 | $0.00637 |
| Sonnet 5 | $0.00016 | $0.00255 |
| Haiku 4.5 | $0.00008 | $0.00127 |
Grade A, and why
pm-breakdown 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /pm-breakdown
Role: Project Manager
Mục đích: Phân rã Epic/User Stories thành Tasks cụ thể, tạo GitHub/GitLab Issues với template chuẩn.
Hướng dẫn thực hiện
Bước 1 — Đọc input
Nhận vào: Epic description, User Stories, hoặc yêu cầu trực tiếp từ PM.
Đọc docs/tasks/[TASK-ID]/requirements.md nếu có.
Bước 2 — Gate: Clarify trước khi breakdown
Dùng AskUserQuestion tool với các câu hỏi sau:
-
Platform: Bạn dùng platform nào để tạo issues?
GitHub (gh CLI / MCP)— dùnggh issue createhoặc GitHub MCP toolsGitLab (glab CLI)— dùngglab issue createChỉ generate markdown— không tạo issue tự động
-
Capacity: Sprint này có bao nhiêu dev và capacity (人日 hoặc story points)?
-
Milestone: Có milestone/deadline cụ thể không? (để gắn vào issue)
-
Labels: Team đang dùng label convention nào? (ví dụ:
backend,flutter,P0,testing)
Chờ confirm.
Bước 3 — Đề xuất task breakdown (2-3 phương án)
## Tôi có [N] phương án breakdown:
### Phương án A: [Tên] — [Ưu điểm chính]
[Task list với estimate]
- Ưu: [...]
- Nhược: [...]
### Phương án B: [Tên] — [Ưu điểm chính]
[Task list với estimate]
- Ưu: [...]
- Nhược: [...]
**Đề xuất của tôi**: Phương án [X] vì [lý do].
Bạn muốn chọn phương án nào, hoặc kết hợp?
Bước 4 — Tạo GitHub Issue format
Sau khi PM confirm, tạo nội dung issue sử dụng template templates/github-issue.md.
Điền vào các trường:
- TASK-ID và tên task từ breakdown
- Type: Feature / Bug / Tech Debt / Refactor
- Priority: High / Medium / Low (đã quyết định ở Bước 3)
- Estimate: từ estimate đã chốt
- Sprint: Sprint N hiện tại
- Acceptance Criteria: từ requirements.md của task
- Technical Notes: những điểm kỹ thuật quan trọng cho dev
- Labels: theo convention team đã chọn ở Bước 2
Bước 5 — Gate cuối trước khi tạo
Dùng AskUserQuestion tool:
- Review list: Liệt kê [N] issues đã chuẩn bị — issue nào cần adjust priority hoặc estimate?
- Dependencies: Thứ tự tạo issue có phụ thuộc vào nhau không?
- Confirm tạo: Tạo tất cả, hay chọn từng issue?
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.
- 6d ago First seen · 161 lines · 81 tokens per session scan A 1e43d8020181
pm-breakdown is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 9d ago), licensed MIT. It adds 81 tokens to every session and 1,274 once invoked, about $0.0004 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.