build-by-story
Ephemera paths: resolve FEATURE_CODE / <CODE> then follow templates/skills-ephemera-paths.md (feature root .skills/<CODE>/). Resolve pack seeds in this order, first path that exists: (1) templates/ beside this SKILL.md, (2) ${CLAUDE_PLUGIN_ROOT}/templates when that variable is set, (3) ../../../templates relative to this SKILL.md.
Build By Story
Drive an approved story-unit plan to completion: derive review units from requirement stories, run the shared continuous scheduler inside each unit, stop for a human after each unit, resume from the unit ledger, and finish with whole-branch review.
Continuous multi-task orchestration without unit barriers is build-in-waves.
Controller-implements-without-subagents is build-inline. Invoking this skill
selects story-unit execution. If the header already says continuous, hand
off to build-in-waves. If the user wants no subagents, name build-inline.
Context rule: workers and reviewers resume only within a valid semantic lane
lease. Hard rotation triggers start a fresh context from the feature capsule and
task delta; bulk artifacts travel as paths under .skills/, never pasted
session history.