prd-breakdown

Featured

Use when user wants to break a PRD into Azure DevOps work items via vertical-slice plan. Workflow: read PRD → quiz user to lock durable decisions → draft slices with HITL/AFK + blocked_by → call az CLI directly via Bash to create items + Predecessor relations. Idempotent re-runs via fingerprint markers embedded in description. Pure prompt-driven — Claude is the runtime, no Python helper, no install ceremony. Trigger phrases: prd-breakdown / 拆 PRD / 切 vertical slice / 推 slice 到 ADO.

AI & Automation 76 stars 13 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 92/100

Stars 20%
63
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# prd-breakdown — PRD → ADO work items You are a PRD-to-tickets engineering assistant for Azure DevOps. You decompose product requirements into vertical, demo-able slices with explicit dependencies, then push them as work items via the `az` CLI. You quiz the user to surface durable assumptions instead of silently guessing, and you treat the user's PRD as authoritative — you don't invent scope. 把 PRD markdown 拆成 vertical slice plan,推上 ADO 變 work items(含 parent link + Predecessor relation + assignee)。全程 prompt-driven — Claude 透過 Bash 直接呼叫 `az` CLI;無 Python helper,無 install ceremony。 ## Prerequisites User 必須先設好: - `az` CLI 2.50+ + azure-devops extension:`az extension add --name azure-devops` - 環境變數: - `AZDO_ORG_URL`:例 `https://dev.azure.com/your-org` - `AZDO_PROJECT`:例 `your-project` - `AZURE_DEVOPS_EXT_PAT`:ADO PAT(Work Items Read/Write/Manage scope) 任一缺,提示 user 看 `README.md` Prerequisites 並停。 **CRITICAL**: PAT 永遠透過 `AZURE_DEVOPS_EXT_PAT` env var 注入,**絕不**放 argv(會被 `ps` / shell history 看到)。`az` CLI 會自動讀此 env var;用 Bash 跑 `az` 命令時不需特別處理 PAT。 ## Workflow A: PRD → vertical slices User 觸發詞如「拆 PRD」「切 vertical slice」時走這條。 ### Step A1. 偵測 ADO process template ```bash az devops project show \ --project "$AZDO_PROJECT" \ --organization "$AZDO_ORG_URL" \ --query "capabilities.processTemplate.templateName" \ -o tsv ``` 對照表 → default work item type: | Process template | Default work item type | |---|---| | Scrum | Task | | Agile | User Story | | CMMI | Requiremen...

Details

Author
KerberosClaw
Repository
KerberosClaw/kc_ai_skills
Created
4 months ago
Last Updated
6 days ago
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

prd-create

Use when user wants to draft a PRD (Product Requirements Document) from raw input (meeting transcripts, hand-waved descriptions, scattered decisions). Workflow: load org's PRD Guideline + writing discipline → lock execution mode (human-run vs unattended-agent-run) → ingest raw input → quiz user numbered-list iterate to fill §1-§15 → draft v0.1 → handle stakeholder merge (review feedback, surface conflicts) → lock v1.0 + sanitize per ADO publication contract → publish to ADO Wiki. For an agent-run PRD, §13 carries the unattended-execution discipline (machine-checkable AC + traffic-light + 3-exits + stop-and-ask), aligned with goal-engineer's loop-run-protocol. NOT for packaging an ALREADY-FROZEN build spec (approved ADR / locked design / machine-checkable AC) into an unattended dispatch — that is goal-engineer's lean build dispatch. Pure prompt-driven — Claude is the runtime, no Python helper. Trigger phrases: 寫 PRD / PRD 撰寫 / prd-create / 初版 PRD / 起 PRD.

76 Updated 6 days ago
KerberosClaw
AI & Automation Listed

prd-to-plan

Convert a PRD into a phased implementation plan using tracer-bullet vertical slices, then optionally create GitHub issues from the plan. TRIGGER when: user has a PRD and wants an implementation plan, says "plan this", asks to break a feature into phases, wants to convert requirements into tasks, asks to break a PRD into issues, create issues from a plan, or says "prd to issues". Also when user wants to stress-test a plan, get grilled on their design, or says "grill me". DO NOT TRIGGER when: user wants to execute a plan (just code it), review existing code, or do general architecture discussion without a PRD.

1 Updated 1 weeks ago
DROOdotFOO
AI & Automation Listed

prd-to-issues

Break a PRD into independently-grabbable tracker issues using tracer-bullet vertical slices. Use when asked to 'PRD to issues', 'break this PRD into tickets', 'create implementation tickets from a PRD', 'turn PRD into issues'.

3 Updated 4 days ago
craigcossairt