Skill

create-plan

Create a structured feature implementation plan as a markdown document with progress tracking, status indicators, critical decisions, and modular task breakdown. For multi-session or ticket-driven work, creates a full ExecPlan living document.

Install

npx claudepluginhub arosenkranz/claude-code-config --plugin workflow-skills

Tool Access

This skill uses the workspace's default tool permissions.

Preview

> **[DEPRECATED]** Candidate for removal (2026-03-03). Replaced by plan mode (simple tasks) and ExecPlan template (multi-session). If unused by 2026-03-17, delete this skill.

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

157.7k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

157.7k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

157.7k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 6, 2026

Actions

View Source View Plugin View on GitHub View README

[DEPRECATED] Candidate for removal (2026-03-03). Replaced by plan mode (simple tasks) and ExecPlan template (multi-session). If unused by 2026-03-17, delete this skill.

Plan Creation Stage

Based on our full exchange, produce a plan document. Choose the appropriate mode:

Mode Selection

Quick mode — for simple tasks (fewer than ~5 steps, single session, no ticket ID): Produce a lightweight checklist plan inline or as a file.

ExecPlan mode — for multi-step, ticket-driven, or potentially multi-session work: Use the ExecPlan specification at ~/.claude/templates/PLANS.md. Save the plan to: ~/workspace/work-artifacts/<TICKET-ID>/<TICKET-ID>-plan.md

When in doubt, default to ExecPlan mode. A plan that can be resumed by any agent without conversation history is always more valuable than one that cannot.

Quick Mode Template

Requirements:

Include clear, minimal, concise steps.
Track status with checkboxes.
Include dynamic tracking of overall progress percentage (at top).
Do NOT add extra scope or unnecessary complexity beyond explicitly clarified details.
Steps should be modular, elegant, minimal, and integrate seamlessly within the existing codebase.

# Feature Implementation Plan

**Overall Progress:** `0%`

## TLDR
Short summary of what we're building and why.

## Critical Decisions
Key architectural/implementation choices made during exploration:
- Decision 1: [choice] - [brief rationale]
- Decision 2: [choice] - [brief rationale]

## Tasks:

- [ ] **Step 1: [Name]**
  - [ ] Subtask 1
  - [ ] Subtask 2

- [ ] **Step 2: [Name]**
  - [ ] Subtask 1
  - [ ] Subtask 2

ExecPlan Mode

Follow the full ExecPlan specification at ~/.claude/templates/PLANS.md. The plan must include:

Progress table with per-step status
Surprises & Discoveries section
Decision Log table
Outcomes & Retrospective section
Explicit acceptance criteria for each step

Once the plan is written, tell the user they can execute it with:

"Use the execplan-executor agent to execute ~/workspace/work-artifacts/<TICKET-ID>/<TICKET-ID>-plan.md"

Again, it's still not time to build yet. Just write the clear plan document. No extra complexity or extra scope beyond what we discussed.