planning

Decompose goals into YAML-based executable plans with checkpoint verification.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/twofoldtech-dakota/studio --skill planning-twofoldtech-dakota
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/twofoldtech-dakota/studio/tree/main/playbooks/planning
Command: npx skills add https://github.com/twofoldtech-dakota/studio --skill planning-twofoldtech-dakota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-and-Solve Planning Skill prevents premature action by enforcing thorough, repeatable planning before execution, helping teams translate ambiguous goals into concrete, trackable plans.

Core Features & Use Cases

  • Loop-driven planning: uses a universal loop system to gather requirements, clarify goals, and validate readiness.
  • Phase-based approach: three planning phases (Variable Extraction, Intermediate Calculation, Step-by-Step Planning) plus checkpoints and risk analysis.
  • Verifiable plan: supports a YAML plan structure with inputs, steps, checkpoints, and verification criteria.
  • Use cases include product planning, software architecture design, and cross-functional project planning where requirements are uncertain.

Quick Start

Start a planning session by prompting the assistant to plan a feature: /studio "plan feature X" and follow the questions to gather requirements, then request to ready_to_plan to proceed.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I decompose ambiguous project goals into executable plans?

To decompose ambiguous project goals into executable plans, this Skill applies a three-phase loop encompassing variable extraction, intermediate calculation, and step-by-step planning. It gathers requirements and assesses risks to produce a verifiable, trackable plan.

What is the best way to enforce requirements gathering before project execution?

Enforcing requirements gathering before project execution is achieved through a planning loop that clarifies goals and validates readiness. The approach codifies checkpoints and risk analysis to prevent premature action and ensure all project requirements are thoroughly verified.

How does a YAML-based plan structure improve project management?

A YAML-based plan structure improves project management by standardizing inputs, execution steps, checkpoints, and verification criteria into a clear format. This structured approach ensures recoverable progress and trackable readiness across complex, multi-round planning tasks.

Can I use this planning approach for cross-functional project planning with uncertain requirements?

Yes, you can use this planning approach for cross-functional project planning with uncertain requirements. It is specifically designed to handle complex, multi-round tasks across product development and software design by codifying a loop-driven system for validation and risk mitigation.

When do I need checkpoint-based verification in software architecture design?

Checkpoint-based verification is needed in software architecture design when translating complex, multi-round goals into actionable steps. It ensures readiness, enforces risk mitigation, and validates progress before moving forward, preventing premature execution failures.