planning-workflow

name	planning-workflow
description	Use when splitting scope into executable implementation slices, or when strengthening test and acceptance coverage (implementation breakdown, delivery slices, task decomposition, test breakdown, acceptance, integration test, verification planning).
argument-hint	Target to break down, e.g.: write tranche, admin queries, report catalog — with "tests" suffix for verification planning
user-invocable	true

Planning Workflow

Covers implementation breakdown and test/acceptance breakdown — the full planning phase before execution begins.

Module Routing

Identify the task, then load only the matching module via read_file before proceeding.

Task	Module
Design is stable and needs to be split into reviewable implementation slices	modules/feature-breakdown.md
A delivery scope, slice, or service needs explicit layered verification and acceptance coverage	modules/test-breakdown.md

Load exactly one module, then follow its Procedure section.

Typical Flow

feature-breakdown  →  execution-workflow
        ↓ (when risk or cross-service scope is high)
   test-breakdown  →  verification plan

For simple slices, keep verification inside the implementation breakdown. Create a standalone test breakdown only when isolation risk is high, cross-service verification is required, or the verification matrix exceeds ~10 scenarios.

When Not to Use This Skill

• Design is not yet stable → use design-workflow first
• An approved slice is ready for execution → use execution-workflow
• Documents need to be moved, renamed, or archived → use document-lifecycle-workflow