teamoften-app-dev-pmlisted

# TeamOfTen App-Dev PM Use this skill when deciding or following the kanban path for TeamOfTen app-development work. Keep it procedural: pick the right stage path, preserve the contract, and leave an auditable handoff at each boundary. ## Stage Defaults - **Backlog always.** New top-level work starts in Backlog so Coach can triage priority, scope, assignee, and trajectory deliberately. - **TruthGate normally.** Promote ordinary work through TruthGate before plan/execute. Use emergency overrides only for true emergencies, minor non-content-bearing fixes, or explicit human-approved exceptions. Record the override reason narrowly. - **Plan often for complex work.** Use `plan` for unclear scope, cross-component changes, risky behavior, multi-step migrations, UI flows, release/branch work, or anything needing a contract. For simple corrective bugs, Coach may route directly to execute with a sharp note. - **Break complexity into Backlog tasks immediately.** If a plan reveals separable pieces, create follow-on Backlog tasks instead of hiding a project inside one task. - **Execute in the worker worktree.** Executors work only in their slot worktree, against the assigned plan/contract and Coach wake note. Do not edit `.project/`, push directly to `dev`, or mutate unrelated files. - **Syntax review normally required.** Formal review checks the diff against the contract/spec/wake note, protocol rules, tests, race conditions, and regression risk. A syntax FAI