wiggum-plan

Design multi-phase implementation plans for software tasks and write them to .ralph/plans/TASK-ID.md.

45|7|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/wiggum-cc/chief-wiggum --skill wiggum-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wiggum-plan
Source: https://github.com/wiggum-cc/chief-wiggum/tree/main/skills/wiggum-plan
Command: npx skills add https://github.com/wiggum-cc/chief-wiggum --skill wiggum-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill designs and maintains strategic implementation plans for software tasks, ensuring deep understanding and guardrails before any coding starts.

Core Features & Use Cases

  • 7-phase planning workflow (discovery, exploration, clarifying questions, architecture design, plan writing, kanban entry, and summary)
  • Planning-only approach: NEVER implements code; outputs a plan file per task
  • Automatic plan file creation at .ralph/plans/TASK-ID.md and optional task addition to kanban

Quick Start

Invoke the planning skill to generate a plan for an existing TASK, e.g., /wiggum-plan TASK-101; use /wiggum-plan (no args) to audit kanban and identify unplanned tasks.

Frequently Asked Questions about wiggum-plan

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

FAQPage Schema
How do I write an implementation plan for a software task before coding?

Implementation plan writing for software tasks uses a 7-phase workflow covering discovery, architecture design, and plan writing to generate a structured plan file before any coding starts.

Can I generate task plans automatically from an existing kanban board?

Yes, you can audit a kanban board to identify unplanned tasks and automatically generate a dedicated plan file for each task without writing any implementation code.

What is the write-first approach in software task planning?

A write-first planning approach means the workflow focuses strictly on designing architecture and writing plans to a file, ensuring deep understanding and guardrails while never implementing actual code.

Where are software task plan files stored during the planning workflow?

Plan files are stored as markdown documents at the path .ralph/plans/TASK-ID.md, creating a persistent record for each planned task on your board.

Does the planning workflow include adding tasks to the kanban board?

Yes, the planning workflow includes a kanban entry phase that optionally adds newly designed tasks directly to your kanban board after the plan file is written.

What phases are involved in software architecture design and task planning?

The planning workflow involves seven phases: discovery, exploration, clarifying questions, architecture design, plan writing, kanban entry, and summary generation.