agentsclimarketplace

Plan

Skill jschilli/argot/skills/plan

Commit to a sequenced, verifiable course of work — decompose into tasks with acceptance criteria, order them, surface risks. Use when the user wants a plan, task breakdown, migration sequence, or premortem before building. Read-only; execution is gated on human approval.From its SKILL.md

Install
npx -y skills add jschilli/argot --skill plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.5 KB, as published. Nobody here has run it

plan — argot verb 3/7

Signature: Design (or direct intent) → Plan (.argot/plan-*.md + .json, schema: artifacts/plan.schema.json). Human-gated: execution does not begin until the gate is approved.

Envelope: read-only.

Procedure

  1. Take the decided Design (or confirm intent directly for work that needs no design phase). If the design decision hasn't been made, go back — planning an undecided design launders the decision away from the human.
  2. Decompose into tasks an implementer with no session context can execute: exact paths, no placeholders, one concern each.
  3. Attach acceptance criteria to every task — checkable done-predicates, not vibes.
  4. Order and premortem: dependencies explicit; riskiest-first where possible; list the ways this plan fails and the mitigation for each.
  5. Present for the gate. Then stop. No "should I continue?" later — approval here buys autonomous execution of the whole plan.

Contract

  • A plan task that can't state its acceptance criteria isn't ready to be a task.
  • Skipping a task during execution requires an explicit skip_reason in the artifact.
  • Changes to an approved plan re-open the gate.

Keep looking

Skills are one crate of 608,475. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.