super-plan

Generate evidence-backed design documents with approval gates before coding.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/asochan-ai/claude-plugins --skill super-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: super-plan
Source: https://github.com/asochan-ai/claude-plugins/tree/main/plugins/super-plan/skills/super-plan
Command: npx skills add https://github.com/asochan-ai/claude-plugins --skill super-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Super Plan enables teams to produce evidence-backed design documents before coding, preventing costly rework caused by insufficient research, ambiguous scope, and late stakeholder alignment.

Core Features & Use Cases

  • Stepwise design workflow: scope definition, persona & quality attribute selection, and thorough risk assessment before implementation.
  • Artifact generation: reusable design documents, evidence-backed plan artifacts, and a clear task plan that feeds rapid-build and ensures governance.
  • Guardrails: explicit approval gates and instruction to replan when evidence is missing or scope is unclear.

Quick Start

Run the super-plan workflow to generate a structured, evidence-backed design document ready for stakeholder review.

Frequently Asked Questions about super-plan

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

FAQPage Schema
How do I create an evidence-backed design document to prevent software rework?

An evidence-backed design document includes frontmatter requirements, scope definitions, persona selections, risk assessments, and stakeholder approval gates. It enforces a multi-step workflow that generates structured artifacts, ensuring alignment and research are captured before coding begins.

What is the best way to structure a planning workflow for complex software projects?

A structured planning workflow for complex software projects requires stepwise task decomposition: define scope, select quality attributes, assess risks, and generate reusable design artifacts. This enforces formal governance and stakeholder approval gates before implementation.

How do I enforce stakeholder approval gates before starting implementation?

You enforce stakeholder approval gates by integrating explicit review checkpoints into your planning workflow. The process instructs you to replan when evidence is missing or scope is unclear, ensuring formal stakeholder alignment is achieved before coding begins.

Can I use task decomposition to generate a clear implementation plan from a design doc?

Yes, task decomposition generates a clear implementation plan from a design doc by producing a structured task plan. This plan feeds rapid-build processes and ensures governance through evidence-backed plan artifacts derived from the approved scope.

When should I replan a software design document due to missing evidence?

You should replan a software design document when evidence is missing or the project scope is unclear. The workflow includes explicit guardrails that trigger a replan to ensure all design documents remain evidence-backed before receiving formal stakeholder approval.

Does evidence-first planning work for complex software projects with external research?

Yes, evidence-first planning works for complex software projects requiring internal and external research. It applies scope definitions, persona selections, and risk assessments to ensure comprehensive alignment and governance before implementation begins.