菜单
Executes a .lmd.md plan in this session — the main agent runs each task itself, pauses at batch checkpoints for human review, and closes at a whole-branch final gate. No companions. Use when executing an implementation plan inline with human review checkpoints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation. Use when starting creative work that will produce a versioned design spec.
Use when you need to render an lmd-* skill phase or companion, or when a render call fails and you must decide whether the gateway is broken or the call was misaddressed.
Use when implementing any feature or bugfix, before writing implementation code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Fans out one focused subagent per independent problem domain (disjoint files, no shared state), then conflict-scans and integrates. Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Guides branch completion by verifying tests, detecting the workspace environment, presenting exactly 4 (or 3 for detached HEAD) integration options, then executing the choice with provenance-based worktree cleanup. Use when implementation is complete and you must decide how to integrate the work — merge, PR, keep, or discard.
| name | lmd-executing-plans |
| description | Executes a .lmd.md plan in this session — the main agent runs each task itself, pauses at batch checkpoints for human review, and closes at a whole-branch final gate. No companions. Use when executing an implementation plan inline with human review checkpoints. |
Body renders one phase at a time — never read it from disk.
Rendering, diagnosis and fallback: see the lmd-rendering-skills skill.
The skill executes a .lmd.md plan inline: the main agent runs each task itself, pauses at
executor-chosen batch boundaries for human review, and closes at a whole-branch final gate.
Every brief, diff and progress marker moves through lean-ctx (ctx_session/ctx_knowledge
/ctx_agent) — never through external SDD bash scripts or scratch-ledger files.
orient → preflight → execute → checkpoint → final-gate → finish.
The orient phase inlines the ambient tool-discipline baseline via @include hard-rules
(the subagent-only register/handoff contract does not apply to inline execution).
None — this is the inline-execution variant. For per-task subagent dispatch with a two-verdict reviewer, use lmd-subagent-driven-development instead.
