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-kickoff/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-kickoff)<a href="https://agentmods.dev/skills/hiepdnh/agentic-development-lifecycle/pm-kickoff"><img src="https://agentmods.dev/badge/skills/hiepdnh/agentic-development-lifecycle/pm-kickoff.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.00095 | $0.01803 |
| Opus 5 | $0.00048 | $0.00901 |
| Sonnet 5 | $0.00019 | $0.00361 |
| Haiku 4.5 | $0.00010 | $0.00180 |
Grade A, and why
pm-kickoff 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: /pm-kickoff
Role: PM / Tech Lead / Bridge Engineer
Mục đích: Bootstrap dự án greenfield — từ ý tưởng đến dự án có cấu trúc, docs, và team sẵn sàng sprint 1.
Context
Greenfield project khác brownfield:
- Không có
ba-reverse— không có codebase cũ để đọc - Cần quyết định tech stack ngay từ đầu — ảnh hưởng mọi thứ sau
- Khách JP thường expect 基本設計書 trước khi bắt đầu code
- Sprint 0 = setup môi trường + architecture decisions + initial docs
Hướng dẫn thực hiện
Bước 1 — Gate: Thu thập thông tin dự án
Dùng AskUserQuestion tool:
- Loại dự án: Web app / Mobile app / API / Microservice / Library / Other
- Khách hàng: JP outsource / Internal / Other
- Timeline: Deadline đầu tiên (format YYYY-MM-DD JST)
- Team size: Số dev / QA / BE
Chờ confirm.
Bước 2 — Phân tích yêu cầu và đề xuất tech stack
Dựa trên input từ Bước 1 và context của dự án, đề xuất:
## Đề xuất Tech Stack: [Tên dự án]
### Option A: [Tên stack] — [Trade-off chính]
| Layer | Technology | Lý do |
|-------|-----------|-------|
| Frontend | [...] | [...] |
| Backend | [...] | [...] |
| Database | [...] | [...] |
| Cache | [...] | [...] |
| CI/CD | [...] | [...] |
| Hosting | [...] | [...] |
**Phù hợp khi**: [...]
**Trade-off**: [...]
### Option B: [Tên stack] — [Trade-off chính]
[Tương tự]
### Option C: [Tên stack] — [Trade-off chính]
[Tương tự]
Chờ confirm tech stack.
Bước 3 — Gate: Architecture decisions
Sau khi chọn tech stack, xác nhận các quyết định kiến trúc ban đầu:
## Architecture Decisions cần xác nhận
| # | Quyết định | Option A | Option B | Recommend |
|---|-----------|---------|---------|----------|
| 1 | Auth strategy | JWT stateless | Session-based | JWT (scale tốt hơn) |
| 2 | API style | REST | GraphQL | REST (JP clients quen hơn) |
| 3 | DB schema | Monolithic | Multi-tenant | [tùy dự án] |
| 4 | Deployment | Monorepo | Multi-repo | Monorepo (team nhỏ) |
| 5 | Logging | Structured JSON | Plain text | Structured JSON |
Mỗi quyết định sẽ được ghi vào ADR sau.
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 · 232 lines · 95 tokens per session scan A a40488f890b3
pm-kickoff is a skill published in the GitHub repository hiepdnh/Agentic-Development-Lifecycle (6 stars, last pushed 9d ago), licensed MIT. It adds 95 tokens to every session and 1,803 once invoked, about $0.0005 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.