planning-and-task-breakdownlisted

Task ledger: Use when ready decisions need one delegated, dependency-ordered tasks.md with owners, proof, cleanup, and reopen conditions. Own faithful ledger authoring; Skip when behavior remains unresolved, implementation is requested, or root planning-phase ownership and readiness review are needed.
Dankosik/go-service-template-rest · ★ 6 · API & Backend · score 75

Install: claude install-skill Dankosik/go-service-template-rest

# Planning And Task Breakdown Must read [Planning](../../../docs/spec-first-workflow/phases/planning.md); it owns the ledger shape and readiness boundary. Build the smallest candidate ledger from implementation-changing accepted obligations. Give each task an owner, real dependencies, matching proof, and cleanup or reopen condition only when present. Do not create waves for sequential work. Authoring ends when the next task or real parallel wave can execute without inventing policy; escalate only blockers that can invalidate that work.