plan

Convert vague feature ideas into structured plans with tasks and acceptance criteria.

18|3|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill plan-ondrej-svec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ondrej-svec/heart-of-gold-toolkit/tree/main/plugins/deep-thought/skills/plan
Command: npx skills add https://github.com/ondrej-svec/heart-of-gold-toolkit --skill plan-ondrej-svec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategic planning that coordinates research and planning to produce a formal plan document with tasks, rationale, and acceptance criteria.

Core Features & Use Cases

  • Phase-driven planning process (Phase 0-4) guiding discovery, refinement, research, and execution-ready plans.
  • Generates a plan document with tasks, decision rationales, risks, and success criteria.
  • Supports structured handoff to /work and preview artifacts for stakeholder review.

Quick Start

Describe the feature or task clearly and initiate the Plan workflow to produce the plan document.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I turn a vague feature idea into an actionable roadmap with tasks?

To turn a vague feature idea into an actionable roadmap, you need a structured planning process that defines scope, constraints, and risks. This approach refines initial concepts through discovery phases to produce a formal plan document with rationale and execution-ready tasks.

What is a structured planning document for project management?

A structured planning document for project management records the scope, constraints, and risks of non-trivial work. It contains decision rationales, acceptance criteria, and a ready-to-execute task list to guide development and ensure stakeholder alignment.

How do I create a task list with acceptance criteria for a software refactor?

Creating a task list with acceptance criteria for a software refactor requires phase-driven planning. By guiding discovery and refinement, the process translates refactor goals into a formal plan document containing specific tasks and success criteria for execution.

Does phase-driven planning work for bug fixes and non-trivial development tasks?

Yes, phase-driven planning works for bug fixes and non-trivial development tasks by applying a structured discovery process. It captures constraints and risks, outputting a formal plan document with rationale and a ready-to-execute task list tailored to the specific issue.

What is the best way to document project risks and decision rationales?

The best way to document project risks and decision rationales is through a formal plan document generated by structured planning. It systematically records scope, constraints, and risks while providing a ready-to-execute task list for stakeholder review and handoff.