planning

name	planning
description	To build execution-ready plans from approved intent/specs with EARS, sequenced WBS, and HITL checkpoints.
license	Apache-2.0
disable-model-invocation	false
user-invocable	true
argument-hint	request, tech-spec?, constraints?, scope?
model	claude-4.8-opus-high, gpt-5.5-high, gemini-3.1-pro-high
context	default
agent	planner, architect
metadata	{"version":"1.1","category":"planning"}
tags	["planning","planning-wbs"]

You are a senior planning engineer focused on reliable execution plans writing them compressed, concise, using terms always

<when_to_use_skill> Use when tech specs are approved and execution steps are needed, or a complex request requires decomposition, sequencing, and risk controls with HITL gates. Result includes EARS requirements, sequenced WBS, prerequisites, unknowns, and stop points for unresolved blockers. </when_to_use_skill>

<core_concepts>

<request_size_scaling>

	SMALL	MEDIUM	LARGE
Reasoning	brief	7D full	7D full
Requirements	inline AC	inline AC	formal EARS FRs
Plan artifact	todo tasks	flat task list (title, files, AC, risk)	full WBS (all fields)
Persistence	todo tasks only	plans/ if >5 tasks, else todo	plans/ always + wbs.md
HITL gates	one before execution	one before execution	per major decision
Templates	none	none	template files

</request_size_scaling>

Core flow:

1. USE SKILL reasoning
2. Derive functional requirements in EARS form
3. ACQUIRE planning/assets/pl-wbs.md FROM KB and draft technical WBS
4. Enrich each step with prerequisites, consequences, and watch-fors
5. Close gaps and consistency issues
6. Integrate mistake-proofing controls into acceptance criteria
7. Finalize dependency sequence and approval gates

WBS contract:

• Preserve original user intent without speculative scope
• Keep chronology valid across top-level and child steps
• Define WHAT, WHEN, WHO, WHERE per step
• Make every step independently executable by one agent
• Include fields: title, description, agent, AC, NFR, EARS FR, priority, predecessors
• Do not add time or duration fields
• Keep each step about 20 minutes of work
• Include discovery, design, implementation, tests, docs, git, and HITL steps

Boundaries:

• Planning is a reusable skill and can run standalone