to-prd

mattpocock/skills · Agent Skill

將對話轉換為技術任務並在錯誤追蹤系統中釋出。

總覽

發布者	mattpocock社群
儲存庫	mattpocock/skills ↗
技能資料夾	`to-spec`
星	303,928
分支	25,577
附帶檔案	2
授權	MIT
最近更新	2026年10月22日
連結	技能原始碼 ↗ · 儲存庫 ↗

Mozgi 檢查

我們在技能檔案中發現的內容。詳細資訊需訂閱。

安全性

低風險 · 未發現明顯風險 — 完整報告會顯示細節

相容性

僅含說明 — 適用於多數代理

相似技能

找到 62 個相似技能

訂閱另含

安裝

技能就是一個含 SKILL.md 的資料夾。選擇你的代理，在專案根目錄的終端機（macOS、Linux 或 Windows 的 Git Bash）執行指令。

把提示貼到 Claude、Codex 或其他助理：它會自行檢查並安裝技能。

Install the “to-prd” skill from mozgi.io (https://mozgi.io/skills/mattpocock-to-prd/) for me.

1. Download the archive: https://mozgi.io/skills/mattpocock-to-prd/download
   If it fails, take the skill folder from the source: https://github.com/mattpocock/skills/tree/main/skills/engineering/to-spec
2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me.
3. Put the “to-prd” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.).
4. Make sure <skills folder>/to-prd/SKILL.md exists.
5. Briefly tell me what this skill does and offer to try it on my task.

If you cannot do a step yourself, tell me what to click or type.

git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/engineering/to-spec .claude/skills/to-spec

重新啟動 Claude Code — 技能就會出現在清單中，手動呼叫：/to-prd。要套用到所有專案，請放在 ~/.claude/skills。

git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills
mkdir -p .agents/skills
cp -r /tmp/skills/skills/engineering/to-spec .agents/skills/to-spec

Codex 會從目前資料夾往上到儲存庫根目錄，在 .agents/skills 中尋找技能；用 /skills 或 $to-prd 呼叫。所有專案：~/.agents/skills。

git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills
mkdir -p .cursor/skills
cp -r /tmp/skills/skills/engineering/to-spec .cursor/skills/to-spec

Cursor 啟動時會載入技能；在 Agent 聊天輸入「/」呼叫。Cursor 也會讀取 .claude/skills 與 .agents/skills。所有專案：~/.cursor/skills。

git clone --depth 1 --branch main https://github.com/mattpocock/skills.git /tmp/skills
mkdir -p .gemini/skills
cp -r /tmp/skills/skills/engineering/to-spec .gemini/skills/to-spec

任務符合時，Gemini CLI 會提議啟用技能，由你確認。所有專案：~/.gemini/skills。

技能檔案

2 個檔案下載 ZIP

安裝前請先檢視 SKILL.md 與相關檔案。點擊檔案即可預覽。

SKILL.md 內容

作者原文 · 唯讀

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. If not, tell the user to run /setup-matt-pocock-skills.

Process

1. 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.

2. 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.

3. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.

<spec-template>

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

1. As an <actor>, I want a <feature>, so that <benefit>

<user-story-example>

1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending

</user-story-example>

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

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.

Testing Decisions

A list of testing decisions that were made. Include:

A description of what makes a good test (only test external behavior, not implementation details)
Which modules will be tested
Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.

</spec-template>

常見問題

to-prd 技能有什麼用途？

將對話轉換為技術任務並在錯誤追蹤系統中釋出。

如何安裝 to-prd？

打開本頁的「安裝」區塊並選擇你的代理 — Claude Code、Codex、Cursor 或 Gemini CLI：那裡有把技能資料夾複製到正確位置的現成指令。也可以複製「透過助理」分頁中的提示，讓助理自行檢查並安裝技能。

to-prd 適用哪些 AI 模型？

技能是純 Markdown 指示（Agent Skills 格式），因此 to-prd 適用任何讀取 SKILL.md 的代理：Claude Code、Codex、Cursor、Gemini CLI、GitHub Copilot、OpenCode 等。只有在任務符合技能描述時，模型才會載入指示。

to-prd 是免費的嗎？

此技能由 mattpocock 公開發布，採用 MIT 授權。技能本身免費 — 你只需向 AI 供應商支付實際使用的 token 費用。

安裝技能安全嗎？

技能是代理會遵循的指示，安裝前請閱讀 SKILL.md 及相關檔案。技能資料夾中的腳本只有在代理執行時才會運行 — 留意它的動作，不要授予多餘權限。

技能和 MCP 伺服器或外掛有何不同？

MCP 伺服器或外掛為模型提供新工具 — 會執行並回傳結果的程式碼。技能提供的是知識與流程：如何處理任務、要遵循哪些步驟、好的成果長什麼樣子。它不需要伺服器或 API 金鑰。

總覽