菜单
Break a feature into implementation tasks — always create a feature branch first, detect test command and directories, write failing test → implement → pass (TDD), and save to /tasks/tasks-[name].md. Use for task list, implementation plan, feature breakdown, TDD tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Master orchestrator for the Agnostic Planning Skills library. Use to discover and activate 11 language-agnostic skills and 4 personas for product planning, task breakdown, estimation, risk assessment, ticket generation, backlog prioritization, sprint planning, retrospectives, requirements clarification, GitHub issue management, and status reporting. Personas guide end-to-end workflows. prd, planning, tasks, tickets, estimation, risks, status, backlog, sprint, retrospective, tdd, agile, product management, requirements, clarification.
Scan dependency chains, single points of failure, ambiguous requirements, external dependencies, capacity, and technical uncertainty. Every risk must reference a specific task/requirement as evidence. Output a risk register with likelihood, impact, and mitigations. Use for risk assessment, what could go wrong, risk register.
Prioritize a backlog using RICE, MoSCoW, value-vs-effort, or WSJF. Rank items by impact and urgency, produce ordered backlog with scores and rationale. Use when prioritizing a backlog, ranking features, applying frameworks.
Generate a stakeholder status report from task data — never fabricate progress, mark unknowns as "needs update". Includes Executive Summary (health, key accomplishment, top concern) and standard sections. Use for status report, sprint update, weekly update, project status.
Use to create, track, or manage GitHub issues with automatic project board integration (V2 and Classic), milestone tracking, and stage lifecycle (todo → in-progress → in-review → done). Covers issue creation, status updates, project board moves, and completion workflows.
Draft a clear actionable PRD from a feature — focus on what/why, no code, save to /tasks/prd-SLUG.md. Use when the user wants a PRD, product requirements, plan a feature, write a spec.
| name | generate-tasks |
| type | atomic |
| license | MIT |
| description | Break a feature into implementation tasks — always create a feature branch first, detect test command and directories, write failing test → implement → pass (TDD), and save to /tasks/tasks-[name].md. Use for task list, implementation plan, feature breakdown, TDD tasks. |
| metadata | {"version":"1.0.0","user-invocable":"true"} |
/tasks/tasks-[feature-name].md.Detect conventions using config files (see TEST_COMMANDS.md). Identify source and test directories.
Run detected test command; if it fails, confirm with user.
Break down the feature/PRD:
Create /tasks/tasks-[feature-name].md using the template in TASK_TEMPLATES.md. Each parent group follows TDD quadruplet (write failing test, confirm fail, implement, confirm pass).
Review tasks for coverage, correctness, and file paths.
| Skill | When |
|---|---|
| create-prd | Feeds requirements |
| estimate-tasks | After tasks generated |