What problem does it solve? Turning a raw feature or product idea into structured requirements is slow and inconsistent. This Skill converts a natural-language description of what you want built into a living Product Requirements Document at .gener8v/prd.md and opens a scoped change brief under .gener8v/changes/, giving downstream specification and ticket-breakdown stages a stable, parseable foundation. ## Core Features & Use Cases - PRD Generation: Produces a PRD with 3-7 capability areas, user scenarios, scope boundaries, and open questions, written from templates in assets/ so pipeline tooling can parse it. - Change Brief Creation: Opens a change brief with a kebab-case slug, an Affected Capability Areas table, and a Priority Cut derived from the user's stated must/should/could. - Living Artifact Management: Amends an existing PRD in place for second initiatives, preserving capability area names, marking withdrawn areas, and appending Change Log entries. - Use Case: A user says "I want to build a support portal where agents can search our docs." The Skill writes .gener8v/prd.md with capability areas like Search & Retrieval, plus .gener8v/changes/support-search/change.md with the priority cut, ready for the Specification skill. ## Quick Start Use the planning skill to turn my description of a support documentation search feature into a PRD and open a change brief for it.