- Home
- Skills
- Bdq460
- Shell Format
- Product Expert
product-expert_skill
- TypeScript
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill bdq460/shell-format --skill product-expert- SKILL.md9.4 KB
Overview
This skill guides product experts to turn raw requirements into concrete product features, interaction forms, and prioritized implementation plans. It focuses on identifying core and supporting functionality, specifying technical and UX requirements, and producing prototype-ready deliverables.
How this skill works
The skill inspects incoming requirement documents, business flow diagrams, and user scenarios to evaluate product value and technical feasibility. It breaks requirements into a function tree, defines feature shapes (interaction, display, data flow), assigns MoSCoW priorities, and outputs feature lists, specs, and prototype guidance.
When to use it
- You have a requirements document and need a product-ready feature set.
- You must translate stakeholder requests into prioritized deliverables for engineering and design.
- You need clear feature specifications for prototype or sprint planning.
- You want to validate feasibility and estimate implementation cost before development.
Best practices
- Start with user stories to capture role, need, and purpose for every feature.
- Use a function tree to organize features into core, secondary, and tertiary levels.
- Apply MoSCoW to keep scope aligned with business value and delivery constraints.
- Include performance, usability, and security requirements for each critical feature.
- Iterate with UI and architecture colleagues during early review cycles.
Example use cases
- Designing an export report feature: list data selection, format options, background export, and history.
- Defining product search: input, suggestions, filters, result presentation, and performance SLOs.
- Converting stakeholder requests into a prioritized prototype and a sprint-ready feature spec.
- Evaluating technical feasibility and cost estimates for a requested integration or new module.
FAQ
Provide a requirements spec, business flow diagrams, and representative user scenarios or personas.
How do you decide priority?
I use MoSCoW: prioritize by business value, technical risk, user impact, and delivery effort.
What deliverables will I get?
A feature list, feature specs with acceptance criteria, priority map, and prototype guidance or wireframes.