plan

Generate dependency-ordered plans with rationale and acceptance criteria.

1|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill plan-aibilitycz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/aibilitycz/superpowered-toolkit/tree/main/plugins/super-intelligence/skills/plan
Command: npx skills add https://github.com/aibilitycz/superpowered-toolkit --skill plan-aibilitycz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategic planning for new features, bugs, or refactors by producing an actionable plan document with tasks, reasoning, and acceptance criteria.

Core Features & Use Cases

  • Generates dependency-ordered tasks with rationale
  • Documents decisions, risks, and assumptions to guide execution
  • Use when starting a feature, fix, or refactor to align teams and kickoff work

Quick Start

Provide a feature brief or select a brainstorm, and ask me to generate an auto-calibrated plan with tasks and acceptance criteria.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a dependency-ordered plan for a new feature?

To generate a dependency-ordered plan for a new feature, provide a feature brief and the tool will output an actionable plan document with tasks, rationale, and acceptance criteria.

What is task decomposition and risk analysis in project planning?

Task decomposition and risk analysis in project planning involve breaking down complex features into dependency-ordered tasks while documenting potential risks and assumptions to guide execution.

Can I use this planning approach for both solo and multi-team projects?

Yes, you can use this planning approach for both solo and multi-team projects across discovery, design, and implementation phases to align teams and kickoff work.

How do I document decision rationale and assumptions for a refactor?

Document decision rationale and assumptions for a refactor by generating a comprehensive plan document that explicitly records reasoning, risks, and acceptance criteria for the work.

What is the best way to align teams and kickoff work for a bug fix?

The best way to align teams and kickoff work for a bug fix is to produce an auto-calibrated plan with dependency-ordered tasks and clear handoff outputs for execution.

When do I need a comprehensive plan document with acceptance criteria?

You need a comprehensive plan document with acceptance criteria when starting a feature, fix, or refactor to ensure strategic alignment, document assumptions, and guide implementation.