superpowerslisted

# Superpowers — Process Discipline Vendored from [obra/Superpowers](https://github.com/obra/Superpowers) (MIT, Jesse Vincent), compressed to house style — see `NOTICE.md`. These are **process skills**: they decide HOW to approach a task and run BEFORE implementation skills. On conflict, this repo's `01-operating-system` + `rules/*` + Brian's preferences win. ## The flow (route by where you are) 1. **Starting anything creative?** → `brainstorming/SKILL.md` — explore intent + design before code. Non-negotiable first step. 2. **Have requirements, multi-step?** → `writing-plans/SKILL.md` — write the plan before touching code. 3. **Work needs isolation?** → `using-git-worktrees/SKILL.md` — spin an isolated workspace (`[[main-only-branch]]`). 4. **Executing the plan?** → `subagent-driven-development/SKILL.md` — one subagent per task + two-stage review (`[[monitor-orchestration]]`, `[[parallel-subagent-economy]]`). 5. **Before merge?** → `requesting-code-review/SKILL.md` — dispatch the `code-reviewer` agent + Agent Diversity Review (`[[agent-selection]]`). 6. **Got feedback?** → `receiving-code-review/SKILL.md` — verify it technically, then act; no blind agreement. 7. **Tests green, done?** → `finishing-a-development-branch/SKILL.md` — merge / PR / cleanup (`[[no-staging-doctrine]]`, auto-push). **Authoring a skill itself?** → `writing-skills/SKILL.md` + `[[skill-authoring-contract]]` (the house authoring rule, where the SDO / match-the-form / ordered-by-weight insights now live