planning

Translate validated software specifications into repository-aware implementation plans with adversarial review.

8|Updated Jun 18, 2026
One-click install
npx skills add https://github.com/ddobrin/plan-skills --skill planning-ddobrin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/ddobrin/plan-skills/tree/main/plugins/orchestrator/skills/planning
Command: npx skills add https://github.com/ddobrin/plan-skills --skill planning-ddobrin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill translates a validated software specification into a detailed implementation plan before coding begins, reducing missed dependencies, unsafe parallel work, and flawed assumptions.

Core Features & Use Cases

  • Codebase-Aware Planning: Delegates investigation to an architect who maps the specification onto the real repository and creates a micro-stepped plan with exact paths and test commands.
  • Adversarial Plan Validation: Sends the plan through a skeptic-led gate that checks source-level assumptions, identifies the first blocking issue, and records confirmed findings.
  • Safe Execution Handoff: Organizes independent work into parallel groups and requires a clean validation artifact plus explicit user approval before construction begins.
  • Use Case: When a feature specification has passed validation but implementation has not started, use this Skill to produce and validate the plan.md required for development.

Quick Start

Use the planning skill to create and adversarially validate an implementation plan from the validated spec.md and context.md for the specified milestone.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create an implementation plan from a validated software specification?

Implementation planning translates a validated specification into a detailed, executable plan before coding begins. It maps the specification onto your real repository to produce exact file paths, concrete test commands, and micro-stepped tasks required for development.

What is adversarial plan validation and how does it prevent flawed implementation?

Adversarial plan validation sends an implementation plan through a skeptic-led review gate that checks source-level assumptions and identifies the first blocking issue. It records confirmed findings to ensure missed dependencies and flawed assumptions are caught before construction starts.

How do I parallelize independent software development tasks safely?

Safe parallelization organizes independent implementation work into parallel groups based on repository-aware task decomposition. It requires a clean validation artifact and explicit user approval before construction begins to prevent unsafe concurrent code modifications.

When do I need repository-aware task decomposition for feature development?

Repository-aware task decomposition is needed when a validated feature specification must be mapped onto an actual codebase. It generates exact file paths and concrete test commands required to execute complex feature development, bug fixes, or refactors.

What inputs are required for implementation planning before code is written?

Implementation planning requires a validated specification and context artifacts, such as spec.md and context.md. These inputs provide the necessary foundation to generate a detailed plan.md with exact file paths and concrete test commands before coding begins.

Can I use implementation planning for refactoring and bug fixes, or only new features?

Implementation planning applies to feature development, bug fixes, and refactors. Any validated specification requiring repository-aware task decomposition, safe parallelization, and adversarial plan review can be translated into an executable implementation plan.