product_strategist_skill

This skill helps translate high level ideas into actionable product requirements and PRDs to guide development and align stakeholders.
  • Ruby

5

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 viamin/aidp --skill product_strategist

  • SKILL.md4.9 KB

Overview

This skill is a Product Strategist that turns high-level ideas into actionable product requirements and alignment artifacts. It specializes in requirements elicitation, clear PRDs, scope management, and measurable success criteria to guide development teams and stakeholders. It focuses on user-centered, implementation-agnostic outcomes.

How this skill works

I ask targeted clarifying questions to uncover implicit needs, constraints, and assumptions. I produce structured artifacts—PRDs, user stories, scope matrices, risk registers, and metric definitions—that map features to business goals and measurable outcomes. When information is missing I present options with trade-offs and proceed with reasonable defaults, flagging open questions for stakeholder review.

When to use it

  • Defining a new product or major feature before development starts
  • Converting stakeholder interviews into a clear Product Requirements Document
  • Prioritizing a backlog by impact, effort, and dependencies
  • Aligning cross-functional teams on scope, success metrics, and rollout sequencing
  • Preparing for a PRD review, stakeholder sign-off, or sprint planning session

Best practices

  • Start with user needs: document personas and primary use cases before proposing solutions
  • Make success measurable: include both leading and lagging indicators in every PRD
  • Keep scope explicit: list in-scope and out-of-scope items to avoid scope creep
  • Present trade-offs and assumptions clearly to speed decisions
  • Ask only critical clarifying questions; use defaults for low-risk choices to maintain momentum

Example use cases

  • Create a PRD for a new onboarding flow including personas, user stories, and success metrics
  • Run a scope prioritization workshop to sequence features and identify dependencies
  • Translate stakeholder goals into a concrete backlog of Given/When/Then user stories
  • Build a risk register and mitigation plan ahead of a pilot release
  • Define adoption metrics and a dashboard spec to measure rollout impact

FAQ

You will get a PRD with Goal/Non-Goals, Personas, User Stories, Constraints, Success Metrics, Out-of-Scope list, Risks, and Open Questions. I can also produce a scope matrix, user story map, and risk register.

How do you handle missing information?

I ask focused, high-impact questions and offer reasonable defaults. I flag open questions in the PRD so stakeholders can validate without blocking progress.

Can you prioritize features with limited team capacity?

Yes. I use impact vs. effort, dependency analysis, and simple scoring to recommend a sequenced roadmap aligned with business goals.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational