megamen32/last-human-commit

Design a working solution when boundaries, data ownership or costly assumptions remain uncertain; test pivotal choices, independently challenge the design, then simplify into complete outcomes and dispatchable tasks.

Compatibility alias for older LHC assignments that request bugfix TDD. Prefer worker-bugfix for new Worker defect tasks; use this only when an existing task or caller explicitly names bugfix-tdd.

Lead-owned least-cost procedure for proving and handing off the accepted business result.

Independently challenge an important proposal or synthesis with counterexamples, alternative explanations and a minimal evidence-producing check.

Use independent strong models to propose and challenge solutions, synthesize a better decision, recheck the synthesis and resolve disputed assumptions with evidence.

Let the strongest suitable Lead turn a goal into coherent model-assigned tasks, dependency-aware parallel lanes and verified integration joins.

Compatibility alias for older LHC assignments that request feature implementation. Prefer worker-code for new Worker coding tasks; use this only when an existing task or caller explicitly names feature-implementation.

Run diverse independent goal-driven Testers on the real product, synthesize observed obstacles, repair them and retest through a closed product-improvement loop.

Convert observed failures and successful methods into tested, retrievable skills, tools or routing changes, then verify reuse and retire ineffective guidance.

Use for engineering tasks that need the Last Human Commit workflow, bounded roles, and a real product canary.

Legacy recovery only. Use solely when the user explicitly selects old Fleet file rollout or rollback for Last Human Commit; never for ordinary plugin install, update, or delivery. Preserves deterministic preview, exact apply, verification and rollback receipts.

Update Last Human Commit sources, regenerate the canonical Agent Plugins package, validate, commit and push, then install or update through each selected harness's native plugin marketplace or manager and prove its installed loader. Use for LHC prompts, roles, protocols, commands, skills, or plugin delivery changes.

Fixed iteration loop for turning a reviewed defect list into a pushed, real-surface-proven result — parallel worker fixes, adversarial critique round, delta re-critique, converge at SHIP. Use when a review, audit, or incident produced concrete findings.

Choose and improve model assignments for Lead, executors and independent verification using task difficulty, actual capabilities, acceptance evidence and total cost.

Lead-owned business-first procedure for choosing the least-cost route to the next real canary.

Mandatory final-gate procedure for proving a user-facing result on the real surface, with the interaction tool ladder (a11y tree -> browser MCPs -> CDP/Playwright -> XY clicks) and evidence rules.

Lead-owned claim-calibrated procedure for a controlled consequential release action.

Split a large or stalled task into the smallest independent, parallel, business-verifiable slices. Use when planning work, assigning Workers, an estimate exceeds 20 active minutes, routes are entangled, or progress has produced little business delta.

Independently attempt a user goal through a real browser, device, application or CLI, returning observable usability and behavior evidence without reading implementation.

Worker-owned least-cost bug-fixing procedure for one bounded behavior failure. Use when a symptom, regression, broken business flow, failing test, or production-path defect must be reproduced, localized, and fixed. Reuse prior failure shields, prefer rg for fresh source tracing, choose the cheapest discriminating red proof, make the smallest coherent fix, and preserve a reusable root-cause map entry when recurrence is likely.

Worker-owned implementation procedure for writing the smallest coherent code change on the real business path. Use for a bounded feature, integration, endpoint, UI flow, adapter, or production-path implementation after the accepted outcome is known. Reuse verified project knowledge, confirm it with rg, ship the thinnest usable vertical, ask Lead non-blockingly at product decisions, and stop when the requested claim is proven.

Worker-owned least-cost codebase research for tracing real production paths, locating symbols and ownership, testing hypotheses, and handing Lead a decision-ready implementation route. Use for read-only repository investigation, architecture orientation, root-cause localization, the research stage of a bounded bugfix, or any task likely to repeat earlier code-location research. Search the reusable project code map first, prefer rg for fresh source truth, use Graphify only for genuinely multi-hop relationships, and use context-mode to process large outputs without flooding context.