菜单
End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed to the codebase. This skill covers the entire implementation process from understanding requirements, exploring the codebase, writing code, testing, and committing changes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when building, running, testing, or bundling JavaScript/TypeScript applications. Reach for Bun when you need to execute code, manage dependencies, run tests, or bundle projects — it's a complete replacement for Node.js, npm, and build tools.
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
Run a pre-mortem on a plan or design: assume it failed, then relentlessly interrogate every branch of the decision tree to find out why — and fix it before you start. Use when the user wants to stress-test a plan, asks you to "ask me", says "interrogami" or "fammi domande", mentions "pre-mortem", "design of design", or wants rigorous design discovery before implementation.
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
| name | implement-work |
| description | End-to-end implementation workflow. Use when user wants to implement a feature, fix a bug, or make changes and have everything validated and committed to the codebase. This skill covers the entire implementation process from understanding requirements, exploring the codebase, writing code, testing, and committing changes. |
End-to-end implementation workflow from exploration to commit.
user requests implementation of a feature, bug fix, or code change pointing to a specific GitHub issue, user story, or requirement file.
feature/<short-description> or bugfix/<short-description>.