agentleFS
Sign inStart free
yokeloopyokeloop/yoke/skills/draft/SKILL.md

draft

Skill1 starsChanged 4 months agoMITView on GitHub

Projects the agreed plan onto the code as Markup — TODO markers plus a compilable skeleton — and opens a Draft PR for review, instead of implementing. Triggered when the user writes "draft", "mark the code", "mark up the plan", "make a draft", "draft pr".

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use onboard, status and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • AnthropicSkill

    status

    Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 2

    Distinctive

    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
  1. Distinctive:

    All of the above → fresh marking.

    line 29
  2. Distinctive:

    Never pauses: No cold-start gate, no confirmation, no mid-run question — the Draft PR is the pause.

    line 55
  3. Very specific:

    Ends at the Draft PR: Never flips it to ready, never merges — /do executes the Draft.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mark the code per plan

The optional marking step between grill and do (ADR-0011). A do-shaped run — the same inputs and the same finish machinery as /do — that marks instead of implementing: it projects the plan onto the code as Markup and opens a GitHub Draft PR for remote review. /draft NEVER pauses — the Draft PR is the pause. The flow becomes grill → draft → PR review → do; grill → do stays the default.

Input

$ARGUMENTS — one of:

  • empty — no input; work from the current conversation
  • a plain task description — chat text, no ticket
  • a single issue URL, a bare <slug>, or a *-task.md path

All of the above → fresh marking. Plus the iteration shapes:

  • a Draft PR URL, or a bare <slug> whose .yoke/ai/<slug>/<slug>-draft.md exists → iteration against the existing Draft

Router

Detect the run from $ARGUMENTS. First match wins:

  1. Input is a Draft PR URL, or a <slug> with an existing .yoke/ai/<slug>/<slug>-draft.md → iteration. Read and follow reference/mode-draft.md § Iteration.
  2. Anything else → fresh marking. Read and follow reference/mode-draft.md from Phase 0.

The full procedure lives in reference/mode-draft.md. Read it, then execute.

Principles

These hold for every run:

  • Never pauses. No cold-start gate, no confirmation, no mid-run question — the Draft PR is the pause.
  • Marks, never implements. The Markup contract is reference/markup-format.md: TODO(yoke): Markers plus a compilable skeleton. The build stays green; tests may be red.
  • Ends at the Draft PR. Never flips it to ready, never merges — /do executes the Draft; /merge finishes after approval.
  • Worktree on default branch + finish machinery per ${CLAUDE_PLUGIN_ROOT}/skills/do/reference/finish.md.
  • Artifacts under .yoke/. <slug>-plan.md and <slug>-draft.md live in .yoke/ai/<slug>/.
  • Commits by convention per ${CLAUDE_PLUGIN_ROOT}/skills/gca/reference/commit-convention.md.
  • Read the git memory first per ${CLAUDE_PLUGIN_ROOT}/skills/gca/reference/history-reading.md — a Marker must not re-propose what a Rejected: trailer already dismissed, and Markup respects active Constraint: entries.
  • Language: match the ticket/input language, or follow the project-level definition in CLAUDE.md / AGENTS.md.

After the run

The user reviews the Draft PR on GitHub and comments on it. A re-run of /draft re-marks per the comments; /do <draft-PR-URL> (or /do <slug>) implements the Markers and flips the PR to ready.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free