dev-flow

John's master development workflow — the reasoning layer that takes a request from "go work on X" to landed-and-verified. Use when John says "go work on <project>", names a project plus a task, "fix this bug", "implement this feature", or fires a ship go-word ("ship it", "do it", "let's go") about a code-change plan. It routes (resolving the project name to its repo), classifies the work as bug/feature/other, drives the right path, decides when confident enough to PR and when to merge, and picks web-vs-OTA-vs-native-rebuild on landing. It REASONS; it never spells mechanical steps — those are deterministic verbs in the per-repo `.workflow.json` contract, called via the `dev-flow` runner (doctor/prep/gate/smoke/gc/pr) and `dev-up`/`dev-down`. Defers to dev-ship for the standing ship authorization itself, and to drafty-proof-canvas for visual proof. Do NOT duplicate those skills.