Convert conversations and codebase context into a structured PRD for issue trackers.
npx skills add https://github.com/akillness/jeo-skills --skill to-prd-akillness
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/to-prd Command: npx skills add https://github.com/akillness/jeo-skills --skill to-prd-akillness
Converts ongoing discussions and codebase context into a structured Product Requirements Document (PRD) ready for publication to the project issue tracker, eliminating the need for separate interviews and manual synthesis.
Analyze the current discussion and codebase context to generate a complete PRD that can be submitted to the issue tracker.
High-intent search queries and answers about installing and using this skill.
To generate a product requirements document from an existing conversation, the Skill analyzes your ongoing discussions and codebase context to automatically produce a structured PRD. This eliminates the need for separate user interviews and manual synthesis before publishing to an issue tracker.
A PRD for an issue tracker should include a problem statement, proposed solution, user stories, implementation decisions, testing considerations, scope, and references. This structure ensures the feature requirements are fully documented and ready for formal planning sessions.
You need a formal spec before breaking development work into tasks when user interviews are not conducted but a structured PRD is required. This Skill converts your codebase context and discussions into the necessary formal specification to guide implementation.
Yes, you can write user stories and implementation decisions without conducting interviews by applying this Skill. It directly extracts requirements from your current conversations and codebase context to populate the full PRD template workflow.
The best way to turn codebase context into a structured PRD is to analyze the current discussion alongside the codebase to synthesize requirements. This approach automatically generates a complete document ready for issue tracker publication and planning.
nselugaGenerate a Product Requirements Document from conversation context and publish it to the issue tracker.
vm0-aiConvert conversation context into structured GitHub issues with labels.
shushuznGenerate a product requirements document from conversation context and repository understanding.
I2olanDPlan, conduct, and synthesize user research into personas and journey maps.
