One-click install
npx skills add https://github.com/Dawn-Technology/aicelerate --skill scope-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-plan
Source: https://github.com/Dawn-Technology/aicelerate/tree/main/plugins/aimate/skills/scope-plan
Command: npx skills add https://github.com/Dawn-Technology/aicelerate --skill scope-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn a request into a deterministic, implementation-ready technical plan with a defensible time estimate instead of vague next steps.

Core Features & Use Cases

  • Resolves the full design tree first by classifying each decision as Observed, Decision, or Assumption, and prompting you only when something blocks planning.
  • Breaks work into small, testable tasks with clear subagent boundaries and explicit file-level responsibilities so another engineer can execute the plan with limited context.
  • Produces a time estimate derived from task breakdown based on the derived functional requirements and shared boundary impact.

Quick Start

Ask for a technical implementation plan and estimate for your feature, and include any key decisions you already know so the planner can close the design tree before estimating.

Frequently Asked Questions about scope-plan

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

FAQPage Schema
How do I create a technical implementation plan with a time estimate?

To create a technical implementation plan with a time estimate, you provide functional requirements in product-owner language. The planner resolves a complete design tree, classifies decisions, and breaks work into testable tasks to derive a defensible time estimate.

What is a design tree in software implementation planning?

A design tree in software implementation planning is a structure that resolves all technical requirements by classifying each branch as Observed, Decision, or Assumption. It ensures dependency-order decisions are made before task breakdown begins.

How do I break down software tasks into testable units for another engineer?

To break down software tasks into testable units, the planner defines explicit task hierarchies with acceptance criteria and clear subagent boundaries. It assigns file-level responsibilities so another engineer can execute the plan with limited context.

Do I need fully defined requirements to get a software estimation?

You do not need fully defined requirements to get a software estimation. You provide functional requirements in product-owner language, and the planner prompts you for user confirmation only when an unknown blocks the planning process.

How to handle edge cases and assumptions during task breakdown?

To handle edge cases and assumptions during task breakdown, the planner explicitly maps them as Assumption or Observed branches within the design tree. It considers error and edge-case scenarios while defining acceptance criteria for each task.

What is the best way to estimate time for a feature with unresolved dependencies?

The best way to estimate time for a feature with unresolved dependencies is to resolve the complete design tree first. By making dependency-order decisions and classifying unknowns, the planner produces a deterministic time estimate derived from the task breakdown.