HE Implement

Execute a PLANS-compliant active plan and keep the plan artifact current.

When to Use

• After he-plan when the initiative is ready for execution
• During re-entry from he-review or he-verify-release for fixes

Key Principles

1. Workspace isolation gate — confirm an isolated workspace is selected and recorded before editing code.
2. Plan-driven execution — implement by Progress items and keep living sections current.
3. Evidence as you go — run relevant tests/commands continuously; do not batch validation at the end.
4. Generated context is a tool — refresh only what matters; keep it usable for reasoning.
5. Unit/e2e by default — avoid mock-only verification unless the repo explicitly documents an exception.
6. Runbooks are additive only — apply any runbook whose frontmatter called_from matches this skill (bash scripts/runbooks/select-runbooks.sh --skill he-implement), but never waive/override anything codified here.

Workflow