he-implement

Plan-driven execution automates software development by reading active execution plans and managing milestone progress. It writes code, runs tests, and updates the plan artifact with completed steps and discoveries incrementally.

Milestone tracking in software implementation progresses through defined development stages, updating living plan artifacts with outcomes and discoveries. It ensures parallel subagent tasks are managed while maintaining continuous evidence gathering.

You can run coding tasks from a markdown plan file by executing active execution plans directly. The system reads the `.md` file, implements tasks according to defined milestones, and commits work using conventional messaging.

Parallel subagent tasks are supported for software development, managing multiple implementation streams simultaneously. The system ensures workspace isolation while executing plan-driven implementation and gathering continuous verification evidence.

Plan execution integrates changes incrementally and commits work according to conventional commit messaging. It updates living plan artifacts with outcomes and discoveries gathered during the implementation process.

Automated plan execution requires pre-existing active execution plans to function. It is limited to implementing tasks defined in plan artifacts and cannot generate plans independently, relying on external plan creation first.