What problem does it solve? Product managers often jump straight to solutions or write specs before product decisions are actually settled, leading to rework and ambiguous builds. This Skill acts as the single discussion front-end for designing or redesigning product modules, restoring prior context, surfacing only real unknowns, and locking decisions before any specification or build begins. ## Core Features & Use Cases - Context restoration before questioning: Compiles a context pack from module docs, decisions, and product baselines so the PM never repeats settled decisions, and recalls relevant personal experience in the background. - Frontier-based decision rounds: Filters out mechanical and reversible choices, then presents only genuine product-model forks as dependency-ordered question rounds with tracked authorization gates and decision receipts. - Automatic internal orchestration: Invokes meta-analysis, mockup exploration, and spec-writing as internal capabilities, then commits the build basis and marks the module ready_to_build. - Use Case: A PM says "redesign the notification card." The Skill restores the module's active and superseded decisions, asks only the unresolved questions about objects, states, and permissions, records each confirmed decision, compiles the final spec, and hands off to the build phase automatically. ## Quick Start Tell the assistant to run /pmai-design and describe the module or product rule you want to design or change.
