planning

Generates a PRD and change brief from natural-language feature descriptions.

3|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/gener8v/gener8v.claude-skills --skill planning-gener8v
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/gener8v/gener8v.claude-skills/tree/main/skills/planning
Command: npx skills add https://github.com/gener8v/gener8v.claude-skills --skill planning-gener8v

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) and assets (resource) components.

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.

Frequently Asked Questions about planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a feature idea into a PRD with AI?โ–ผ

Describe the feature or product in natural language, including your must/should/could priorities. The Skill writes a PRD at .gener8v/prd.md with capability areas, user scenarios, scope boundaries, and open questions, plus a change brief under .gener8v/changes/.

What is a change brief in a requirements pipeline?โ–ผ

A change brief is a markdown document at .gener8v/changes/<slug>/change.md that scopes one initiative: which PRD capability areas it adds or modifies, the priority cut, and out-of-scope items. Downstream specification and ticket-breakdown skills read it to know what to work on.

Can I run planning on a project that already has a PRD?โ–ผ

Yes. For a second initiative the Skill amends the existing PRD in place, keeping all capability area names stable, marking dropped areas as withdrawn, and appending a Change Log entry. It opens a new change brief rather than editing existing ones.

When should I use brownfield instead of planning?โ–ผ

Use brownfield when an existing codebase has working code but no PRD; it builds the baseline bottom-up from code. Planning works top-down from user intent and is not for onboarding existing code or detailing areas the current change already covers.

Why does planning ask for must, should, and could priorities?โ–ผ

The Priority Cut in the change brief is the only place priority enters the pipeline. Specification tags requirements from it and every ticket's priority comes from it, so an invented cut would propagate to every ticket as if the Product Owner had set it.