How a feature ships here

The superpowers build loop, with a real shipped feature as evidence: brainstorm → spec → plan → TDD → review → merge-commit PR.

6. The build workflow (how every feature here was shipped)

Donna is built with the superpowers skill loop. For any non-trivial change, follow it:

Brainstorm (superpowers:brainstorming) → a design doc in docs/superpowers/specs/.
Plan (superpowers:writing-plans) → a task-by-task plan in docs/superpowers/plans/.
Execute (superpowers:subagent-driven-development) — a fresh implementer subagent per task, each doing TDD (failing test → implement → green → commit), followed by two-stage review (spec compliance, then code quality) per task.
Whole-branch review (Opus) before the PR.
PR with a merge commit. Commit + push per task as you go.

Scale the ceremony to the change: a one-line fix doesn't need a spec, but anything that adds a surface or touches a contract does. The specs/plans for every shipped phase are archived under docs/superpowers/ — read the closest analog before building (e.g. mirror how Playbooks did list→detail→execute→poll→typed results, or how Automations threaded memories_total through the receipt chain).