writing-planslisted

# Writing Plans (Umbrella flavor) ## Overview Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. Minimal tests. Frequent commits. Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they don't know good test design very well. > **Umbrella standalone skill** (originally forked from superpowers:writing-plans). Beyond the base flow it adds **walk-tagging** (every task marked `static-verifiable` or `browser-walk-only`) plus a consolidated **Browser-Walk Inventory**, and pins plan output to `docs/plans/`. **Announce at start:** "I'm using the umbrella:writing-plans skill to create the implementation plan." **Context:** If working in an isolated worktree, it should have been created via the `umbrella:using-git-worktrees` skill at execution time. **Save plans to:** `docs/plans/YYYY-MM-DD-<feature-name>.md` - (User preferences for plan location override this default) **Author with:** the block catalog at `$BRIEF_DIR/BLOCKS.md` — plan blocks 24-28, and the `### Task <N>:` heading contract that every `**Depends on:**` edge resolves against. `$BRIEF_DIR` is defined under "Render the Change Brief" below. ## Scope Check If the spec covers multiple independent subsyst