PI

PRD Writer That Files a GitHub Issue

Turn a shared understanding into a structured PRD (problem, user stories, decisions) posted as a live GitHub issue.

Engineeringp4matt-pocock
Or just install the prompt above — no subscription needed

About this skill


name: prd-writer-github-issue description: Turn a shared understanding into a structured PRD (problem, user stories, decisions) posted as a live GitHub issue. Use when working on prd writer that files a github issue.

PRD Writer That Files a GitHub Issue

Runs a 4-step process: get description, verify against the repo, deep interview if not already grilled, sketch modules to change, then emit a PRD from a fixed template. Files the PRD as a GitHub issue so it becomes the durable destination doc that every downstream skill references. Use immediately after grill-me and before slicing work into implementable pieces.

What you get

  • Polished PRD
  • Problem statement
  • User stories
  • Implementation decisions
  • Live GitHub issue link
  • Modules-to-change map

Customize your output

  • Feature description: free text
  • PRD template: default, custom URL
  • GitHub repo: owner/name
  • Labels: comma list
  • User story format: agile, gherkin
  • Priority: P0, P1, P2, P3

Example output

'Article writing page currently regenerates the entire document on every AI interaction' PRD with user stories and a split-pane document editing solution, filed as issue 483.

Best for

Founders, staff engineers, product engineers running an issue-driven workflow.


Note: Assumes gh CLI is installed. Composes cleanly with grill-me. High confidence.

Source: Ian Nuttall · https://www.youtube.com/watch?v=EJyuu6zlQCg Category: Engineering · Priority: P4

SKILL.md preview

---
name: prd-writer-github-issue
description: Turn a shared understanding into a structured PRD (problem, user stories, decisions) posted as a live GitHub issue. Use when working on prd writer that files a github issue.
---

# PRD Writer That Files a GitHub Issue

Runs a 4-step process: get description, verify against the repo, deep interview if not already grilled, sketch modules to change, then emit a PRD from a fixed template. Files the PRD as a GitHub issue so it becomes the durable destination doc that every downstream skill references. Use immediately after grill-me and before slicing work into implementable pieces.

## What you get

- Polished PRD
- Problem statement
- User stories
- Implementation decisions
- Live GitHub issue link
- Modules-to-change map

## C...