菜单
Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
4-skill academic pipeline: deep research (13-agent), academic paper (LaTeX), peer review (7-agent), pipeline orchestrator (10-stage). CC BY-NC 4.0 — non-commercial use only.
Analyzes existing workflows and processes to find inefficiencies, bottlenecks, and optimization opportunities. Goes beyond automation to improve the process itself. Use when user says "optimize my process", "find bottlenecks", "why is this slow", "improve this workflow", "process audit", or "efficiency review".
Takes a process description and generates a complete Standard Operating Procedure document with numbered steps, decision points, checklists, and troubleshooting guidance. Use when user says "write an SOP", "create SOP", "standard operating procedure", "document this process", "write a procedure for", or asks to formalize any business process.
Interactive weekly review assistant that helps business owners reflect on their week, measure progress against stated goals, and plan the next week with clarity. Use when user says "weekly review", "review my week", "what did I accomplish", "plan next week", "week in review", "how did my week go", or asks to reflect on recent work.
Maps business processes from natural language descriptions into structured workflows, identifies automation opportunities using the GREEN/YELLOW/RED framework, and generates visual workflow diagrams. Use when user says "map my workflow", "describe my process", "where should I automate", "workflow audit", or describes any business process.
GraphRAG-powered code review with blast-radius analysis via Tree-sitter AST. MCP server. Recommended for 500+ file codebases.
| name | to-prd |
| description | Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context. |
| auto-activate | false |
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.
The issue tracker and triage label vocabulary should have been provided to you.
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 PRD, and respect any ADRs in the area you're touching.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
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 PRD.
Any further notes about the feature.