Generate a production-ready PRD through an adaptive interview with codebase context.
npx skills add https://github.com/mattjefferson/agents --skill dev-brainstorm
Please help me install this Agent Skill. Skill: dev-brainstorm Source: https://github.com/mattjefferson/agents/tree/main/skills/dev-brainstorm Command: npx skills add https://github.com/mattjefferson/agents --skill dev-brainstorm
Creates a production-ready PRD by guiding an adaptive interview workflow that captures user needs, context, and scope, while grounding decisions with codebase insights.
Describe your feature or problem to begin the adaptive PRD process.
High-intent search queries and answers about installing and using this skill.
To generate a production-ready PRD, describe your feature request to initiate an adaptive interview that captures scope and context, then embeds codebase insights to produce a self-contained document for handoff.
An adaptive interview for product documentation is a progressive questioning process that adjusts depth based on complexity, capturing user needs to generate Quick, Standard, or Full PRDs for both small tweaks and large redesigns.
Yes, you can create a quick PRD for a small feature tweak by initiating the adaptive interview, which automatically adjusts its depth to match the complexity of minor adjustments while maintaining structured output.
Codebase research integrates into PRD generation by pulling relevant project insights during the interview process, ensuring the final document reflects the current architectural state and grounds decisions in actual implementation context.
The best way to structure a PRD for handoff is using a self-contained document with structured sections generated through adaptive interviews, ensuring all requirements from R0 and higher are satisfied for immediate planning.
Yes, the PRD generation process handles large system redesigns by progressively increasing the interview depth to a Full PRD format, capturing complex scope and extensive codebase context for comprehensive architectural changes.
yu13130122297Identify uncertainties in research framing, datasets, metrics, and baselines.
krzemienskiConvert vague goals into structured milestones with progress tracking and Serena MCP persistence.
JohannesKoningsSynthesize conversation and codebase context into a product requirements document and publish it to the issue tracker.
christopher-bussGenerate a Product Requirements Document from conversation context and codebase understanding.
