Menu
Turn the current conversation context into a PRD and write it to the docs/prd folder. Use when user wants to create a PRD from the current context.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Guides agents through isolated Git worktree setup, lifecycle commands, process cleanup, and per-worktree local development state. Use when creating, starting, stopping, inspecting, cleaning up, or troubleshooting Git worktree development environments or when a repository includes a worktree lifecycle CLI.
Continuously watch and fix release main CI until the branch is fully green and verified working. Use when asked to babysit CI, babysit CI release, monitor release main, run /loop for CI, run /goal until checks pass, or keep iterating until release main is green.
Fix flaky tests by repeatedly running the suite, collecting intermittent failures, and proving stability. Use when asked to fix flaky tests or require repeated/consecutive green test runs.
Manage LinkedIn messaging, profiles, posts, connections, and company pages via Unipile. Use for networking, content publishing, and lead engagement.
Scoped commit workflow with a bundled committer script that prevents accidental broad staging. Use when the user asks to commit, commit all, create a git commit, or handle commit-time staging in this repository.
Systematically QA a web application like a real user, triage issues by severity, fix scoped bugs when asked, verify fixes with evidence, and report ship readiness. Use when asked to QA, test a site or app, find bugs, test and fix, or check whether a feature works.
| name | to-prd |
| description | Turn the current conversation context into a PRD and write it to the docs/prd folder. Use when user wants to create a PRD from the current context. |
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 — 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 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.
docs/prd/ folder.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.