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.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you create a PRD for that feature. A good PRD typically includes a problem statement, user stories, acceptance criteria, and some technical details about what needs to change. From your description, it sounds like you want to improve how people edit documents by showing multiple sections at once. That's useful. I could sketch out the main sections and suggest some user stories, but I'd want to clarify a few things first. What specific editing workflows do you think this will improve? And do you have a sense of what technical changes would be needed? Once I understand those details better, I can put together something more complete.
PROCESSING PRD → GITHUB ISSUE: PROBLEM STATEMENT: Article writers currently regenerate the entire document on every Claude AI interaction, breaking manual edits in unmodified sections. Split-view editing enables independent left-pane human editing + right-pane AI-only regeneration, eliminating 47-second interruptions per interaction cycle. USER STORIES: → As a writer, I want to edit the introduction while Claude rewrites section 2 in parallel, so I don't lose my work → As an editor, I want to freeze my edits in columns A-C while AI handles D-E, so collaborative writing doesn't deadlock → As a creator, I want to compare my original text against AI suggestions side-by-side before merging IMPLEMENTATION DECISIONS: → Split into left (DOM editable) and right (API streaming) panes via CSS Grid → Lock mechanism: timestamps on each pane; merge conflict resolution favors human edits → Storage: Use change-diff protocol instead of full-document save MODULES TO CHANGE: • editor/EditorPane.tsx (add split layout) • api/regenerate.ts (stream to right-pane only) • lib/mergeConflicts.ts (new file) ISSUE FILED: 483 • labels: enhancement, product • priority: P1 • assigned: your team
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.
SKILL.md preview
---
name: prd-writer-github-issue
description: Use immediately after aligning on a shared understanding of a feature, to turn it into a structured PRD posted as a live GitHub issue before slicing work into implementable pieces.
version: 1.0.0
category: Engineering
author: AgentVolt
license: proprietary
tags:
- engineering
- p4
---
# PRD Writer That Files a GitHub Issue
Turns a shared understanding of a feature into a structured PRD — problem statement, user stories, decisions — and files it as a live GitHub issue that becomes the durable reference every downstream skill and teammate points to.
## When to use
… (sign up to view the full skill)