Source-controlled sequence of design specs for upcoming Branchout work.
Each spec describes one cohesive change: a new module, a new subsystem, or a
significant rework. Specs are numbered, kept in dependency order, and live one
per file under docs/superpowers/specs/.
docs/superpowers/specs/
001-<topic>-design.md
002-<topic>-design.md
...
docs/superpowers/plans/
001-<topic>.md # implementation plans, written when a spec is taken on
002-<topic>.md
Specs are produced via the superpowers:brainstorming skill; plans are
produced via superpowers:writing-plans when work begins.
Plain markdown — no YAML frontmatter (renders poorly on GitHub) and no date prefixes (sequence numbers carry order). Sections cover problem, goals, non-goals, architecture, components, data flow, configuration, error handling, testing, migration, and explicit non-goals / future work.
| # | Title | Status | Depends on |
|---|---|---|---|
| 001 | branchout-claude | draft | — |
| 002 | branchout-reviewer | planned | 001 |
| 003 | review-branchout-pr skill | planned | — |
| 004 | packaging (homebrew + debian) | planned | 001, 002 |
Status values: draft (in progress), accepted (ready to plan/build),
in-progress (plan being executed), done (shipped), abandoned (decided
against).