cursor-implement
Skill3 starsChanged 6 days agoMITView on GitHub
Dispatch an implementation task to Cursor's CLI (cursor-agent) in an isolated worktree, with the model pinned to whichever family the round's cross-family accounting needs. Use when the user asks Cursor to implement something, or to keep another family's quota free for review.
In this repository15 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- agy-adversarial-reviewSkill
- agy-implementSkill
- claude-adversarial-reviewSkill
- claude-implementSkill
- codex-adversarial-reviewSkill
- codex-implementSkill
- configSkill
- cursor-adversarial-reviewSkill
- dev-leadSkill
- grok-adversarial-reviewSkill
- grok-implementSkill
- opencode-adversarial-reviewSkill
- opencode-implementSkill
- quota-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
Every write leg gets its own worktree, without exception — same rule, same helpers, same reasons as the other families (the CLI's own …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Implement via cursor-agent
A paid-pool write leg whose family is whatever model you pin — a
cursor-served Codex tier produces GPT-family work, a cursor-served Sonnet
produces Claude-family work. The cross-family rule reads the served model's
family: the reviewer for this leg's output must come from a different family
than the one you pinned here, and auto/composer-* output (family
unknown/undisclosed) must be reviewed by TWO named families to be safe —
cheaper to just pin a named model when the work will need a gate.
Before the first run of a session
Read references/cursor-runtime.md.
What bites the write role: bare -p already has full write and shell access
(measured — no --force needed, and none of --force/--yolo/
--approve-mcps may appear anyway), the prompt rides argv with an
unverified size cliff, and quota exhaustion is loud (ActionRequiredError,
exit 1) so a dead dispatch tells you immediately.
Worktree, snapshot, then dispatch
Every write leg gets its own worktree, without exception — same rule, same
helpers, same reasons as the other families (the CLI's own --worktree
under ~/.cursor/worktrees is not used; the suite's helpers own directory
lifecycle):
RUN_DIR=$(mktemp -d "${TMPDIR:-/tmp}/cursor-implement.XXXXXX") # FIRST — the snapshot lands here
BASE=$(git rev-parse HEAD) # from a clean checkout, recorded before anything
WORKTREE=../<repo>-cursor-<short-task-slug>
git worktree add -b cursor/<short-task-slug> "$WORKTREE" "$BASE"
# The helper lives in the SUITE's tree, cwd is the TARGET repo — a bare
# `scripts/…` resolves against the target and exits 127.
DEV_LEAD=${DEV_LEAD_ROOT:-$(ls -d "$HOME"/.claude/plugins/cache/dev-lead/dev-lead/* 2>/dev/null | sort -V | tail -1)}
[ -x "$DEV_LEAD/scripts/snapshot-refs.sh" ] || { echo "dev-lead root unresolved — set DEV_LEAD_ROOT to your checkout"; exit 1; }
"$DEV_LEAD/scripts/snapshot-refs.sh" save "$WORKTREE" "$RUN_DIR/remote-refs.before" # push-detection baselineThe snapshot is the no-push evidence on this adapter: the shell tool is fully available in the write posture, so the rule is instruction level — state it in the task prompt, then let the fail-closed ref check at handoff prove what happened either way.
Launch
# Write the task prompt to "$RUN_DIR/task.md" in its own FOREGROUND step.
cd "$WORKTREE" && \
cursor-agent -p --trust \
--model '<family-pinned-model>' \
--output-format json \
"$(cat "$RUN_DIR/task.md")" > "$RUN_DIR/impl.json" 2> "$RUN_DIR/impl.err"- Bare
-pIS the write posture (measured: creates files, runs shell, no prompting) — that is exactly why this launch happens only inside a dedicated worktree, and why the review leg never uses it. --modelpinned and recorded — the run log must name adapter, model flag, and therequest_idreturned in$RUN_DIR/impl.json; the reviewer-family decision downstream depends on it.- JSON audit output — preserve the whole
impl.json: itsresultis the delegate's report and itssession_id/request_idbind that report to the dispatch. On failure, inspectimpl.err; never fabricate an id from mixed stdout/stderr. - Task prompt must state: local commits only, never push, list what was not finished rather than improvising around it.
Handoff
"$DEV_LEAD/scripts/snapshot-refs.sh" check "$WORKTREE" "$RUN_DIR/remote-refs.before" || exit 1
git -C "$WORKTREE" status --porcelain=v1
git -C "$WORKTREE" diff "$BASE" --statThe helper exits nonzero on a remote-ref delta, and || exit 1 makes that
failure terminal for this handoff. Do not replace it with a second snapshot
and a raw diff, which can be noticed but accidentally continued past.
Measured once (2026-09-22, grok-4.7-high, a 1600-line task that said "commit
locally, NO AI-authorship trailers"): it committed its work, and the commit
carried Co-authored-by: Cursor <cursoragent@cursor.com> anyway. Read
every delegate commit message before it goes anywhere, and rewrite it while it
is still local. The lead's own verification pass (build, tests, real code
path) is the merge gate regardless, followed by a reviewer from a
different model family than the one pinned above.
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.

