planner

Create implementation plans with file paths, dependencies, risks, and rollout order.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/itou-daiki/easy_stat_edu --skill planner-itou-daiki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/itou-daiki/easy_stat_edu/tree/main/.agent/skills/planner
Command: npx skills add https://github.com/itou-daiki/easy_stat_edu --skill planner-itou-daiki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates comprehensive, actionable implementation plans for complex features and architectural refactors, reducing risk and enabling incremental delivery.

Core Features & Use Cases

  • Detailed requirements analysis and dependency mapping for new features and architectural changes
  • Step-by-step implementation plans with explicit file paths, dependencies, risks, and an optimized rollout order
  • Architecture review, risk identification, and strategy for incremental delivery across sprints or milestones

Quick Start

Provide a detailed implementation plan for the requested feature.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I create an implementation plan for complex feature development?

To create an implementation plan for complex feature development, you must perform requirement analysis, map dependencies, and break the work into phased milestones with explicit file paths and risk mitigation strategies.

What is the best way to plan an architectural refactor for incremental delivery?

The best way to plan an architectural refactor for incremental delivery is to review the architecture first, identify risks, and structure the rollout into manageable phases across sprints or milestones to reduce delivery risk.

How do I identify dependencies and risks for a large-scale migration?

Identifying dependencies and risks for a large-scale migration requires detailed requirements analysis and dependency mapping, ensuring that potential roadblocks and implementation risks are documented before execution begins.

Can I use this for step-by-step feature planning with file paths and testing strategy?

Yes, this creates step-by-step implementation plans that include explicit file paths, dependency mappings, risk identification, and a comprehensive testing strategy tailored for feature enhancements and architectural changes.

Does this approach work for planning new product features across multiple sprints?

Yes, this approach works for planning new product features across multiple sprints by providing a phased breakdown with optimized rollout order, ensuring milestones and dependencies are clearly identified for incremental delivery.

When do I need a roadmap for architectural changes and risk management?

You need a roadmap for architectural changes and risk management when tackling complex feature development or large-scale migrations that require comprehensive dependency mapping, phased breakdowns, and explicit risk mitigation strategies.