[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MP8F7VWRPHTSQF2NF76RTB":3,"skill-same:01M6MP8F7VWRPHTSQF2NF76RTB":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":31,"linkOnly":32,"markdownContent":33,"markdownBody":34,"frontMatter":35,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":41,"ownerHtmlUrl":42,"ownerBlogUrl":43,"ownerDescription":44,"updatedAt":45,"install":46,"resources":59},"01M6MP8F7VWRPHTSQF2NF76RTB","executing-plans",null,"Use when executing an implementation plan linearly with explicit human checkpoints between batches of tasks.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fexecuting-plans\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30],"executing plans","plans","tasks","plan","use","implementation","human","with","batches","checkpoints","implementation plan","when","2026-11-10 10:12:30",false,"---\nname: executing-plans\ndescription: Use when executing an implementation plan linearly with explicit human checkpoints between batches of tasks.\n---\n\n# Executing Plans (Linear with Checkpoints)\n\nExecute the plan task by task. Pause after every 3 tasks for human review.\n\nThis remains the explicit manual-checkpoint profile. New host-native or fallback runs may enter through `governed-execution`; when they do, use its selected driver for lifecycle calls, sensitive-action decisions, budgets, receipts, and reconciliation while preserving every checkpoint in this skill.\n\n## Workflow File Resolution\n\nResolve which workflow file to execute:\n\n1. If the user specified a filename → use that file\n2. Else, glob for canonical workflows in `docs\u002Fplans\u002F*-workflow.md`:\n   - **One match** → use it automatically\n   - **Multiple matches** → if one is clearly the newest revision for the same semantic slug, prefer it; otherwise list them and ask the user to pick\n3. If no canonical matches, glob for legacy `hotl-workflow*.md` in project root:\n   - **One match** → use it automatically\n   - **Multiple matches** → list them and ask the user to pick\n4. **No matches** → stop and ask the user to create or name a workflow file\n\n## Branch\u002FWorktree Preflight\n\nAfter resolving the workflow file, run this preflight **before executing any steps**:\n\n```\n1. Is this a git repo with at least one commit?\n   - No  → log \"Skipping branch setup (no git history)\" → proceed to step execution\n   - Yes → continue\n\n2. Check for uncommitted changes\n   - First, exclude HOTL-owned transient artifacts from the dirty check:\n     • docs\u002Fplans\u002F*-workflow.md (canonical workflow files)\n     • hotl-workflow-*.md (legacy workflow files)\n     • docs\u002Fdesigns\u002F*.md (canonical design docs from brainstorming)\n     • docs\u002Fplans\u002F*-design.md, docs\u002Fplans\u002F*-plan.md (legacy design docs from brainstorming)\n     • .hotl\u002F (runtime state, reports, cache)\n   - If only HOTL artifacts are dirty → treat as clean, continue\n   - If non-HOTL dirty files exist:\n     • If dirty_worktree: allow in workflow frontmatter → proceed without prompting\n     • Otherwise → HARD-FAIL. Tell the user which non-HOTL files are dirty. Offer choices:\n       a. Clean up manually, then re-run\n       b. Stash manually, then re-run\n       c. Explicitly approve HOTL to stash and continue\n   - Clean → continue\n\n3. Determine branch name\n   - If branch: field exists in workflow frontmatter → use it\n   - Otherwise → derive `hotl\u002F\u003Cslug>` from the workflow filename\n     • Canonical: strip `YYYY-MM-DD-` prefix and `-workflow.md` suffix from `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cslug>-workflow.md`\n     • Legacy: strip `hotl-workflow-` prefix and `.md` suffix from `hotl-workflow-\u003Cslug>.md`\n\n4. Capture authoring origin\n   - Record the current branch name (if any) and current `HEAD` commit as the workflow's authoring origin\n   - If the current branch is neither `main` nor `master`, and the workflow frontmatter does not already set `branch:` or `worktree:`, PAUSE and ask:\n     a. Continue on the current branch in this checkout\n        → set `branch: \u003Ccurrent-branch>` and `worktree: false`\n     b. Use HOTL's isolated execution branch\u002Fworktree (recommended)\n        → leave `worktree: true` and let HOTL derive `hotl\u002F\u003Cslug>` unless the user wants a custom branch name\n     c. Use a custom execution branch\n        → set `branch: \u003Cuser-branch>` and keep worktree isolation unless the user explicitly opts out\n   - Explain clearly: the authoring checkout and the execution checkout can differ. HOTL can execute in a separate worktree while leaving the current checkout untouched\n\n5. Determine isolation mode\n   - If `worktree: host` in frontmatter → stay on the current checkout's current feature branch exactly as provided by the host tool; reject `main` and `master`\n   - If `worktree: false` in frontmatter → stay in the current checkout and use a dedicated branch there\n   - If the current checkout is already a named linked git worktree, and the workflow frontmatter does not set `branch:` or `worktree:`, use host mode automatically to avoid stacking another worktree\n   - Otherwise → use an isolated git worktree by default\n\n6. Check if the target branch\u002Fworktree already exists locally\n   - Current helper behavior: existing branch\u002Fworktree collisions are a hard stop, not an interactive reuse\u002Frecreate flow\n   - If the helper reports an existing branch\u002Fworktree conflict, stop and ask the user whether to reuse manually, delete+recreate manually, or abort\n   - Does not exist → create (no prompt)\n\n7. Resolve the execution root with `scripts\u002Fhotl-prepare-execution-root.sh \u003Cworkflow-file> --executor-mode \u003Cmode>`\n   - The helper returns JSON with: `branch`, `repo_root`, `execution_root`, `workflow_path`, `source_workflow_path`, `source_branch`, `source_head`, `worktree_path`\n   - By default it creates a linked git worktree for the branch, copies the current workflow into that worktree, and returns that worktree as `execution_root`\n   - If `worktree: false` in frontmatter → create\u002Fswitch to the dedicated branch in the current checkout and return the repo root as `execution_root`\n   - If `worktree: host` in frontmatter → keep the current branch and return the current checkout as `execution_root`; if `branch:` is set, it must match the current branch\n   - If `branch:` matches the currently checked-out branch while worktree isolation is still enabled, the helper must STOP with a clear message telling the user to set `worktree: false` or `worktree: host` for same-branch continuity\n8. Change into `execution_root`\n   - Every later git command, runtime call, Codex helper call, and review command for this run MUST execute from that directory\n```\n\n**Rules:**\n- No auto-stash. Hidden state mutation weakens governance.\n- Existing branch\u002Fworktree collisions do not currently auto-prompt; treat them as a stop-and-ask condition until interactive reuse\u002Frecreate is implemented.\n- Non-git repos skip entirely — HOTL works without git ceremony.\n- Run HOTL structural lint (`scripts\u002Fdocument-lint.sh`) automatically on the workflow file before any git mutation or step execution. If lint fails, STOP and show all errors. If lint passes, continue silently.\n\n## Typed Verification\n\nThe `verify` field supports 4 types. A scalar string is shorthand for `type: shell`. If `verify` is a list, ALL checks must pass.\n\n- **type: shell** — run command, check exit code, capture stdout\u002Fstderr\n- **type: browser** — use browser tooling with url+check; if unavailable, downgrade to type: human-review with check text as prompt\n- **type: human-review** — `hotl-rt step N verify` returns a `human review required: ...` block reason and pauses the run; show the prompt, wait for approval, then persist it with `hotl-rt gate N approved|rejected --mode human` (never auto-approve)\n- **type: artifact** — check path exists, evaluate assert (kind: exists | contains | matches-glob)\n  For `matches-glob`, `path` must be the directory and `value` must be a filename glob only; values like `src\u002F*` are invalid and should be authored as `path: src`\n\n## Execution State Persistence\n\nAll state persistence is handled by the `hotl-rt` shared runtime (`runtime\u002Fhotl-rt`). This executor calls `hotl-rt` for all state transitions and keeps the claimed controller token in `HOTL_OWNER_TOKEN`:\n\n- `hotl-rt init \u003Cworkflow-file> --require-owner --executor-mode executing-plans ...` — at run start\n- `hotl-rt owner claim ...` and renewable `hotl-rt owner heartbeat ...` — controller coordination\n- `hotl-rt step N start --run-id \u003Crun-id>` — before each step\n- `hotl-rt step N verify --run-id \u003Crun-id>` — after each step's action\n- `hotl-rt step N retry --run-id \u003Crun-id>` \u002F `hotl-rt step N block --reason \"...\" --run-id \u003Crun-id>` — on failure\n- `hotl-rt gate N approved|rejected --run-id \u003Crun-id>` — at gate steps\n- `hotl-rt action request|decide|begin|complete|reconcile ...` — sensitive authorization and effect evidence\n- `hotl-rt budget check --run-id \u003Crun-id>` — before another costly or long action when telemetry is relevant\n- `hotl-rt finalize --json --run-id \u003Crun-id>` — after all execution evidence is complete; successful runs become `ready_to_finish`\n- `hotl-rt finish \u003Cdisposition> --run-id \u003Crun-id>` — after the user selects the explicit disposition; successful runs then become `completed`\n\nThe runtime owns `.hotl\u002Fstate\u002F\u003Crun-id>.json` and `.hotl\u002Freports\u002F\u003Crun-id>.md`. Agents do not manage these files directly. Runtime calls happen before the corresponding chat or progress UI update.\n\nUse the same HOTL runtime and script path resolution order defined in `skills\u002Floop-execution\u002FSKILL.md`. Do not assume `runtime\u002F` or `scripts\u002F` exist in the user's project checkout.\n\nTo resume an interrupted executing-plans run, use the host tool's native resume entry point.\n- **Codex:** ask me to use `$hotl:resuming` on the workflow file\n- **Claude Code:** `\u002Fhotl:resume \u003Cworkflow-file>`\n\n### Long-running controller and effect rules\n\n- Immediately after init, run `hotl-rt owner claim --owner \u003Cstable-controller-id> --lease-seconds \u003Cbounded-lease> --run-id \u003Crun-id>`, parse its one-time token without displaying it, export it as `HOTL_OWNER_TOKEN`, and heartbeat before and after long actions and at batch boundaries. Every later mutation inherits the token.\n- If control must move, use explicit `owner handoff`, `owner release`, or reviewed `owner takeover`. Age alone is never takeover authority.\n- Host goals, automations, background sessions, handoffs, and hooks provide scheduling and liveness only. HOTL state, verification, ownership, and receipts remain authoritative.\n- For each sensitive effect, use `action request` with a stable idempotency key, human `action decide`, then `action begin` before the external operation and `action complete` with evidence afterward. If the outcome is interrupted or uncertain, inspect the target and use `action reconcile`; do not replay it blindly.\n\n## Process\n\n1. Resolve and read the workflow (see above)\n2. Run Branch\u002FWorktree Preflight (see above), capture its JSON result, and change into `execution_root`\n3. Run `hotl-rt init \u003Cworkflow-file> --require-owner --executor-mode executing-plans --repo-root \u003Crepo-root> --execution-root \u003Cexecution-root> --source-workflow-path \u003Csource-workflow-path> --source-branch \u003Csource-branch|null> --source-head \u003Csource-head|null> --worktree-path \u003Cworktree-path|null> --branch \u003Cbranch>` to initialize state and report\n4. Capture the run id, claim ownership, retain the raw token only as `HOTL_OWNER_TOKEN`, and pass `--run-id \u003Crun-id>` (or set `HOTL_RUN_ID=\u003Crun-id>`) on every later runtime\u002Fhelper call for this run\n5. Execute tasks in order, 3 at a time:\n   - `hotl-rt step N start --run-id \u003Crun-id>` before each step\n   - Execute the action\n   - `hotl-rt step N verify --run-id \u003Crun-id>` to run typed verification\n   - If verify reports `human review required: ...`, pause and do not continue until `hotl-rt gate N approved|rejected --mode human --run-id \u003Crun-id>` succeeds\n   - On failure: `hotl-rt step N retry --run-id \u003Crun-id>` or `hotl-rt step N block --reason \"...\" --run-id \u003Crun-id>`\n   - On gate: `hotl-rt gate N approved|rejected --run-id \u003Crun-id>`\n6. After each batch: run review checkpoint (see below), then show what was done, ask \"Continue to next batch?\"\n7. On failure: stop and report — never silently skip a failed step\n8. When execution evidence is complete: run final review checkpoint (see below), invoke `hotl:verification-before-completion`, then `hotl-rt finalize --json --run-id \u003Crun-id>`. Treat `ready_to_finish` as awaiting disposition, render the verified-step summary, and invoke `hotl:finishing-a-development-branch` with the same `run_id` and owner token.\n9. After explicit finish moves a successful run to `completed`, release ownership, require a sufficient receipt, and only then claim completion.\n\n## Review Checkpoints\n\nRecord `git rev-parse HEAD` as the review base before starting each batch.\n\n### After Each Batch\n\nAfter all steps in the batch have passed verification:\n1. Invoke `requesting-code-review` to dispatch the `code-reviewer` agent\n   - Review type: checkpoint\n   - Review base: the recorded pre-batch HEAD\n   - Steps reviewed: the batch step numbers\n2. When findings return, invoke `receiving-code-review`\n   - Follow Verify → Evaluate → Respond → Implement\n3. Resolve all BLOCK findings before proceeding to the next batch\n\n### Before Final Completion\n\nA final review is required unless the most recent review already covers all current changes and no code changed afterward.\n\n1. Invoke `requesting-code-review` with review type: final\n   - Review base: branch point or last review base, whichever is more recent\n2. When findings return, invoke `receiving-code-review`\n3. Resolve all BLOCK findings before finalizing\n4. If fixes after the last review changed scope, constraints, or risk_level, request a scoped follow-up review before completing\n\nReview happens after step verification, before `verification-before-completion`, before `hotl-rt finalize`.\n\nUse this over `loop-execution` when you want explicit human checkpoints at every stage rather than auto-approve.\n\n## Reporting\n\nExecution report output must conform to `docs\u002Fcontracts\u002Fexecution-report-output.md`. This is the canonical reporting contract from `skills\u002Floop-execution\u002FSKILL.md`. Live step visibility follows the same rules as `skills\u002Floop-execution\u002FSKILL.md` — per-step chat logs on all platforms, deterministic renderer for final summary.\n","# Executing Plans (Linear with Checkpoints)\n\nExecute the plan task by task. Pause after every 3 tasks for human review.\n\nThis remains the explicit manual-checkpoint profile. New host-native or fallback runs may enter through `governed-execution`; when they do, use its selected driver for lifecycle calls, sensitive-action decisions, budgets, receipts, and reconciliation while preserving every checkpoint in this skill.\n\n## Workflow File Resolution\n\nResolve which workflow file to execute:\n\n1. If the user specified a filename → use that file\n2. Else, glob for canonical workflows in `docs\u002Fplans\u002F*-workflow.md`:\n   - **One match** → use it automatically\n   - **Multiple matches** → if one is clearly the newest revision for the same semantic slug, prefer it; otherwise list them and ask the user to pick\n3. If no canonical matches, glob for legacy `hotl-workflow*.md` in project root:\n   - **One match** → use it automatically\n   - **Multiple matches** → list them and ask the user to pick\n4. **No matches** → stop and ask the user to create or name a workflow file\n\n## Branch\u002FWorktree Preflight\n\nAfter resolving the workflow file, run this preflight **before executing any steps**:\n\n```\n1. Is this a git repo with at least one commit?\n   - No  → log \"Skipping branch setup (no git history)\" → proceed to step execution\n   - Yes → continue\n\n2. Check for uncommitted changes\n   - First, exclude HOTL-owned transient artifacts from the dirty check:\n     • docs\u002Fplans\u002F*-workflow.md (canonical workflow files)\n     • hotl-workflow-*.md (legacy workflow files)\n     • docs\u002Fdesigns\u002F*.md (canonical design docs from brainstorming)\n     • docs\u002Fplans\u002F*-design.md, docs\u002Fplans\u002F*-plan.md (legacy design docs from brainstorming)\n     • .hotl\u002F (runtime state, reports, cache)\n   - If only HOTL artifacts are dirty → treat as clean, continue\n   - If non-HOTL dirty files exist:\n     • If dirty_worktree: allow in workflow frontmatter → proceed without prompting\n     • Otherwise → HARD-FAIL. Tell the user which non-HOTL files are dirty. Offer choices:\n       a. Clean up manually, then re-run\n       b. Stash manually, then re-run\n       c. Explicitly approve HOTL to stash and continue\n   - Clean → continue\n\n3. Determine branch name\n   - If branch: field exists in workflow frontmatter → use it\n   - Otherwise → derive `hotl\u002F\u003Cslug>` from the workflow filename\n     • Canonical: strip `YYYY-MM-DD-` prefix and `-workflow.md` suffix from `docs\u002Fplans\u002FYYYY-MM-DD-\u003Cslug>-workflow.md`\n     • Legacy: strip `hotl-workflow-` prefix and `.md` suffix from `hotl-workflow-\u003Cslug>.md`\n\n4. Capture authoring origin\n   - Record the current branch name (if any) and current `HEAD` commit as the workflow's authoring origin\n   - If the current branch is neither `main` nor `master`, and the workflow frontmatter does not already set `branch:` or `worktree:`, PAUSE and ask:\n     a. Continue on the current branch in this checkout\n        → set `branch: \u003Ccurrent-branch>` and `worktree: false`\n     b. Use HOTL's isolated execution branch\u002Fworktree (recommended)\n        → leave `worktree: true` and let HOTL derive `hotl\u002F\u003Cslug>` unless the user wants a custom branch name\n     c. Use a custom execution branch\n        → set `branch: \u003Cuser-branch>` and keep worktree isolation unless the user explicitly opts out\n   - Explain clearly: the authoring checkout and the execution checkout can differ. HOTL can execute in a separate worktree while leaving the current checkout untouched\n\n5. Determine isolation mode\n   - If `worktree: host` in frontmatter → stay on the current checkout's current feature branch exactly as provided by the host tool; reject `main` and `master`\n   - If `worktree: false` in frontmatter → stay in the current checkout and use a dedicated branch there\n   - If the current checkout is already a named linked git worktree, and the workflow frontmatter does not set `branch:` or `worktree:`, use host mode automatically to avoid stacking another worktree\n   - Otherwise → use an isolated git worktree by default\n\n6. Check if the target branch\u002Fworktree already exists locally\n   - Current helper behavior: existing branch\u002Fworktree collisions are a hard stop, not an interactive reuse\u002Frecreate flow\n   - If the helper reports an existing branch\u002Fworktree conflict, stop and ask the user whether to reuse manually, delete+recreate manually, or abort\n   - Does not exist → create (no prompt)\n\n7. Resolve the execution root with `scripts\u002Fhotl-prepare-execution-root.sh \u003Cworkflow-file> --executor-mode \u003Cmode>`\n   - The helper returns JSON with: `branch`, `repo_root`, `execution_root`, `workflow_path`, `source_workflow_path`, `source_branch`, `source_head`, `worktree_path`\n   - By default it creates a linked git worktree for the branch, copies the current workflow into that worktree, and returns that worktree as `execution_root`\n   - If `worktree: false` in frontmatter → create\u002Fswitch to the dedicated branch in the current checkout and return the repo root as `execution_root`\n   - If `worktree: host` in frontmatter → keep the current branch and return the current checkout as `execution_root`; if `branch:` is set, it must match the current branch\n   - If `branch:` matches the currently checked-out branch while worktree isolation is still enabled, the helper must STOP with a clear message telling the user to set `worktree: false` or `worktree: host` for same-branch continuity\n8. Change into `execution_root`\n   - Every later git command, runtime call, Codex helper call, and review command for this run MUST execute from that directory\n```\n\n**Rules:**\n- No auto-stash. Hidden state mutation weakens governance.\n- Existing branch\u002Fworktree collisions do not currently auto-prompt; treat them as a stop-and-ask condition until interactive reuse\u002Frecreate is implemented.\n- Non-git repos skip entirely — HOTL works without git ceremony.\n- Run HOTL structural lint (`scripts\u002Fdocument-lint.sh`) automatically on the workflow file before any git mutation or step execution. If lint fails, STOP and show all errors. If lint passes, continue silently.\n\n## Typed Verification\n\nThe `verify` field supports 4 types. A scalar string is shorthand for `type: shell`. If `verify` is a list, ALL checks must pass.\n\n- **type: shell** — run command, check exit code, capture stdout\u002Fstderr\n- **type: browser** — use browser tooling with url+check; if unavailable, downgrade to type: human-review with check text as prompt\n- **type: human-review** — `hotl-rt step N verify` returns a `human review required: ...` block reason and pauses the run; show the prompt, wait for approval, then persist it with `hotl-rt gate N approved|rejected --mode human` (never auto-approve)\n- **type: artifact** — check path exists, evaluate assert (kind: exists | contains | matches-glob)\n  For `matches-glob`, `path` must be the directory and `value` must be a filename glob only; values like `src\u002F*` are invalid and should be authored as `path: src`\n\n## Execution State Persistence\n\nAll state persistence is handled by the `hotl-rt` shared runtime (`runtime\u002Fhotl-rt`). This executor calls `hotl-rt` for all state transitions and keeps the claimed controller token in `HOTL_OWNER_TOKEN`:\n\n- `hotl-rt init \u003Cworkflow-file> --require-owner --executor-mode executing-plans ...` — at run start\n- `hotl-rt owner claim ...` and renewable `hotl-rt owner heartbeat ...` — controller coordination\n- `hotl-rt step N start --run-id \u003Crun-id>` — before each step\n- `hotl-rt step N verify --run-id \u003Crun-id>` — after each step's action\n- `hotl-rt step N retry --run-id \u003Crun-id>` \u002F `hotl-rt step N block --reason \"...\" --run-id \u003Crun-id>` — on failure\n- `hotl-rt gate N approved|rejected --run-id \u003Crun-id>` — at gate steps\n- `hotl-rt action request|decide|begin|complete|reconcile ...` — sensitive authorization and effect evidence\n- `hotl-rt budget check --run-id \u003Crun-id>` — before another costly or long action when telemetry is relevant\n- `hotl-rt finalize --json --run-id \u003Crun-id>` — after all execution evidence is complete; successful runs become `ready_to_finish`\n- `hotl-rt finish \u003Cdisposition> --run-id \u003Crun-id>` — after the user selects the explicit disposition; successful runs then become `completed`\n\nThe runtime owns `.hotl\u002Fstate\u002F\u003Crun-id>.json` and `.hotl\u002Freports\u002F\u003Crun-id>.md`. Agents do not manage these files directly. Runtime calls happen before the corresponding chat or progress UI update.\n\nUse the same HOTL runtime and script path resolution order defined in `skills\u002Floop-execution\u002FSKILL.md`. Do not assume `runtime\u002F` or `scripts\u002F` exist in the user's project checkout.\n\nTo resume an interrupted executing-plans run, use the host tool's native resume entry point.\n- **Codex:** ask me to use `$hotl:resuming` on the workflow file\n- **Claude Code:** `\u002Fhotl:resume \u003Cworkflow-file>`\n\n### Long-running controller and effect rules\n\n- Immediately after init, run `hotl-rt owner claim --owner \u003Cstable-controller-id> --lease-seconds \u003Cbounded-lease> --run-id \u003Crun-id>`, parse its one-time token without displaying it, export it as `HOTL_OWNER_TOKEN`, and heartbeat before and after long actions and at batch boundaries. Every later mutation inherits the token.\n- If control must move, use explicit `owner handoff`, `owner release`, or reviewed `owner takeover`. Age alone is never takeover authority.\n- Host goals, automations, background sessions, handoffs, and hooks provide scheduling and liveness only. HOTL state, verification, ownership, and receipts remain authoritative.\n- For each sensitive effect, use `action request` with a stable idempotency key, human `action decide`, then `action begin` before the external operation and `action complete` with evidence afterward. If the outcome is interrupted or uncertain, inspect the target and use `action reconcile`; do not replay it blindly.\n\n## Process\n\n1. Resolve and read the workflow (see above)\n2. Run Branch\u002FWorktree Preflight (see above), capture its JSON result, and change into `execution_root`\n3. Run `hotl-rt init \u003Cworkflow-file> --require-owner --executor-mode executing-plans --repo-root \u003Crepo-root> --execution-root \u003Cexecution-root> --source-workflow-path \u003Csource-workflow-path> --source-branch \u003Csource-branch|null> --source-head \u003Csource-head|null> --worktree-path \u003Cworktree-path|null> --branch \u003Cbranch>` to initialize state and report\n4. Capture the run id, claim ownership, retain the raw token only as `HOTL_OWNER_TOKEN`, and pass `--run-id \u003Crun-id>` (or set `HOTL_RUN_ID=\u003Crun-id>`) on every later runtime\u002Fhelper call for this run\n5. Execute tasks in order, 3 at a time:\n   - `hotl-rt step N start --run-id \u003Crun-id>` before each step\n   - Execute the action\n   - `hotl-rt step N verify --run-id \u003Crun-id>` to run typed verification\n   - If verify reports `human review required: ...`, pause and do not continue until `hotl-rt gate N approved|rejected --mode human --run-id \u003Crun-id>` succeeds\n   - On failure: `hotl-rt step N retry --run-id \u003Crun-id>` or `hotl-rt step N block --reason \"...\" --run-id \u003Crun-id>`\n   - On gate: `hotl-rt gate N approved|rejected --run-id \u003Crun-id>`\n6. After each batch: run review checkpoint (see below), then show what was done, ask \"Continue to next batch?\"\n7. On failure: stop and report — never silently skip a failed step\n8. When execution evidence is complete: run final review checkpoint (see below), invoke `hotl:verification-before-completion`, then `hotl-rt finalize --json --run-id \u003Crun-id>`. Treat `ready_to_finish` as awaiting disposition, render the verified-step summary, and invoke `hotl:finishing-a-development-branch` with the same `run_id` and owner token.\n9. After explicit finish moves a successful run to `completed`, release ownership, require a sufficient receipt, and only then claim completion.\n\n## Review Checkpoints\n\nRecord `git rev-parse HEAD` as the review base before starting each batch.\n\n### After Each Batch\n\nAfter all steps in the batch have passed verification:\n1. Invoke `requesting-code-review` to dispatch the `code-reviewer` agent\n   - Review type: checkpoint\n   - Review base: the recorded pre-batch HEAD\n   - Steps reviewed: the batch step numbers\n2. When findings return, invoke `receiving-code-review`\n   - Follow Verify → Evaluate → Respond → Implement\n3. Resolve all BLOCK findings before proceeding to the next batch\n\n### Before Final Completion\n\nA final review is required unless the most recent review already covers all current changes and no code changed afterward.\n\n1. Invoke `requesting-code-review` with review type: final\n   - Review base: branch point or last review base, whichever is more recent\n2. When findings return, invoke `receiving-code-review`\n3. Resolve all BLOCK findings before finalizing\n4. If fixes after the last review changed scope, constraints, or risk_level, request a scoped follow-up review before completing\n\nReview happens after step verification, before `verification-before-completion`, before `hotl-rt finalize`.\n\nUse this over `loop-execution` when you want explicit human checkpoints at every stage rather than auto-approve.\n\n## Reporting\n\nExecution report output must conform to `docs\u002Fcontracts\u002Fexecution-report-output.md`. This is the canonical reporting contract from `skills\u002Floop-execution\u002FSKILL.md`. Live step visibility follows the same rules as `skills\u002Floop-execution\u002FSKILL.md` — per-step chat logs on all platforms, deterministic renderer for final summary.\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fexecuting-plans",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans",{"tool":52,"command":53},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans",{"tool":55,"command":56},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill executing-plans","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fyimwoo\u002Fhotl-plugin\u002Fskills\u002Fexecuting-plans\u002FSKILL.md",true,[],[61,71,79,87,95,103],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":70},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":70},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":70},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":70},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":70},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":65,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":70},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]