Create structured PRDs using a land-then-expand approach with interactive prompts.
npx skills add https://github.com/navidemad/claude-code-plugins --skill plan-prd
Please help me install this Agent Skill. Skill: plan-prd Source: https://github.com/navidemad/claude-code-plugins/tree/main/prd-plugin/skills/plan-prd Command: npx skills add https://github.com/navidemad/claude-code-plugins --skill plan-prd
Creating comprehensive and consistent Product Requirement Documents (PRDs) is a complex and time-consuming task. This Skill streamlines the PRD creation process, ensuring structured planning, enforcing a "land then expand" philosophy, and automatically leveraging existing project context to maintain consistency across features.
CLAUDE.md) to ensure new expansions are consistent with established patterns.plan-prd, and the AI guides them through defining the minimal core, then helps them plan subsequent expansions (e.g., "Profile Picture Upload," "Social Media Links") by automatically referencing the patterns established in the core PRD.Plan a new core feature for user authentication.
High-intent search queries and answers about installing and using this skill.
This Skill automates PRD creation using a land-then-expand approach: start with a minimal core PRD (2-4 substories), then plan focused expansions iteratively. It guides you through type selection, scope definition, and next steps via interactive prompts, reducing ambiguity and preventing feature bloat.
Yes. The Skill automatically loads context from existing core PRDs and your project's CLAUDE.md conventions, ensuring new expansions follow established patterns and maintain consistency across all feature documentation.
Core PRDs define minimal viable features with 2-4 substories. Expansion PRDs build complexity on core PRDs with new capabilities. Task PRDs break down individual work items. The Skill guides you to choose the right type based on your planning need.
It structures PRD generation to enforce focused scoping upfront, minimizing rewrites. By loading existing context automatically and using interactive prompts with built-in free-text options, it eliminates redundant specification work and keeps your token consumption efficient.
No. The Skill handles the technical integration internally using jq for context processing. You interact through guided prompts asking about feature type, scope, and next steps—no scripting knowledge required.
Use this Skill when you need consistent, structured planning across multiple features or expansions, want to enforce minimal scoping discipline, or need to keep new work aligned with existing project conventions without manual context hunting.
phyter1Analyzes project documentation and codebases to extract architecture patterns and conventions.
dot-doConvert approved specs from discovery.db into beads epics with task breakdowns.
Ikram-AlamOrganize prompts, tools, documents, and history into structured context components.
timywelRoute PRD generation by analyzing input complexity and chaining downstream skills.