hyperflow-plan

# hyperflow-plan — planning phase (Antigravity single-agent) Thinking, not building. The only writes are to `.hyperflow/`. Each phase skips itself when the request doesn't need it. Follow the `hyperflow` doctrine (autonomy, file-first, AskUserQuestion gates). ## Steps 1. **Amplify (skippable).** If the prompt is rough, rewrite it into its strongest form — role · task · context · constraints · output spec. Skip when it's already specific. Never inflate a one-line ask into a spec. 2. **Research first.** Read the relevant code, `AGENTS.md`, and `.hyperflow/memory/*`. Map the affected surface yourself — do not ask what the code answers. 3. **Design (skippable).** For an open-ended request: ask ≥2 clarifying questions (what/which/where only), propose 2–3 approaches, then design section-by-section into `.hyperflow/specs/<slug>.md` with approval per section. A clear request bounces straight to decomposition. When a system, UI, motion, or mobile surface is in scope, ground the design in the matching standards (architecture decomposition + a diagram, the design system, the Motion language, the mobile platform/device matrix). 4. **Decompose.** Produce a topologically-ordered batch graph; each sub-task = one conventional-commit-sized change. **Split any sub-task** touching >5 files, >500 LOC, 2+ subsystems, or >10-min review. Write `.hyperflow/tasks/<slug>.md`: status table → Goal → Why → Scope-at-a-glance → Affected files → Execution plan → Batches (role, files, complexity, acceptan...