planner_skill

Overview

This skill creates comprehensive, phased implementation plans with sprints and atomic tasks for bugs, features, or projects. It produces demoable increments, clear task-level acceptance criteria, file-path hints, test/validation steps, and a filename-ready plan saved as a kebab-case -plan.md file. The output focuses on practical execution, risk mitigation, and rollout/rollback guidance.

How this skill works

First it researches the codebase and analyzes the request to identify scope, dependencies, and edge cases. It then asks clarifying questions to remove ambiguity, retrieves relevant external docs when required, and generates a multi-sprint plan with atomic, testable tasks, demo checklists, and validation steps. After drafting the plan it lists potential gotchas and may request up to three follow-up questions before finalizing.

When to use it

• When you need a step-by-step implementation plan for a new feature or bug fix
• When you want sprints with demoable, testable increments
• When tasks should be atomic, committable, and independently verifiable
• When you need file-path or repo-specific task guidance
• When planning requires dependency mapping or parallel-task coordination

Best practices

• Start by answering 5–10 clarifying questions about goals, scope, and constraints
• Request or attach repo context so tasks can include accurate file paths
• Use small, independent tasks that can be completed and tested in a single commit
• Include demo/verification steps for every sprint to enable incremental validation
• Fetch official docs for external libraries or APIs before drafting tasks

Example use cases

• Plan the implementation of a new OAuth sign-in flow, broken into environment, backend, and frontend tasks
• Draft a multi-sprint migration plan for upgrading a framework or dependency with rollback steps
• Break down a production bug into reproducible tasks, tests, and verification steps
• Design phased delivery for a payment integration with testing and security validation
• Create a test-and-deploy plan for launching a microservice with CI/CD and monitoring