Menu
Convert context to PRD and publish to issue tracker.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Guide for creating or updating skills. Use when extending Claude with specialized knowledge, workflows, or tool integrations.
Read and post to Twitter/X via the `bird` CLI — tweets, threads, search, timelines, bookmarks, follows, lists, media.
Set up and maintain bookkeeping for solopreneur. Track income/expenses, manage invoices, reconcile accounts, generate reports. Software, chart of accounts, categorization. Not professional. Trigger: bookkeeping, accounting, track expenses.
Explore feature, component, or functionality before implementation. Clarifies intent, requirements, design through dialogue.
Build brand identity: personality, voice/tone, visual system (colors, typography, logo, imagery), tagline, guidelines. Trigger: create my brand, brand identity, rebrand.
Deep competitive analysis: map competitors, find gaps, understand strategy, benchmark offering. Focused dissection vs broad landscape. Trigger: analyze competitors, competitive analysis, how beat them.
| name | to-prd |
| description | Convert context to PRD and publish to issue tracker. |
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.
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.