agentsclimarketplace

Cairn planning

Skill eventually-consistent-code/cairn2/skills/cairn-planning

Use when a repo has cairn.json and the cairn MCP tools (plan_*, issue_*) are available — the cairn 2.0 planning lifecycle. Owns the depth dial (quick/standard/deep), the model-routing rubric for agent fan-out, artifact conventions under .cairn/plans/, and the precedence rule (git plan docs win over tracker issue text).From its SKILL.md

Install
npx -y skills add eventually-consistent-code/cairn2 --skill cairn-planning

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

One thing to look at

  • 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

4.6 KB, as published. Nobody here has run it

cairn planning (lifecycle policy)

The server owns mechanism (scaffolding, frontmatter, mirroring, drift math). This skill owns judgment: how deep to plan, which models to fan out, what goes in which artifact, and what "verified" means.

Activation gate

Apply when cairn.json exists in the repo AND the plan_* MCP tools are available. The tracker named in cairn.json is the single source of truth for work items; git owns plans and memory.

Artifacts — what goes where

FileOwnsWritten by
PROJECT.mdvision, requirements/cairn:new interview
roadmap.mdphase table + status/cairn:new, updated at verify/ship
phases/NN/CONTEXT.mdlocked decisionsplanning discussion
phases/NN/RESEARCH.mddeep-mode research briefresearch fan-out
SURVEY.mdproject-wide research brief (survey markers)/cairn:survey fan-out
phases/NN/PLAN.mdtask breakdown + issues: frontmatter/cairn:plan
phases/NN/VERIFICATION.mdgoal-backward check results; its EXISTENCE marks the phase verified/cairn:verify

Frontmatter is the constrained flat form only (key: value, key: [a, b]). Update issues: through plan_issues_set, not hand-editing, so validation runs.

Depth dial

Resolution order: command flag > PLAN.md depth: frontmatter > cairn.json default > standard.

quickstandarddeep
researchnone1 research subagentparallel fan-out, multi-angle
plandraft tasks directlyPLAN.md + CONTEXT.md+ plan-checker agent pass
verifytests pass+ tracker cross-check (plan_drift)+ adversarial verification, VERIFICATION.md rigor

MVP shaping (plan --mvp)

First tasks form ONE thin vertical slice exercising every layer end-to-end (walking skeleton); depth and breadth come only after the slice stands. A slice that can't demo is not a slice.

TDD eligibility (plan --tdd)

Eligible: behavior-testable code — logic, APIs, parsers, state machines. Not eligible: config, docs, scaffolding, pure styling, generated code. Eligibility is per task, decided at plan time, stored in PLAN.md tdd: frontmatter via plan_meta_set; work-time enforcement is the RED/GREEN commit pair in the ledger, checked at verify.

Model routing (research fan-out)

cairn.json → agents.model: auto | inherit | haiku | sonnet | opus. inherit = session model everywhere; explicit value pins everything; auto routes per work class:

work classsignalsrouted model
mechanicalenumerate/locate/scrapesmall/fast (haiku-tier)
synthesisresearch briefs, pattern analysissession model (sonnet-tier)
judgment gatesplan-checker, adversarial verify, architecture trade-offsstrongest available (opus-tier)

Blast radius rules: output that gates a lifecycle transition (verify/ship) routes UP, never down. Downgrade only mechanical work. Uncertain → inherit.

The rubric governs ALL research fan-out — scout, survey, and plan --deep — not only deep mode. Research verbs dispatch one subagent per pending topic, in parallel, classifying each TOPIC by work class to pick its model; the main thread writes results and flips markers as each agent completes.

Lifecycle

new → plan N → work N → verify N → ship. Each command's file defines its steps; this skill's conventions bind them all:

  • Claim before work: issue_update(id, state: "in_progress") + context_set before touching code for an issue.
  • Close only on verified done: tests passing, behavior confirmed. Never close to make a gate pass.
  • Precedence: on conflict between a phase's CONTEXT.md/PLAN.md and tracker issue text, the GIT DOC WINS — update the issue (issue_update) with a dated note; never silently follow the stale issue.
  • Drift is a stop signal: plan_drift flags mean reconcile before proceeding (missing → recreate; closed-unverified → verify the phase or reopen the issue).
  • Assignee courtesy: never claim an issue assigned to someone else without saying so.

Failure honesty

Report gates truthfully: a failed verify is a failed verify. Never write VERIFICATION.md for a phase that didn't pass — its existence is a machine-read signal (drift treats closed issues in verified phases as normal).

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.