skills.rest
berrzebb
berrzebbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

consensus-loop:planner

Analyze feature requests into PRD requirements and track-level plans with linked WBs.

15|4|Updated Mar 15, 2026
Search Tags:#planning#prd#dependency-graph#work-breakdown#track#drm#execution-order
One-click install
npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-planner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: consensus-loop:planner
Source: https://github.com/berrzebb/consensus-loop/tree/main/skills/planner
Command: npx skills add https://github.com/berrzebb/consensus-loop --skill consensus-loop-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planner helps teams translate vague requests into formal Product Requirements Documents, track-level plans, and implementable work-breakdowns, ensuring alignment before coding starts.

Core Features & Use Cases

  • Analyze feature requests and maintain PRDs
  • Define tracks, create execution plans, and decompose work into WBs
  • Interactively guide DRM, WB drafting, and cross-track alignment
  • Use for new feature planning, architecture changes, or scope adjustments
  • Trigger structured planning when user mentions requirements

Quick Start

Clarify scope with the user, confirm requirements, and begin with DRM validation before drafting PRD and WBs.

Frequently Asked Questions about consensus-loop:planner

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

FAQPage Schema
How do I translate a vague feature request into a PRD and work-breakdown?▼

To create a PRD and work-breakdown, analyze the feature request, confirm scope with the user, then guide through dependency validation and WB drafting before generating formal planning documents.

What is the best way to plan execution order for cross-track dependencies?▼

Planning execution order for cross-track dependencies requires referencing inter-track links during track-level plan creation to sequence work-breakdowns accurately and ensure alignment before execution.

How do I decompose PRD requirements into a track-level plan?▼

Decomposing PRD requirements into a track-level plan involves breaking down the formal requirements into implementable work-breakdowns and linking them directly back to the specific PRD items.

When do I need to perform DRM validation before drafting a PRD?▼

DRM validation is needed immediately after clarifying scope and confirming requirements, serving as a mandatory step before you begin drafting the PRD and work-breakdown structures.

Can I use this for architecture changes and scope adjustments, or only new feature planning?▼

You can use this planning process for new feature planning, architecture changes, and scope adjustments, triggering structured planning whenever requirements or architectural modifications are mentioned.

Related Skills

Explore More Product & Management Skills→
hemoryhemory

brainstorming

Guide structured brainstorming to clarify feature requirements before development.

Community
Intermediate
BellaBeBellaBe
37

planning-action

Translate goals into phased plans with milestones and dependencies.

Community
Advanced
prulloacprulloac

feature-planning

Transform feature breakdowns into ordered, dependency-aware execution sequences.

Community
Advanced
luongnv89luongnv89
104

tasks-generator

Transform PRD documents into sprint-based development tasks with dependency analysis.

Community
Advanced