writing-board-taskslisted

# Writing Board Tasks **Derived from superpowers:writing-plans.** Same decomposition discipline and self-review habits — reads the **design spec** directly and outputs **task files** for GitHub issues (skips the intermediate plan file). ## Overview Decompose a **feature design spec** into **board task files**. Each file becomes one GitHub issue and one PR through super-board Build → QA → Review. Assume the Builder agent has **only the issue body** plus `PROJECT.md` — not your session history. The spec on `main` is background; the task file is the **dispatch contract**. **Announce at start:** "I'm using the writing-board-tasks skill to create super-board task files." **REQUIRED INPUT:** Design spec at `docs/superpowers/specs/<feature-slug>-design.md` (from Step 16 — refining-spec, office-hours copy, or brainstorming). **OPTIONAL INPUT:** An existing `docs/superpowers/plans/…` file if the user already ran `writing-plans` — use it as extra detail, but do not require it. **Save task files to:** `docs/superpowers/tasks/<feature-slug>/NN-short-name.md` - One file per board task (PR-sized — not micro-steps) - Template: `docs/templates/task-file.md` - Issue quality bar: `docs/templates/issue.md` ## Scope Check If the spec covers multiple independent subsystems, suggest separate feature slugs — one task folder per subsystem. Each board task should produce working, testable software on its own **after its dependencies merge**. ## Decomposition (writing-plans discipline, spe