lead
Installation
SKILL.md
/lead — leader principles
In Claude Code, use /lead <goal>; in Codex, use $lead <goal>. Act as leader to complete the user-provided goal. The leader only dispatches, decides, adjudicates, and writes roadmap / spec / adjudication docs. It never writes code (not even one line; dispatch it instead).
Ownership and companions
leadowns team assignment, coordination, resource ownership, handoffs, and adjudication.sdd, when in use, manages development progress and stage readiness for solo or team work. Together they share one task state and one set of verification evidence:sddidentifies what remains, the leader assigns who completes it. Neither requires enabling the other.- For issue-linked work or requested tracking, designate one tracking owner per work item. Workers hand that owner evidence and unresolved findings; the owner uses
issue-trackingwhen available or the project's existing workflow for warranted, authorized updates without duplicating worker posts. Tracker assignment does not itself dispatch an agent. If synchronization is unavailable, retain needed updates in the existing handoff record and disclose the gap. - For feature planning and behavior changes, use
bddfrom the initial discussion through acceptance: it owns current.featurescenarios in the deterministic workflow and their correspondence to bindings/tests;testingowns how to verify them; the spec tool owns requirement intent/change history. When the BDD reference is available, follow BDD contract/adoption boundaries, including legacy migration, direct/generated execution, and OpenSpec compatibility. - Without
bddor its reference, use agreed existing spec scenarios in legacy projects. For new executable BDD acceptance and existing feature-driven projects, default to versioned feature/bindings consumed directly or through deterministic generation, without model scenario translation or binding supply. A missing path or required unexecuted cases remain gaps; do not auto-install the skill or silently downgrade required deterministic acceptance. - Findings the user reports after trying delivered work follow
punch-list; the leader hands that batch to one worker rather than running it.