deep-plan

Create consensus-reviewed implementation plans with executable verification commands and ADR artifacts.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/npow/claude-skills --skill deep-plan-npow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-plan
Source: https://github.com/npow/claude-skills/tree/main/deep-plan
Command: npx skills add https://github.com/npow/claude-skills --skill deep-plan-npow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns complex software tasks into structured, verifiable implementation plans backed by independent architectural and quality reviews, reducing ambiguity before coding begins.

Core Features & Use Cases

  • Consensus Planning: Coordinates Planner, Architect, and Critic roles to develop and review multi-step implementation plans.
  • Verification and Risk Controls: Requires testable acceptance criteria, executable verification commands, explicit risks and mitigations, and honest termination labels.
  • Decision Documentation: Produces SDD-compatible planning artifacts and an Architecture Decision Record for features, refactors, migrations, bug fixes, and architectural decisions.
  • Use Case: Use it to plan a public API migration, database change, authentication feature, or other multi-step engineering effort before implementation.

Quick Start

Ask the deep-plan skill to create a consensus-reviewed implementation plan for migrating the application authentication flow to token-based authentication.

Frequently Asked Questions about deep-plan

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

FAQPage Schema
How do I create an implementation plan for a complex software migration?

A consensus-reviewed implementation plan requires independent reviews from Planner, Architect, and Critic roles, structured acceptance criteria with executable verification commands, explicit risk mitigations, and ADR-backed SDD artifacts to ensure coordinated analysis before coding.

What is the best way to plan a public API change before coding starts?

Planning a public API change requires consensus reviews from Planner, Architect, and Critic roles, structured acceptance criteria with executable verification commands, explicit risk mitigations, and ADR-backed SDD artifacts to reduce ambiguity before coding.

How do you document architecture decisions for complex software refactoring?

Document architecture decisions for software refactoring by producing SDD-compatible planning artifacts and an Architecture Decision Record that capture multi-step implementation plans, explicit risks, mitigations, and structured acceptance criteria.

Can I use consensus planning for database migrations and authentication features?

Consensus planning applies to database migrations, authentication features, refactors, bug fixes, and architectural decisions, coordinating independent Planner, Architect, and Critic reviews to produce verifiable implementation plans with testable acceptance criteria and risk controls.

Does implementation planning require executable verification commands?

Implementation planning requires testable acceptance criteria paired with executable verification commands, explicit risk mitigations, and honest termination labels to ensure complex engineering tasks are verifiable before coding begins.

When do I need an ADR-backed plan for software development tasks?

An ADR-backed plan is needed for software development tasks involving public API changes, database migrations, authentication work, or architectural decisions requiring coordinated analysis, verifiable acceptance criteria, and documented risk mitigation.