Convert conversation context into a structured PRD for GitHub issue submission.
npx skills add https://github.com/AcendWay/ai-skills-library --skill to-prd-acendway
Please help me install this Agent Skill. Skill: to-prd Source: https://github.com/AcendWay/ai-skills-library/tree/main/skill-folders/to-prd Command: npx skills add https://github.com/AcendWay/ai-skills-library --skill to-prd-acendway
Turning scattered conversation details into a clear, actionable PRD is slow and error-prone, and important requirements often get missed or misinterpreted.
Example use case: A product discussion covered goals, constraints, user roles, and desired outcomes; use this skill to package that information into an end-to-end PRD draft suitable for engineering review.
Use the skill to create a PRD from your current conversation context and prepare it for submission as a GitHub issue.
High-intent search queries and answers about installing and using this skill.
To convert a product discussion into a GitHub issue PRD, use this skill to synthesize your current conversation context into a structured document. It automatically captures product intent, user stories, and implementation decisions without requiring follow-up questions.
Writing user stories from existing context involves extracting desired outcomes and user roles from your discussion. This skill automatically generates extensive numbered user stories and decision lists directly from the synthesized conversation material.
Yes, you can generate product requirements without interviews by using this skill to synthesize existing conversation context. It packages goals, constraints, and testing decisions into a complete draft while clarifying what items still need stakeholder validation.
Yes, this skill structures implementation and testing decisions for engineering review. It produces implementation decisions focused on deep, testable modules and formats the output using a PRD template suitable for direct submission as a GitHub issue.
If your scattered conversation details are missing out-of-scope items, this skill identifies and explicitly lists them within the generated PRD. It ensures important requirements, constraints, and boundaries are captured without misinterpretation during synthesis.
You need to package feature planning context into a structured document when a product discussion covers goals and desired outcomes. This skill transforms that raw context into an end-to-end PRD draft suitable for immediate engineering review.
dformosoGenerate a Product Requirements Document from conversation, codebase, and research.
apocohqGenerate a structured PRD as a GitHub issue from stakeholder interviews and repo exploration.
nesihaver-ILCreate structured issues in GitHub Issues, Linear, or Jira.
DaRacciManage encrypted secrets with sops-nix and age for NixOS configurations.
