Menu
Sync a PRD after prototype changes — updates scope, features, golden examples, and changelog to keep the PRD as a living document.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Prepare for a 1:1 — pull context from goals, meeting notes, Slack, and tasks to generate talking points
Auto-generate or update description, type, topics, aliases, and graph-backed relationship fields for a file.
Build a focused plan for today based on goals, tasks, and recent activity. Reads from the weekly plan if it exists and updates it.
Check system health — metadata gaps, graph integrity, alias sync, and referential integrity.
Weekly review + compound learnings — review progress, surface blockers, distill insights into Memory
Cross-initiative alignment checker — surfaces misalignment, gaps, duplication, dependency risks, and synergy opportunities across active initiatives in the company and your groups roadmap. Complementary to /pulse (broad discovery); /align focuses on whether your initiatives are pulling in the same direction and have synergies with other company groups. Run ad-hoc or before key decisions.
| name | prd-update |
| description | Sync a PRD after prototype changes — updates scope, features, golden examples, and changelog to keep the PRD as a living document. |
Keep the PRD in sync with the prototype as it evolves. Prototypes are cheap to iterate; the PRD must keep up or it becomes stale.
When the user invokes /prd-update [prd-path] [what-changed], run through all steps in sequence.
If only a name is provided (e.g., "VoiceAgent PRD"), search:
Tasks/ directoryContext/Document Hub/ directoryIf [what-changed] is not provided, ask: "What changed in the prototype?"
Context/Reference/writing-styles/prd.md for voiceBased on the user's description, categorize the changes:
| Change Type | Sections to Update |
|---|---|
| Feature added | Scope (in-scope), Key Features, Golden Examples |
| Feature cut | Scope (out-of-scope), Key Features |
| Scope expanded | Scope, Risks, Success Metrics |
| Scope narrowed | Scope, Key Features |
| New edge case discovered | Golden Examples, Risks |
| Architecture changed | Proposed Solution, Feasibility Review |
| Hypothesis shifted | Success, Working Hypothesis |
| Prototype rebuilt | Interactive Prototype (what is real vs simulated) |
For each affected section:
[REVIEW]Add a new row to the changelog table:
| YYYY-MM-DD | [Description of what changed via /prd-update] |
Show a diff-style summary of what was updated:
PRD Updated: [Name]
Changed:
~ Scope — added [feature], moved [feature] to out-of-scope
~ Golden Examples — added 2 new examples (#6, #7)
~ Risks — new risk: [risk name]
Unchanged: Problem, Hypothesis, Milestones, Rollout Plan
Then ask: "Want me to run /prd-ready to check if this is ready for review?"
[REVIEW] rather than inventing answers