copilot-goal-skill vs. flow

Goal-driven task orchestration with independent verification. Interviews the user to define a clear goal, then loops between a Builder subagent (does the work) and an Inspector subagent (judges the result with fresh context). The Inspector never trusts the Builder. Output is auditable in git commits from each subagent actions. Use when the user says "achieve this goal", "make this work", "implement until done", or wants verified autonomous task completion with independent quality review.

Flow turns Claude into a project partner who manages your backlog. Say "park this for later," and it queues the idea. Say "what's next?" and it finds the highest-priority ready item and offers to start, handling the bookkeeping so you stay in flow. It works as a lightweight scrum board with three ways to interact: talk to Claude conversationally, drag cards on the built-in Kanban board, or run multiple agents in parallel, each with filtered views. All three read and write the same backlog.json, no sync step, no drift. Lanes are fully configurable. Start with the default agile flow (Backlog → Refined → Ready → In Progress → Code Review → Done) or define your own columns and gate rules. The board, the API, and the agent all enforce them consistently. Conversational management: Add, reorder, refine, and complete items by talking naturally; no commands to memorize. Built-in Kanban board: Drag-and-drop web UI that syncs with the agent in real time; launch with one command. Multi-agent support: Leader agents assign