planner

Create step-by-step plans with approaches, risks, and verification checkpoints.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/tim-hub/role-based-skills --skill planner-tim-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner
Source: https://github.com/tim-hub/role-based-skills/tree/main/planner
Command: npx skills add https://github.com/tim-hub/role-based-skills --skill planner-tim-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converting ambiguous goals, complex technical challenges, or feature requests into a clear, ordered set of verifiable steps while surfacing trade-offs, risks, and rollback options so teams can proceed with confidence.

Core Features & Use Cases

  • Structured planning workflow: Clarify goals, gather context, propose multiple approaches, and build a prioritized step-by-step plan.
  • Risk and trade-off analysis: For each major decision, provide pros/cons, likelihoods, impacts, and mitigations.
  • Multiple planning modes: Supports problem solving, debugging investigations, feature implementation, architecture design, migrations, and refactors.
  • Use Case: Turn a vague request like "improve login reliability" into a phased implementation plan with verification checkpoints, rollback strategies, and T-shirt sized estimates.

Quick Start

Create a step-by-step plan to implement OAuth login for our web app, including alternative approaches, pros and cons, key risks, and verification steps.

Frequently Asked Questions about planner

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

FAQPage Schema
How do I create a step-by-step plan for debugging a complex system issue?

To create a debugging plan, define the investigation goal, gather context, and build an ordered, verifiable execution plan. This includes proposing candidate approaches, analyzing pros and cons, and setting verification checkpoints to isolate the root cause.

What is the best way to turn a vague feature request into an actionable roadmap?

Turning a vague request into an actionable roadmap requires clarifying the objective, proposing multiple approaches, and prioritizing structured steps. The resulting roadmap includes T-shirt sized estimates, risk mitigations, and rollback strategies for confident execution.

How do I plan an application migration with proper risk analysis and rollback strategies?

Planning an application migration involves creating a phased, step-by-step plan with built-in risk analysis. You identify likelihoods and impacts of potential failures, propose mitigations, and define explicit rollback strategies at verification checkpoints.

Can I use this structured planning approach for system architecture design and refactoring?

Yes, structured planning supports architecture design and refactoring scenarios. It clarifies architectural goals, compares candidate designs through pros and cons analysis, and sequences verifiable implementation steps to ensure system stability.

Do I need to provide specific technical context for generating a feature implementation plan?

Yes, providing specific technical context is necessary for generating an accurate feature implementation plan. The planning workflow requires clarifying goals and gathering contextual details to propose viable approaches, identify risks, and establish relevant verification steps.