Convert Notion product items into technical PRDs with GitHub project plans.
npx skills add https://github.com/martinjlowm/nixfiles --skill prd-martinjlowm
Please help me install this Agent Skill. Skill: prd Source: https://github.com/martinjlowm/nixfiles/tree/main/config/claude/skills/prd Command: npx skills add https://github.com/martinjlowm/nixfiles --skill prd-martinjlowm
It eliminates the gap between a product initiative description (often stored in Notion) and an engineering plan that can be implemented with clear scope, tasks, and measurable success criteria.
Use it when you have a Notion initiative link and need an engineering-ready breakdown that produces GitHub project items plus roadmap dates and success criteria.
Use prd to create a technical PRD from this Notion product item link and generate the corresponding GitHub project and Notion roadmap plan grounded in the reference codebase.
High-intent search queries and answers about installing and using this skill.
To generate a technical PRD from a Notion product item, provide the initiative link and a reference codebase. The tool extracts Notion context, analyzes codebase impact, and outputs structured scope, assumptions, and engineering epics.
Codebase-grounded engineering planning analyzes your reference codebase to identify architecture boundaries, conventions, and deployment patterns. This ensures your roadmap initiatives produce technical breakdowns that strictly follow existing project constraints.
You can create GitHub project epics from product ideas by passing a Notion product item to the tool. It translates the initiative into phased GitHub project issues and user stories grounded in your reference codebase architecture.
Yes, this approach supports technical roadmap planning by synchronizing Notion and GitHub Projects. It converts Notion product items into GitHub Project epics while validating a contiguous Notion timeline including hypercare.
The best way to estimate engineering tasks for a Notion product roadmap is calibrating estimates against an optional baseline file. This grounds the technical breakdown and phased execution plan in historical data.
Yes, you need a reference codebase to create verifiable success criteria for a PRD. Analyzing the codebase ensures the checklist-style criteria match actual architecture boundaries, tests, and deployment patterns.
dpaola2Generate a structured Product Requirement Document from a work item brief.
evolution-foundationGenerate structured PRDs with goals, requirements, and acceptance criteria.
coco-deBreak epics into user stories and sync sprint artifacts with ZenHub.
baekenoughAnalyze GitHub issues against the codebase and post prioritized triage comments.
