crank-plan

Installation
SKILL.md

Plan

Goal

Turn the spec into something a coding agent can execute task-by-task with no further design conversation. Bite-sized tasks. TDD rhythm. Frequent commits. No placeholders.

Hard Rules

  • If $ARGUMENTS is a path, read the spec from there; otherwise use the spec already in the conversation.
  • Write the plan to a fresh OS temp file: $(mktemp -t crank-plan).md. Do not write into the working directory unless the user explicitly asks. Tell the user the path once.
  • Every subagent this skill spawns runs at the standard tier (see References → Subagents) unless otherwise specified.
  • No placeholders. No TODO, TBD, implement later, "add appropriate error handling", "similar to Task N", or references to symbols no task defines. Show code in every code step.
  • Tasks must be readable out of order. Repeat structure across tasks rather than back-referencing.

Guidelines

Test-first or lightest-check

Installs
4
First Seen
Jun 23, 2026