lodestar-plan

You are running lodestar-plan. Write a plan. Do not implement it unless the user asked you to in the same turn.

Plans are how. Link audit findings or specs for what. Home is the resolved plans root (default docs/plans/). Completed work goes to that root's done/ via lodestar-implement; abandoned work to abandoned/. Do not write new plans into done/ or abandoned/.

Routing. An audit action item is one concern, one bounded change, one acceptance unit. A lodestar plan is for multiple stages, cross-package redesign, or unresolved product/architecture decisions. Escalate an oversized audit item here instead of growing its contract.

Scripts live beside this SKILL.md. Reach the shared plans module only through scripts/setup-modules.mjs:

node <this-skill>/scripts/setup-modules.mjs resolve --root <repo>
node <this-skill>/scripts/setup-modules.mjs ensure-root --root <repo>
node <this-skill>/scripts/setup-modules.mjs list --root <repo>

Load references one hop from this file. Do not copy their procedures back here.

How to talk to the user

Anything you print or ask is read by a person who is skimming.

• Ask one clear question at a time. Say what happens for each answer.
• Name a file by its path, not by an internal key.
• Never trim or postpone a warning. A missing file or command the plan names stays in.
• Point first. Bullets, not paragraphs. Blank line between blocks.
• Bold the first few words of each bullet.

Milestones

Concise chat progress — not diagnostic logs or run files:

• Opening — plans root, rigor intent, checks, mutation/commit policy (plan does not edit app source)
• Before long work — locate / ground / write
• At boundaries — grounded paths and next step
• Closing — plan path, skipped coverage, actionable failures

Steps

Work in order. Load the named reference before each step.

1. Locate — references/locate.md. Resolve the

plans root. Do not create it yet.

1. Discover — references/discover-context.md.

Only when .agents/lodestar/context.md is missing: find the same facts in the repo. Never a stop, and never a hand-off to lodestar-setup.

1. Ground — references/ground.md. Bounded

verification, not research. Stop rather than write a plan that names a missing file or a command that is not real. A failed ground leaves no scaffold.

1. Shape and tier — references/shape-and-tier.md.

Pick file vs folder. Write rigor: from size, then risk.

1. Write — references/write.md. Create the

plans root only now, then the plan. Do not commit unless asked.

Never

• Application source (packages/**, src/**, or the equivalent in

Package Layout).

• .agents/lodestar/context.md.
• Guessing a missing file or command into existence. Stop and ask.
• Writing a folder plan with rigor: light.
• Creating the plans root, done/, or any bookkeeping before grounding

succeeds.