elroykanye/vince-gate

Keep Vince task updates action-first, concise, and easy to resume. Use after a Vince workflow starts or when the user asks for a shorter, clearer status; do not use to replace evidence or safety decisions.

Safely clean leaked worktrees, attributable processes, background jobs, and regenerable output after a task. Use for cleanup, locked directories, failed worktree removal, stray processes, or unexplained workspace disk use.

Diagnose and safely repair Vince install drift, broken bindings, stale profiles, missing paths, orphaned tasks, and undiscoverable skills. Use when Vince behaves incorrectly, after major repository changes, or for a Vince health check.

Write or publish factual task completion documentation from the contract, diff, evidence, and deployment state. Use for completion-documentation.md, task documentation, release handoffs, or publishing to the profile’s configured destination.

Execute repository features, fixes, and refactors with contract confirmation, test-first RED/GREEN/TAMPER evidence, end-to-end proof, and fresh Vince review. Use for any request that changes code or shipped behavior.

Turn vague, contradictory, impossible, unsafe, unauthorized, or unbounded implementation requests into an actionable contract or a clear refusal before vince-implement starts. Use when a request may not be ready for implementation; do not use for ordinary questions that require no repository change.

Promote recurring review findings and user corrections into Vince lessons, known traps, definition-of-done gates, and evidence-based metrics. Use after a PASS, during adoption, or when reviews repeatedly catch the same class of problem.

Review a task against its stated requirements and relevant tests, then write PASS or FAIL and stop. Use to check whether requested work is done, not for a general audit.

Choose the least expensive capable model and narrowest useful agent role for an implementation task using exact harness-specific mappings from the project profile. Use before implementation planning, delegation, or review; recommend a user-visible model switch when warranted without weakening verification.

Create or refresh a verified Vince project/workspace profile containing real commands, branch and version rules, security boundaries, wire rigs, traps, and exact model mappings. Use for Vince onboarding, missing profiles, or repository convention drift.

Safely upgrade or roll back Vince at the recorded scope and bindings, preserving in-place edits and migrating new profile fields honestly. Use to update Vince, check its version, repair an outdated install, or pin a release.