Swapped 'backlog' for 'issue tracker
Co-authored-by: Copilot <copilot@github.com>
This commit is contained in:
parent
5fed805a92
commit
179a14e721
11 changed files with 67 additions and 41 deletions
|
|
@ -1,11 +1,11 @@
|
|||
---
|
||||
name: to-prd
|
||||
description: Turn the current conversation context into a PRD and publish it to the project backlog. Use when user wants to create a PRD from the current context.
|
||||
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.
|
||||
---
|
||||
|
||||
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 backlog backend and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
|
||||
The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
|
||||
|
||||
## Process
|
||||
|
||||
|
|
@ -17,7 +17,7 @@ A deep module (as opposed to a shallow module) is one which encapsulates a lot o
|
|||
|
||||
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
|
||||
|
||||
3. Write the PRD using the template below, then publish it to the project backlog. Apply the `needs-triage` triage label so it enters the normal triage flow.
|
||||
3. Write the PRD using the template below, then publish it to the project issue tracker. Apply the `needs-triage` triage label so it enters the normal triage flow.
|
||||
|
||||
<prd-template>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue