light-plan-and-work
Skill787 starsChanged 4 months agoMITView on GitHub
Create a 3–7 step plan for a bounded task, execute immediately, verify, and hand it back. Use when the user explicitly requests a lightweight plan-and-work flow; do not use for open-ended brainstorming, discovery, high-risk migrations, multi-system architecture, or releases.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- codex-cli-model-bridgeSkill
- codex-doctorSkill
- codex-external-handoffSkill
- codex-handoffSkill
- codex-image-genSkill
- codex-model-routing-teamSkill
- codex-skill-adminSkill
- codex-theme-studioSkill
- enterprise-clone-builderSkill
- gpt56-sol-pro-consultSkill
- html-expressSkill
- leadbookSkill
- scholar-stickersSkill
- skill-open-sourcerSkill
- web-clipperSkill
- wechat-article-searchSkill
- wechat-stylerSkill
- workbuddy-cli-model-bridgeSkill
- wxmp-article-harvesterSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read the request, relevant project instructions, current files, and repository state.
- Distinctive: line 19
Heavy workflow: use the project's full specification or plan/work system when consequence, ambiguity, or coordination cost is high.
- Distinctive: line 27
Use the host plan tracker for 3–7 observable steps, with at most one step in progress.
- Distinctive: line 28
Start after the plan is visible.
- Distinctive: line 29
If a heavy condition appears, preserve completed safe work, pause the affected mutation, explain the evidence, and switch to the heavier …
- Distinctive: line 30
Verify in proportion to risk.
- Distinctive: line 34
Never revert, stash, edit, or stage unrelated work to make a broad verification command pass.
- Distinctive: line 36
Do not create a durable plan file by default.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Light Plan and Work
Planning and doing are one continuous workflow.
Route before planning
Read the request, relevant project instructions, current files, and repository state. Choose one route:
- Direct execution: one or two obvious actions. State a one-line brief and do them; do not manufacture a plan.
- Light plan and work: the outcome is concrete, the scope is bounded, and 3–7 steps can complete and verify it.
- Specialist Skill: a narrower installed Skill owns the artifact or domain. Use it, with this Skill only as the execution wrapper when useful.
- Discovery or brainstorming: the user is still choosing the problem, audience, concept, story, or direction. Use a discovery Skill before planning.
- Heavy workflow: use the project's full specification or plan/work system when consequence, ambiguity, or coordination cost is high.
Heavy conditions include destructive or sensitive operations, migrations, public API changes, cross-system architecture, releases, multiple owners, unresolved acceptance criteria, and explicit requests for a full specification or Compound Engineering. Read routing and verification when the route is unclear.
Execute
- Lock a compact execution brief: Goal, Deliverable, Boundary, and Acceptance.
- Resolve reversible choices yourself. Ask one blocking question only when the answer changes the outcome or requires new authority.
- Use the host plan tracker for 3–7 observable steps, with at most one step in progress. Each step must produce or verify something.
- Start after the plan is visible. Read before editing, preserve unrelated work, follow project instructions, and keep the plan aligned with evidence.
- If a heavy condition appears, preserve completed safe work, pause the affected mutation, explain the evidence, and switch to the heavier workflow.
- Verify in proportion to risk. Distinguish checks that directly cover the task from repository-wide or environment-wide gates.
- When a broad gate fails, classify the failure before acting. If read-only evidence shows it comes from pre-existing, unrelated work, preserve that work, run the strongest safe task-scoped checks, and record the blocked gate without claiming the repository is fully green. If the failure overlaps task files, causality is uncertain, or the gate is required for a release, treat it as a task blocker and fix, pause, or escalate.
- Hand back the result, artifacts, evidence, blocked gates, and residual risk.
Never revert, stash, edit, or stage unrelated work to make a broad verification command pass. Read routing and verification for the evidence and handoff contract.
Do not create a durable plan file by default. Create one only for an explicit request, future resumption, external handoff, multiple owners, or a lasting design decision, and follow the project's existing plan location.
Maintain trigger boundaries with evals/trigger_cases.json and output behavior with the baseline comparisons in evals/output/cases.jsonl.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

