Loom Plan Writer

THE REQUIRED SKILL FOR CREATING LOOM EXECUTION PLANS. Invoke it whenever an agent needs to author a plan for loom orchestration.

A loom plan is a DAG of stages that loom runs in isolated git worktrees. It maximizes throughput with two levels of parallelism — subagents within a stage (FIRST priority) and concurrent worktree stages (SECOND) — and it is only as good as its CLAIMS about the code are TRUE and its verification actually PROVES them.

This skill assumes CLAUDE.md is in context (it always is under loom). Where CLAUDE.md already governs something — subagent preambles (Rule 5), hierarchies (Rule 6c), memory routing (Rule 12/18), branch discipline — this skill points at it rather than restating it.

Two rules dominate everything below:

1. Ground every claim before you write it (Section 1) — the #1 cause of bad plans.
2. The plan file is your deliverable. After writing it, STOP (Section 11) — never implement.

1. Ground Every Claim (READ THE SEAM)

⚠️ A plan is a set of CLAIMS about code: "this function does X," "this enum's consumers are Y," "this field is safe to add," "this command type-checks." Every claim is WRONG until the code confirms it. The design spine is usually sound — defects hide in UNREAD seams. A file the plan NAMES is a promise to read; a described file is an unread file.