SkillAgentSearch skills...

plan-writing

Write or fix a Cheap Agent plan file before calling the cheapag delegate tool

Install / Use

npx skills add muaaz9329/cheap-ag --skill plan-writing

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Tags

Our assessment of plan-writing

plan-writing scores 82/100 on our quality scale, 952nd of 1,148 Content & Media skills we index.

Its SKILL.md is 4.7 KB long, well organised into 11 sections with 2 code examples: a solid amount of guidance for an agent.

It has 341 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
18/20
Description
12/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 6 days ago, so plan-writing is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

plan-writing compared with similar skills

All 4 of these similar skills score higher than plan-writing; compare them before choosing.

SkillScoreStarsUpdatedFormat
plan-writing (this skill)by muaaz9329823416d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
algorithmic-artby anthropics100177.9k2mo agoSKILL.md
pptxby anthropics100177.9k2mo agoSKILL.md
prospectingby coreyhaines3110060.1k11d agoSKILL.md

Frequently asked questions

How do I install plan-writing?
Run npx skills add muaaz9329/cheap-ag --skill plan-writing. The install tabs above show the steps for each supported agent.
Which AI agents does plan-writing work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is plan-writing safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is plan-writing still maintained?
The repository was last updated 6 days ago, so plan-writing is actively maintained.

name: plan-writing description: Write or fix a Cheap Agent plan file before calling the cheapag delegate tool. Use when planning a change of more than ~20 lines or several files for the cheap worker, splitting work into steps, or after delegate rejects a plan.

Writing a Cheap Agent plan

The cheap worker sees the whole plan, then implements the steps you name in delegate. It works in an isolated copy of the repo and does only what a step says, so each step must stand on its own: exact files, what to build, and a check that proves it works.

Save plans under .plan/ in the repository, e.g. .plan/rate-limit.md (the developer may read, edit or commit them). Pass the path relative to the repository root.

Grammar

# <plan title>                              ← required, exactly one H1
<shared context, optional, ≤ ~15 lines>
## <id> <short title>                       ← id = integer or integer+letter (3, 3a; s3, step-3 also work)
files: <path>, <dir/>, ...                  ← required; scope + overlap key
do: <what to build; continuation lines indented 2+ spaces>
done-when: <condition>; <condition>         ← required; `backticked` = executed
dont: <constraint>; <constraint>
needs: <step id>, ...
difficulty: easy | medium | hard            ← picks the worker model; wins over delegate's
kind: fix | change                          ← fix: a bug to reproduce; change: no reproduction expected
model: <model>
deps: <package@range>                       ← the step needs a new package
  • Keys are lowercase, at the start of the line, never bullets (- files: is wrong). Continuation lines are indented 2+ spaces.
  • In done-when, every backticked fragment is run as a shell command in the worker's copy and must exit 0. Put only commands in backticks; plain text is the worker's responsibility.
  • Unknown keys (e.g. api:, example:) are passed to the worker as hints.

Rules

  • Size: one step ≈ under an hour of junior-developer work. Split anything bigger.
  • One change per step: a do: that lists three or more numbered items is refused at delegate; split it into 3a, 3b, … and order them with needs:.
  • Details as bullets: write a do: as - bullets or prose; numbered or lettered items count as separate changes, and three or more get the task refused. do: 1. extract X 2. move Y 3. update the import is refused; - extract X, - move Y, - update the import is accepted.
  • Checks: give every step an executable done-when (a test command, a type check), not only prose. Name the one test file or test id the step concerns, never the whole suite.
  • Kind: say kind: fix for a bug to reproduce or kind: change when no reproduction is expected; otherwise the worker infers it from the step's wording.
  • Source: put the user's request or the issue verbatim in the shared context, or pass it as delegate(source=…) (text or a file path): the worker checks your steps against it and reports where they disagree.
  • Scope: files: lists every file or directory the step may touch, accurately. It also decides which steps can run in parallel.
  • Constraints: add dont: for the mistakes you expect (new dependencies, touching auth, changing public APIs).
  • Grouping: make independent steps separate comma groups so they run in parallel; use needs: when one step must land first.
  • Packages: declare a new package with deps:; the worker cannot install packages itself.
  • Share context once at the top (conventions, existing helpers to reuse) instead of repeating it per step.

Example

# Rate limiting for auth endpoints
Redis is already wired in src/lib/redis.ts. Keep middleware style consistent with src/middleware/*.

## 1 limiter lib
files: src/lib/rateLimit.ts, test/rateLimit.test.ts
do: sliding-window limiter `limit(key, max, windowSec) -> {allowed, retryAfter}` using redis ZSET.
done-when: `npm test -- rateLimit` passes; tests cover allow, block, window expiry
dont: add dependencies

## 2 wire into login
files: src/api/login.ts, src/middleware/, test/login.test.ts
do: 5 req/min per IP on POST /api/login; on block return 429 + Retry-After.
done-when: `npm test -- login` passes; new test: 6th request → 429
dont: touch auth/session logic
needs: 1

## 3 docs
files: docs/api.md
do: document the 429 response and Retry-After.
done-when: section "Rate limits" exists under /api/login

Delegating it

  • steps="3": one step, one job. steps="3-5": a range, run in order in one job. steps="1-2,3": comma-separated groups, run in parallel unless their files: overlap or needs: orders them.
  • delegate(plan=".plan/rate-limit.md", steps="1-2,3")
  • delegate(plan=".plan/rate-limit.md", steps="2", note="use the existing ipFrom(req) helper"): a note is at most 300 characters, for one-off guidance.

Related Skills

View on GitHub
GitHub Stars341
CategoryContent
Updated6d ago
Forks31

Languages

TypeScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions