The working solution
A complete route from today's system to the requested result. Understand how the whole thing can work.
A METHOD FOR AI-LED DEVELOPMENTv…
Your intent.
A team of agents.
A finished change.
You describe what should work. LHC gives coding agents the method to research, design, split the work, test it in practice and integrate the result.
Not another code generator. A method for taking responsibility for the whole result.
LHC / EXECUTION MAPILLUSTRATION, NOT LIVE STATUS
01 / HUMAN INTENT
“I want a result I can actually use.”
Leadunderstand → design → orchestrate
LW / 01Interfacebounded task
W / 02Logicbounded task
W / 03Regressionbounded task
Review → deploy → real useFresh eyes. A real user goal. Fix what fails.
Merged where it belongs
→ main / your branchINTENT, NOT A PERFECT SPECIDEAL → USEFUL MINIMUMPARALLEL WORK, ONE OWNERTESTED & INTEGRATED
01 / THE COMPLETE JOURNEY
The whole cycle.
Not just the coding.
The process starts before the first line of code and ends after the result is tried and brought into shared development history.
Loading the current method from Git…
Loading the current method from Git…
A failed user scenario returns to repair, not to a report marked “done”.
02 / FIRST, DESIGN THE RIGHT THING
Think to the ideal.
Build what matters.
Research the code. Compare viable solutions and challenge the assumptions. Then make three passes over one plan, not three implementations.
The ideal version
Improve the plan. Compare alternatives. Let independent criticism expose weak assumptions and unnecessary compromises.
The useful minimum
Cut what does not serve this result. Keep the highest-value changes and deliver the entire accepted outcome.
THIS IS THE VERSION WE BUILD80%
of the ideal's useful value is a design target, not permission to deliver 80% of the promised result.
03 / SMALL TASKS. A SHARED RESULT.
Split the work.
Not the responsibility.
Lead holds the whole objective. Workers own small, verifiable contributions. Independent tasks run together; real dependencies set the order.
ILLUSTRATIVE PLAN / NOT A LIVE TIMELINE∥
Wave 1Wave 2Wave 3
W₁W₂W₃∑◎Delivery time follows the critical path and available capacity, not the sum of every task.
One bounded piece of work
The planned size of a leaf, including its check. Not a timer that kills an agent after 15 minutes.
Owner of the whole outcome
Lead coordinates decisions, dependencies and convergence. Parallel execution never means “someone else will finish it”.
FOLLOW ANY PLAN FROM YOUR PHONE
One link per plan.
One page for all of them.
When a plan is created, the agent gives you its permanent public link once.
- Filter by project and state
- Current step and expected finish
- Stuck plans stand out
ILLUSTRATION OF THE PLAN LIST
In progressagent-herder
Sessions page: rename without restart
Now: connect the mode switch in four adapters
Ends ≈ today 14:45 (in 20 min)Stucknoticeplace
Voice secretary answers the call
No changes for 7 h · stopped at: first audible reply
04 / THE TEST IS SOMEONE USING IT
A green test suite
is not the finish line.
Deploy to the available development environment. Give fresh testers a realistic goal, not your implementation story or a recipe for success.
Is the change sound?
Technical review checks the change and its real regression risk.
Can someone actually use it?
No code. No diffs. A deployed product and a real task. Different personas cover the affected user journeys.
Fix what blocks the goal.
Return observed failures to implementation. Do not turn every preference into a new product requirement.
05 / FINISHED MEANS MERGED
Every session
merges its own work.
A folder full of finished worktrees is not delivery. Publish, review and converge the owned changes into the project's development branch.
feature/interfacefeature/logicfeature/regressionYOUR REPOSITORYmainBranch → PR → merge as soon as checks are green
Someone else's repository: your branch.
Dev integration does not authorize an automatic merge into an external owner's main branch.
The target is configured per project. For shared Airlock work: megamen32-dev. Ownership and actual permissions still apply.
06 / WHO OWNS WHAT
A team, not
an agent parade.
Lead orchestrates; Workers execute. Independent roles challenge decisions and test the result. Each has a responsibility, not a ceremonial place in a queue.
Loading the current method from Git…
THE METHOD IS NOT THE ENTIRE PLATFORM
Keep the boundaries clear.
The backlog chooses the work. Agent Herder manages sessions and harnesses. LHC defines how engineering work reaches a verified result.
DESIGN ≠ IMPLEMENTATION STATUS
This page explains the intended method. It does not claim that every mechanism is already automated. The repository records the remaining implementation gaps.
Read the current limitations ↗FROM AN IDEA TO SOMETHING YOU CAN TRY