Turn an existing conversation and knowledge of the codebase into a specification, then publish it to the project's issue tracker. It organizes the problem, user stories, implementation and testing decisions, and scope without a new requirements interview.
中文简介正在准备中。当前显示英语简介。
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.
Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.
Check with the user that these seams match their expectations.
ready-for-agent triage label - no need for additional triage.The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this spec.
Any further notes about the feature.
</spec-template>还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Turn an initial idea into an agreed design before coding. The skill clarifies goals and constraints through focused questions, compares possible approaches, and produces a reviewed specification ready for implementation planning.
中文简介正在准备中。当前显示英语简介。
Review code changes from a chosen Git reference against both project coding standards and the original requirements. Separate agents examine each perspective in parallel, and the results stay separate so specification gaps and coding issues are visible.
中文简介正在准备中。当前显示英语简介。
Routes a Comet request to the Native or Classic workflow based on project settings. When project settings are missing, it saves the global defaults locally so later changes to those defaults do not alter the project's choice.
中文简介正在准备中。当前显示英语简介。
Start or resume a development workflow by checking the request and current change state. Routes work through proposal, design, implementation, verification, and archiving, with separate paths for bug fixes and smaller changes and pauses for required user decisions.
中文简介正在准备中。当前显示英语简介。
Guide a development change through requirements, design, implementation, verification, and archiving. Comet combines OpenSpec for specifications with Superpowers for technical work, detects the current phase, and routes the agent to the appropriate next step.
中文简介正在准备中。当前显示英语简介。
Start a Comet task without choosing Native or Classic yourself. This entry skill reads the project’s workflow configuration, activates the configured option, and forwards the original request unchanged to the matching skill so work follows the project’s saved settings.
中文简介正在准备中。当前显示英语简介。