pm-requirement-flowv1.2.0

A product manager receives a vague request from an internal team to build a small tool feature. Using this skill, the PM clarifies requirements through structured questioning, writes a SPEC, gets confirmation, dispatches development to Claude Code, and validates the output.

A PM collects raw feedback from multiple customers about a product improvement. The skill helps in aggregating, clarifying, and prioritizing the feedback into a clear SPEC, which is then dispatched for implementation with clear acceptance criteria.

A bug is reported with ambiguous steps. The PM uses the questioning phase to understand the context, reproduce the issue, and document expected behavior before dispatching a fix to the development team.

An entrepreneur has a raw idea for a feature. The PM guides them through defining scope, users, and success criteria, then quickly dispatches a prototype via Claude Code for fast validation.

A PM needs to hand off a well-defined feature request to another team's developer. The skill ensures the requirement is documented, confirmed, and dispatched with clear boundaries and completion criteria, reducing back-and-forth.

Offer the PM skill as a free basic template, with premium options for advanced integrations (e.g., Jira, Slack) or analytics on flow efficiency.

Product management consultants can use this skill to standardize their client engagements, deliver faster results, and offer fixed-price packages for requirement-to-development workflows.

License the skill to companies with in-house PM teams to streamline their internal development processes, reducing miscommunication and development rework.