planning-and-task-breakdown

Decomposes features into vertical slices with dependency graphs, checkpoint gates, and risk registers.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/ArMaTeC/Redball --skill planning-and-task-breakdown-armatec
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning-and-task-breakdown
Source: https://github.com/ArMaTeC/Redball/tree/main/.devin/skills/planning-and-task-breakdown
Command: npx skills add https://github.com/ArMaTeC/Redball --skill planning-and-task-breakdown-armatec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large feature requests often lead to unstructured implementation, underestimated scope, and horizontal slicing that delays testability. This Skill enforces a disciplined planning workflow that produces thin, independently verifiable vertical slices before any code is written. ## Core Features & Use Cases - Scale Detection: Classifies work as Quick, Standard, or Epic and adjusts planning depth accordingly. - Vertical Slicing with Dependency Graphs: Breaks features into end-to-end slices ordered by dependency, with parallelizable slices marked. - Anti-Rationalization Checks: Flags common agent shortcuts like deferred edge cases, type-first planning, and late testing. - Checkpoint Gates and Risk Register: Defines verifiable gates between phases and documents concrete risks with mitigations. - Use Case: When asked to add a new subsystem to an application, the Skill first reconnoiters the codebase, then writes a feature doc (F-NNN) containing slices, tasks with exact file paths, risks, and gates for review before implementation begins. ## Quick Start Ask the agent to plan the implementation of a new feature, for example: plan adding a scheduled export feature to the settings module.

Frequently Asked Questions about planning-and-task-breakdown

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

FAQPage Schema
How do I break a large feature into smaller tasks?▼

Use vertical slicing: split the feature into thin end-to-end slices where each slice touches all layers (types, data, logic, UI) and has one verifiable acceptance criterion. Order slices by dependency and split any task touching more than five files.

What is vertical slicing in feature planning?▼

Vertical slicing decomposes a feature into minimal working pieces that span all layers from data to UI, rather than building all types first then all UI. Each slice is independently deployable and testable, proving the approach early.

How does the planning skill handle small quick tasks?▼

Quick tasks under 30 minutes with a single file and no unknowns skip the full feature doc. The skill produces an inline task checklist instead, while Standard and Epic scale work goes through all planning steps.

When should I not use a full feature planning doc?▼

Skip the feature doc for single-file fixes with clear solutions and no unknowns. Full planning with dependency graphs and risk registers is intended for multi-file features or cross-cutting epics where sequencing and integration risks exist.

What common planning mistakes does the anti-rationalization check catch?▼

It flags deferring edge cases, building foundations horizontally before testable slices, underestimating multi-file tasks as one task, defining all types upfront, postponing testing to the end, and promising later refactors.