project-flow-ops

# Project Flow Ops <skill_contract> <input>Project objective, tasks, owners, dependencies, budgets, artifacts, current states, and definitions of done.</input> <output>A WIP-limited project state with ranked work, explicit blockers, bounded actions, and verified closure receipts.</output> <done>Every active item has one owner and observable artifact, and completion is backed by its named fresh verification.</done> <non_goals>Hidden WIP, duplicate ownership, status by intuition, backlog accumulation, or completion without evidence.</non_goals> Maintain a small, inspectable project state machine: `BACKLOG -> ACTIVE -> BLOCKED | COMPLETED`. Optimize flow and verified outcomes, not task volume. ## Usage Template Provide: project objective, current tasks, owners, dependencies, time budget, artifacts, and definition of done. Optional: prior review receipts. ## Workflow <intake> Normalize each item into `{id, objective, owner, state, artifact, definition_of_done, budget, dependencies}`. Reject duplicate ownership and distinguish waiting from active execution. </intake> <unknowns_gate> If an active item lacks an owner, artifact, or observable definition of done, return `NEEDS_INPUT`. Probe the ambiguity with the largest impact on scheduling; do not guess priority from wording alone. </unknowns_gate> <execute> 1. Rank work by objective impact, urgency, dependency leverage, and cost of delay. 2. Limit `ACTIVE` to one or two items per owner. 3. Decompose the selecte...