Convert discovery input into an engineering-ready PRD or feature brief.
npx skills add https://github.com/ace3/skills --skill product-manager-ace3
Please help me install this Agent Skill. Skill: product-manager Source: https://github.com/ace3/skills/tree/main/skills/product-manager Command: npx skills add https://github.com/ace3/skills --skill product-manager-ace3
The Product Manager skill translates discovery input, stakeholder asks, feedback, and research findings into a concise, engineering-ready PRD or feature brief, enabling clear scope and handoffs before engineering begins.
Provide a request description and I will generate a compact PRD or feature brief with clear scope and acceptance criteria.
High-intent search queries and answers about installing and using this skill.
To turn stakeholder feedback into an engineering-ready PRD, provide the discovery input to generate a compact feature brief defining jobs, outcomes, and acceptance criteria. This translates vague requests into clear scope and handoff notes for faster delivery.
Writing acceptance criteria and non-goals to prevent scope creep involves structuring discovery input into defined release slices. This approach explicitly outlines boundaries and constraints, ensuring engineering teams focus only on defined outcomes.
Yes, you can use this to create handoff notes from research findings. It processes research data to provide decision context and clearly scoped deliverables, bridging the gap between product discovery and engineering execution.
A feature brief structures vague requests into defined jobs by applying a strict template. It satisfies requirements for goals, users, non-goals, risks, and acceptance criteria, converting abstract stakeholder asks into actionable engineering tasks.
Documenting decision context in a PRD requires goal definitions, user identification, non-goals, acceptance criteria, and risk assessments. These components ensure engineering teams understand stakeholder asks and constraints before development begins.
You need to generate a compact PRD instead of a full feature brief when translating simple stakeholder asks or research findings into clearly scoped deliverables. This prevents scope creep while providing essential engineering handoff notes.
Ocean326Document product problems and opportunities through structured discovery and stakeholder interviews.
marchattonRun verification checks before and after incremental code implementation with PRD JSON updates.
hajrasarwar11Generate PRDs, user stories, and roadmaps with acceptance criteria.
nicepkgGuide Agile product management with Scrum, Kanban, and SAFe practices.
