skills.rest
phj128
phj128COMMUNITY
Explore all skills by this author →
WebsiteGitHub

deep-plan

Run a five-phase planning workflow that outputs a plan-ready artifact.

17|3|Updated Mar 24, 2026
Search Tags:#planning#project-management#acceptance-criteria#plan-mode#task_plan.md#structured-discussion#ai-planning
One-click install
npx skills add https://github.com/phj128/autoworker --skill deep-plan-phj128
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-plan
Source: https://github.com/phj128/autoworker/tree/main/skills/deep-plan
Command: npx skills add https://github.com/phj128/autoworker --skill deep-plan-phj128

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan work often reaches Plan Mode with shallow questioning, risking vague goals and unclear criteria. deep-plan enforces a rigorous, multi-phase inquiry to surface motivation, assumptions, design decisions, and explicit acceptance criteria before a plan is produced.

Core Features & Use Cases

  • Five-phase deep discussion that covers motivation, assumptions, solution concepts, acceptance criteria, and consolidated planning output.
  • Early risk visibility by surfacing and validating core assumptions, reducing rework in later phases.
  • Plan generation by producing a structured plan file that autoworker:subtask-init can extract from.
  • Adaptable to non-trivial tasks requiring deeper exploration before execution.

Quick Start

Enter Plan Mode and run the deep-plan phase to generate a complete plan file that autoworker:subtask-init can extract.

Frequently Asked Questions about deep-plan

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

FAQPage Schema
How do I create structured project management plans with clear acceptance criteria?▼

Structured project management plans require a multi-phase deep discussion workflow that explores motivation, validates assumptions, and defines explicit acceptance criteria before generating a plan-ready artifact.

What is the best way to enforce thorough planning before starting non-trivial tasks?▼

Thorough planning for non-trivial tasks is enforced by running a five-phase inquiry in Plan Mode that surfaces design decisions and core assumptions, reducing rework risk in later execution phases.

How do I generate a task_plan.md file that downstream execution can extract from?▼

To generate a task_plan.md file, enter Plan Mode and run the deep planning workflow, which consolidates the structured discussion output into a plan-ready artifact for automated extraction.

Does deep-plan work with autoworker:subtask-init for automated task execution?▼

Yes, deep-plan produces a structured plan file that autoworker:subtask-init can directly extract from to drive automated task execution after the planning phases complete.

When should I use a multi-phase planning workflow instead of standard Plan Mode?▼

A multi-phase planning workflow should be used for non-trivial tasks requiring deeper exploration of motivation and design decisions, as standard Plan Mode often reaches vague goals with shallow questioning.

Why does my project planning fail with unclear goals and missing acceptance criteria?▼

Project planning fails with unclear goals when shallow questioning skips assumption validation, whereas a rigorous five-phase inquiry surfaces motivation and explicit acceptance criteria before execution.

Related Skills

Explore More Product & Management Skills→
KubrickCodeKubrickCode
1

work-execution-plan-documentation

Create structured work execution plans with goals, scope, and task order.

Community
Basic
phj128phj128
17

subtask-plan

Automates preparation and verification of carpentry and other craftwork estimates and invoices.

Community
Advanced
phj128phj128
17

autoworker

Automate end-to-end implementation tasks with a state-machine workflow and quality gates.

Community
Advanced
product-on-purposeproduct-on-purpose
527

develop-design-rationale

Document UX design decisions with context, options, and trade-offs.

Official
Basic