Define product scope and generate a dated spec file in docs/specs/.
npx skills add https://github.com/MaxGzLi/claudeorc --skill pm-maxgzli
Please help me install this Agent Skill. Skill: pm Source: https://github.com/MaxGzLi/claudeorc/tree/main/skills/pm Command: npx skills add https://github.com/MaxGzLi/claudeorc --skill pm-maxgzli
This Skill turns vague product ideas into clear, scoped, and actionable specifications so teams avoid ambiguous requirements and misaligned work. It guides users through a structured interactive conversation to identify target users, user stories, MVP scope, and measurable acceptance criteria.
/pm flow for product discovery or as the first phase inside a larger orchestrated workflow to hand off to planning and implementation agents.Use the pm skill to turn the idea "Build a habit tracker app" into a scoped spec by invoking /pm with a one-sentence idea.
High-intent search queries and answers about installing and using this skill.
To turn a one-sentence idea into a buildable MVP spec, an interactive Q&A flow asks clarifying questions one at a time to define target users, user stories, MVP scope, and measurable acceptance criteria. It then generates a dated markdown spec file for development handoff.
Defining product scope and writing user stories requires clarifying target users and MVP boundaries through structured questioning. This approach produces a consistent specification document that includes an overview, user stories, out-of-scope items, and technical constraints to align engineering teams.
You can generate measurable acceptance criteria using an interactive Q&A flow that systematically refines your project scope. By asking clarifying questions sequentially, it converges vague ideas into a dated spec file containing structured, testable acceptance criteria for engineers.
Product spec writing works both as a standalone product discovery flow and as the first phase inside an orchestrated workflow. It produces a dated specification file that serves as a direct handoff to downstream planning and implementation agents for development.
The generated product spec file uses a dated markdown format saved to the docs/specs/ directory. It applies a consistent template that organizes the overview, target users, user stories, MVP scope, out-of-scope features, and tech constraints into a single buildable document.
npc-chrisGuide product idea refinement through structured brainstorming questions.
epieczkoParse Markdown Epic documents and generate structured user stories as JSON.
wzserDecompose project plans and specifications into granular issues for tracking.
deltatreeGuide collaborative creation of product briefs through a structured workflow.