---

name: planning description: > Generate and optimize PRDs, Implementation Plans, and Progress Tracking documents optimized as AI artifacts for development agents. Use when creating new feature plans, breaking down long planning docs (>800 lines), or setting up progress tracking. Supports: 1) Create PRD from feature request, 2) Create Implementation Plan from PRD with phase breakdown and subagent assignments, 3) Optimize existing plans by breaking into phase-specific files, 4) Create progress tracking with task assignments. Example: "Create a PRD for user authentication feature" or "Break down the sidebar-polish implementation plan into phase files" or "Create progress tracking for data-layer-fixes PRD".

Planning Skill

Generate and optimize Product Requirements Documents (PRDs) and Implementation Plans as AI artifacts - file-based context caches optimized for AI agent consumption.

Purpose

• Generate comprehensive PRDs from feature requests
• Create phased Implementation Plans with subagent task assignments
• Optimize existing planning docs by breaking into token-efficient files
• Set up progress tracking (delegates to artifact-tracking skill)

Key Benefits

---

Quick Start

Create PRD

CopyUser: "Create a PRD for advanced filtering on the prompts page"
# Output: docs/project_plans/PRDs/[category]/advanced-filtering-v1.md

Create Implementation Plan

CopyUser: "Create implementation plan for docs/project_plans/PRDs/features/advanced-filtering-v1.md"
# Output: Main plan + phase files (if >800 lines)

Optimize Existing Plan

CopyUser: "Optimize docs/project_plans/implementation_plans/harden-polish/sidebar-polish-v1.md"
# Breaks 1200-line plan into summary + 3 phase files

Create Progress Tracking

CopyUser: "Create progress tracking for data-layer-fixes PRD"
# Delegates to artifact-tracking skill

---

Core Workflows

---

File Organization

PRDs

Copydocs/project_plans/PRDs/[category]/[feature-name]-v1.md
Categories: harden-polish, features, enhancements, refactors

Implementation Plans

Copydocs/project_plans/implementation_plans/[category]/[feature-name]-v1.md
Phase files (if >800 lines): [feature-name]-v1/phase-[N]-[name].md

See ./references/file-structure.md for complete structure.

---

Templates

---

References

---

Subagent Integration

Plans integrate with 50+ project subagents. Key assignments:

See ./references/subagent-assignments.md for complete mapping.

---

Token Efficiency

Before Optimization

CopyLoad 1200-line plan for any query = 1200 lines context

After Optimization

CopyOverview query: Load 200-line summary only (83% reduction)
Phase query: Load 200 + 400-line phase = 600 lines (50% reduction)

See ./references/optimization-patterns.md for patterns.

---

When to Use This Skill

---

Related Skills

Related Agents

---

Request-Log Integration

When feature requests come from request-log items (REQ-YYYYMMDD-*), update their status:

Copy# Mark item as planned when implementation plan is created
meatycapture log item update DOC ITEM --status planned

# Add note linking to the plan
meatycapture log note add DOC ITEM -c "PRD: docs/project_plans/PRDs/... Implementation plan: docs/project_plans/implementation_plans/..."

Use /mc update and /mc note for token-efficient operations.

---

Version History