writing-lane-briefs
Installation
SKILL.md
Writing lane briefs
Overview
A brief is a plan written for a stranger who will not ask questions. It merges three sources:
the coordinator lane contract (worktree, sentinel, fixture contract, .feature gate), the
plan disciplines of superpowers:writing-plans (bite-sized red→green steps, interfaces,
no placeholders) and improve plans (drift stamp, current-state excerpts, machine-checkable
done criteria, STOP conditions). If a decision is not in the brief, the lane does not make it.
Two parts, always: What changes for the team (plain English, becomes the PR body's first
section) then the technical brief. Never head the plain part "In plain English". The lane hands
back the PR body too, written with pr — the coordinator corrects it, never
writes it from scratch.