strategic-planner

Breaks down features into actionable implementation plans with dependencies and success criteria.

4|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/AreteDriver/ai_skills --skill strategic-planner-aretedriver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategic-planner
Source: https://github.com/AreteDriver/ai_skills/tree/main/skills/strategic-planner
Command: npx skills add https://github.com/AreteDriver/ai_skills --skill strategic-planner-aretedriver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategic planning for complex features helps teams avoid vagueness, identify dependencies, and deliver incrementally with clear success criteria.

Core Features & Use Cases

  • Decompose features into step-by-step implementation plans.
  • Identify dependencies, prerequisites, and milestones.
  • Produce structured plans with acceptance criteria and testing strategy.
  • Use Case: When starting a large feature, generate an actionable plan ready for engineering sprints.

Quick Start

Use the strategic-planner skill to decompose a feature request into a concrete implementation plan with steps, dependencies, and success criteria.

Frequently Asked Questions about strategic-planner

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

FAQPage Schema
How do I break down a feature into an actionable implementation plan?

To create an actionable implementation plan, decompose a feature into step-by-step tasks, identify dependencies, define acceptance criteria, and outline a testing strategy for incremental delivery.

What is the best way to identify dependencies and milestones for product development?

Identifying dependencies and milestones for product development requires decomposing the overall feature into structured tasks, mapping prerequisites, and enforcing clear success criteria for each step.

How do I generate acceptance criteria and a testing strategy for a feature request?

Generate acceptance criteria and a testing strategy by decomposing the feature request into structured implementation plans that enforce measurable success criteria and built-in testing protocols.

Can I use this for project scoping before starting engineering sprints?

Yes, you can use this for project scoping to produce structured, actionable plans with defined dependencies and milestones, ready for engineering sprints before development begins.

When do I need to decompose a feature into step-by-step tasks?

You need to decompose a feature into step-by-step tasks when starting a large feature request to avoid vagueness, identify dependencies, and ensure incremental delivery with clear success criteria.

Does feature planning work without identifying prerequisites and dependencies?

Feature planning avoids vagueness by explicitly identifying dependencies and prerequisites, ensuring teams deliver incrementally with structured, actionable steps and measurable success criteria.