task-flowlisted

# task-flow ## Overview My end-to-end flow for building a feature with trust. It is a **thin orchestrator** over `superpowers` — it sequences existing skills, it does not re-implement them. One human gate (after the plan); everything else runs automatically with per-task gates. The keystone is an adversarial verifier that re-earns "done" in fresh context. ## When to use - Implementing a feature or non-trivial task from a spec, ticket, or request. - NOT for a one-line fix or a quick question — the ceremony isn't worth it there. ## Phase 1 — understand & plan (auto, adaptive) 1. **`eskills:spec-intake`** — normalize the task into objective, acceptance criteria, constraints, definition of done. It also classifies **greenfield vs brownfield** and flags a **hard-tech challenge** (complex algorithm / performance bottleneck). 2. **If brownfield →** `feature-dev:code-explorer` to understand the existing code before planning. 3. **If hard-tech challenge → SPIKE sub-phase:** explore 2–3 approaches, benchmark candidates if needed (apply `eskills:perf-bar`), and pick the approach **before** committing the plan. Use `deep-research` (if available) / `feature-dev:code-architect` as needed. 4. **`superpowers:brainstorming`** — refine intent and trade-offs. 5. **`superpowers:writing-plans`** — produce the plan, enriched with the template below. 6. Emit the **PLAN + acceptance criteria + subagent design + chosen-approach rationale**. ### Plan template (integrated — not