One-click install
npx skills add https://github.com/Ratler/dream-team --skill plan-ratler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Ratler/dream-team/tree/main/skills/plan
Command: npx skills add https://github.com/Ratler/dream-team --skill plan-ratler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates collaborative brainstorming to turn a vague idea into a concrete, validated plan before any spec is written.

Core Features & Use Cases

  • Four-phase dialogue that guides discovery, constraint analysis, and approach decisions.
  • Opinionated, structured questioning with one question per turn to maintain alignment.
  • Smooth handoff to specification-writing steps with a clear execution plan and success criteria.

Quick Start

Describe your idea and let the planner guide a structured, phase-wise conversation to a validated plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a rough software feature idea into a validated plan before writing a spec?

Collaborative feature planning guides rough ideas into validated plans using a four-phase dialogue: getting oriented, exploring the idea, shaping the approach, and choosing execution. It enforces one-question-per-turn alignment before spec writing.

What is the best way to facilitate brainstorming and requirements gathering for architecture discussions?

Structured brainstorming for architecture discussions uses opinionated, phase-wise questioning to uncover constraints and present 2-3 approaches with trade-offs. This validates requirements before finalizing execution steps.

Can I use a decision-tree approach for feature planning across small improvements and large redesigns?

Yes, decision-tree style feature planning suits both small improvements and large redesigns across software projects. It coordinates collaborative conversations to shape approaches and choose execution methods through structured discovery phases.

Does structured collaborative planning work without prior documentation or formal dependencies?

Structured collaborative planning operates with no prior documentation or formal dependencies. You describe your idea, and the planner guides a phase-wise conversation to validate constraints and shape concrete execution steps.

How do I move from requirements gathering to a concrete execution plan with success criteria?

Moving from requirements gathering to execution involves shaping approaches and choosing execution paths. The planning process ensures smooth handoff to specification-writing by defining clear success criteria and validated steps.