Generate Jira-ready PRDs from local codebase analysis.
npx skills add https://github.com/nobelk/claude-tools --skill prd-generator-nobelk
Please help me install this Agent Skill. Skill: prd-generator Source: https://github.com/nobelk/claude-tools/tree/main/skills/code-to-prd-doc Command: npx skills add https://github.com/nobelk/claude-tools --skill prd-generator-nobelk
Quickly translate a codebase into a formal Product Requirements Document (PRD) that can be turned into Jira epics, stories, and tasks, enabling clear visibility of features, gaps, and technical debt.
Run this skill on the repository root to generate a Jira-ready PRD from the current codebase.
High-intent search queries and answers about installing and using this skill.
To generate a PRD from an existing codebase, you run the skill on your repository root to reverse-engineer project structure, identify missing functionality, and output a Jira-ready prd_doc.md mapped to epics and stories.
Yes, you can automatically identify technical debt and missing features for Jira backlog creation by auditing the local repository data through a five-phase workflow to validate gaps and generate actionable work items.
Reverse-engineering code into product requirements works by analyzing the project structure and local documentation to discover existing features, behaviors, and constraints, then mapping them directly to Jira epics, stories, and tasks with traceability.
The best way to turn repository documentation into Jira epics and stories is to execute a five-phase workflow that discovers, analyzes, audits, validates, and generates a formal prd_doc.md from your local repository data.
No, you do not need external dependencies to map code to product requirements documentation, as the skill relies solely on local repository data and its documentation to perform the code analysis and feature identification.
oaustegardInitialize Git repositories and commit changes for skill directories.
ninthspaceBreak down specifications into structured epic documents with stories and tasks.
coolbeevipConvert technical debt specifications into engineering issues with dependency tracking.
georgekhananaevEnforce consistent Markdown syntax across documentation and README files.
