Generates a Product Requirements Document from conversation and codebase context and publishes it to the issue tracker via API.
npx skills add https://github.com/tanglg/cms --skill to-prd-tanglg
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/tanglg/cms/tree/main/.codex/skills/to-prd Command: npx skills add https://github.com/tanglg/cms --skill to-prd-tanglg
This Skill automates the process of creating a Product Requirements Document (PRD) from existing conversation context and project information, and publishes it to the project's issue tracker.
Run the to-prd skill to automatically generate and publish the PRD for your current feature.
High-intent search queries and answers about installing and using this skill.
Generating a PRD from codebase context requires synthesizing conversation and project information into structured project documentation. This automates extracting technical details to draft requirements without manual writing.
Automating publishing product requirements to an issue tracker involves a contextual generation step that builds the document and then publishes it via the tracker's API. This applies appropriate labels automatically during the creation process.
To create automated PRDs for your current feature, you need domain knowledge of the project's codebase and access to the issue tracker's API. These prerequisites ensure the generated documentation accurately reflects the technical context.
Yes, contextual PRD generation is specifically useful for developers who need to document a feature they are working on but lack detailed user requirements. It derives the necessary documentation directly from the existing codebase and conversation context.
The limitations of automated PRD creation include a dependency on your existing domain knowledge of the codebase and valid issue tracker API access. Without sufficient project context or API credentials, the automated publishing process will fail.
MohammedSaudAlsahliGenerate a PRD from conversation context and publish it to the issue tracker.
slabgorbOrganize sprint status, backlog, and story workflows via the pf sprint CLI.
ViniciuscarvalhoExtract key terms from prompts and map them to the existing codebase.
MarcoAntoliniConvert conversation context into a Product Requirements Document and integrate it into an issue tracker.
