Repository-Verified PRD to GitHub Issue
Turn feature decisions into a repository-checked PRD with testable acceptance criteria and a verified GitHub issue link.
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
“We already discussed the feature. Why does the spec still describe code that doesn't exist?” Turn that discussion into a PRD grounded in the actual repository, with testable outcomes, explicit non-goals, and a live GitHub issue the team can reference.
What it does
- Checks claims about existing behavior against the relevant code paths and records evidence.
- Reuses decisions already made, asking only questions that change scope or acceptance.
- Converts feature requests into user stories and observable acceptance criteria, including relevant failure cases.
- Separates agreed decisions, proposals, assumptions, and unresolved blockers.
- Maps affected modules without prematurely prescribing implementation or splitting work into tickets.
- Files or updates the authorized GitHub issue, checks for duplicates, and reads back the saved result.
What you get
A PRD covering the problem, users, success criteria, scope, user stories, acceptance criteria, decisions, and likely affected modules. When publication is authorized and access is available, you also get the verified issue link; otherwise, you get the complete draft and the specific publication blocker.
Best for
Founders, product engineers, and engineering leads who align through conversation and use GitHub issues as the durable reference for feature delivery.
SKILL.md preview
---
name: repository-verified-prd-to-github-issue
description: Turn feature discussions into repository-verified PRDs with testable acceptance criteria, explicit decision status, and an affected-module map, then file or update the authorized GitHub issue and read it back. Use when the user says "write the PRD", "turn this discussion into a GitHub issue", "we agreed on the feature, document it", "our PRDs don't match the code", "this spec keeps growing", "verify this PRD against the repo", or "update the feature issue with our decisions".
---
# Repository-Verified PRD to GitHub Issue
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.