メニュー
Produces token-efficient `.lmd.md` implementation plans (task-on-demand render, code anchors, @define/@call macros) without functional loss. Use when you have a spec or requirements for a multi-step task, before touching code.
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.
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.
| name | lmd-writing-plans |
| description | Produces token-efficient `.lmd.md` implementation plans (task-on-demand render, code anchors, @define/@call macros) without functional loss. Use when you have a spec or requirements for a multi-step task, before touching code. |
Body renders one phase at a time — never read it from disk.
Rendering, diagnosis and fallback: see the lmd-rendering-skills skill.
The skill produces plans as .lmd.md documents: a meta-head (Goal / Architecture /
Global Constraints + @var + @import .lean-ctx/lean-md/plan-recipes /), one
@phase "task-N" per task, anchors for existing code, verbatim for new code, and
@call macros for boilerplate. The executing controller renders one task at a
time: lean-md render <plan.lmd.md> --phase task-N.
pre-context → file-structure → task-sizing → plan-format → write-plan → self-review → handoff.
The self-review phase composes an @dispatch to the plan-reviewer companion. The
terminal state offers the execution handoff (lmd-subagent-driven-development or
lmd-executing-plans).
plan-reviewer — independent plan-completeness review; dispatchable as a brief