plan

Plan complex development work with PRD-driven phases and TDD specs.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/jayprimer/pmc-marketplace --skill plan-jayprimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/plan
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill plan-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and coordinating complex work can be error-prone and time-consuming. This Skill provides a structured approach to create PRDs, define phases, tickets with TDD specs, and parallel execution planning to ensure a clean, auditable workflow.

Core Features & Use Cases

  • KB lookup prerequisite to understand existing patterns and SOPs before planning.
  • SCOPE determination to decide between small tickets or larger PRD-driven phases.
  • PRD creation for large work with phased breakdown and traceability.
  • Roadmap updates that reflect tickets, phases, and E2E testing.
  • Ticket creation with 3-spec (TDD) guidance and progress tracking.
  • Parallel analysis to assess dependencies, conflicts, and resource planning.
  • Git setup guidance (phase branches and worktrees) to enable parallel work.
  • Questions resolution process to clarify ambiguity before implementation.

Use cases include planning a new feature that spans multiple files or teams, refactoring with a phased rollout, or any task requiring coordinated multi-step work.

Quick Start

Initiate planning by consulting the KB with /pmc:kb and then generate a phased plan with /pmc:plan.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I plan complex development work that spans multiple files and teams?

Plan complex development work by enforcing a PRD-driven, phased approach that decomposes ambiguous requirements into structured phases. This method supports scope determination and multi-file feature coordination to ensure a clean, auditable workflow.

What is the best way to break down a large refactor into manageable tickets?

Breaking down a large refactor uses scope determination to decide between small tickets or larger PRD-driven phases. It generates phase tickets with 3-spec TDD guidance and progress tracking for a structured rollout.

How do I create a PRD and roadmap for a new software feature?

Create a PRD and roadmap for a new feature by consulting the knowledge base for existing patterns, then generating a phased plan. This produces traceable roadmap updates reflecting tickets, phases, and E2E testing requirements.

Can I use TDD specs within project phases for parallel execution planning?

Yes, you can use TDD specs within project phases for parallel execution planning. The process creates tickets with 3-spec guidance, assesses dependencies and conflicts, and provides Git setup guidance using phase branches and worktrees.

When should I use a PRD-driven phased approach instead of simple tickets for project management?

Use a PRD-driven phased approach instead of simple tickets when handling multi-file features, large refactors, or ambiguous requirements needing structured decomposition. SCOPE determination evaluates the task to decide if simple tickets or larger phases are required.