From shazam
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
npx claudepluginhub qhuang20/shazam --plugin shazamThis skill uses the workspace's default tool permissions.
This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.
Generates a PRD from conversation context and codebase analysis using a structured template, publishes to project issue tracker. Use to formalize features from chats.
Synthesizes conversation context and codebase into a PRD artifact as markdown file or GitHub issue. Use when requesting PRD, requirements doc, feature spec, or crystallizing discussions before planning.
Synthesizes PRD for substantial new features from project context, ADRs, commits, and conversation. Validates modules/architecture, writes structured spec in docs/specs/. Asks before GH issue.
Share bugs, ideas, or general feedback.
This skill will be invoked when the user wants to create a PRD. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Interview the user relentlessly about every aspect of this plan until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
Sketch out the major modules you will need to build or modify to complete the implementation. Actively look for opportunities to extract deep modules that can be tested in isolation.
A deep module (as opposed to a shallow module) is one which encapsulates a lot of functionality in a simple, testable interface which rarely changes.
Check with the user that these modules match their expectations. Check with the user which modules they want tests written for.
The problem that the user is facing, from the user's perspective.
The solution to the problem, from the user's perspective.
A LONG, numbered list of user stories. Each user story should be in the format of:
This list of user stories should be extremely extensive and cover all aspects of the feature.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this PRD.
Any further notes about the feature.
After the PRD is created, suggest: "PRD done! Next: /prd-to-plan to break it into phases, or /prd-to-issues to create tickets directly."