workforce-planning-brieflisted

# Workforce Planning Brief ## Why this skill exists, and why it's gated A workforce planning brief is easy to fill in badly: four sections, a handful of bullet points each, done in one pass. The problem is that a single-pass brief reliably misses two things that only show up under scrutiny — the business logic connecting the plan to the company's actual strategy, and full coverage of the standard categories a reviewer expects (every canonical risk type, every stated talent gap represented in a success criterion). Both are invisible from inside a single draft; they only surface when someone checks coverage against a list, and by then the brief is "done" and nobody checks. So this skill is not "fill in four sections." It is a sequence of gates, each one closing off a specific way this kind of document goes wrong. Skipping a gate to save time reliably reproduces the exact gaps this skill exists to prevent — so don't skip them, even when the user seems to be in a hurry. If the user explicitly wants a fast, ungated single pass, say so out loud before doing it, so they know they're trading rigor for speed. ## The state file — how sequencing works Before doing anything else, look for `workforce-plan-status.json` in the user's working directory (or wherever they're building this brief). This file is what lets the process be resumed out of order, across sessions, instead of forcing a rigid restart every time. - **No file found** → this is a cold start. Go to `00-intake/INSTRUCTI