Prp Plan

Create comprehensive feature implementation plan with codebase analysis and pattern extraction

Adapted from PRPs-agentic-eng by Wirasm. Part of the PRP workflow series.

Input: $ARGUMENTS

Invoke the planner agent to create a detailed, self-contained implementation plan.

If input is a .prd.md file path: parse Implementation Phases, find the next pending phase, plan that phase. Update phase status from pending to in-progress after plan creation. If input is free-form text: plan the described feature. If blank: ask the user what feature to plan.

Load skills: dog:writing-plans, dog:interface-contracts

The agent will:

  1. Parse input — clarify ambiguities before proceeding (ambiguity gate)
  2. Explore the codebase across 8 categories: naming, error handling, logging, types, tests, config, dependencies, similar implementations
  3. Research external docs if the feature involves unfamiliar libraries or APIs
  4. Design architecture: approach, alternatives considered, scope, NOT building list
  5. Generate plan at .dog/PRPs/plans/{kebab-case-feature}.plan.md using the full PRP template (user story, mandatory reading, patterns to mirror, tasks with VALIDATE)
  6. Report: file path, complexity, estimated files, confidence score (1-10)

Golden Rule: The plan must be self-contained — a developer unfamiliar with the codebase should be able to implement it without additional searches or questions.

Next step: /dog:prp-implement .dog/PRPs/plans/{name}.plan.md