harness-wip-control

What problem does it solve? Broad requests like "add X" or "refactor Y" often lead to scope creep, half-finished changes, and lost context. This Skill enforces a WIP=1 (work-in-progress limit of one) discipline so only a single atomic task is active at any moment, with everything else explicitly deferred. ## Core Features & Use Cases - Request Decomposition: Restates the broad request, lists all implied sub-tasks, and orders them by dependency before any code is written. - WIP=1 Contract: Marks exactly one task as in_progress in feature_list.json; newly discovered work is recorded as not_started instead of being started immediately. - Observable Acceptance Criteria: Requires runnable commands as acceptance criteria and explicit non-goals for the session. - Use Case: When asked to "improve the API layer", the Skill produces a dependency-ordered task list, activates only the first atomic unit, and records the rest as pending with clear exclusions. ## Quick Start Ask the agent to decompose your broad feature request into atomic tasks and start only the first one using the WIP control workflow.