← ClaudeAtlas

create-flywheellisted

Scaffold the session-flywheel dev process for a project — tracked requirement tables, STATUS.md, per-workstream NEXT_SESSION pointers, HANDBOOK, and the session protocol written into AGENTS.md. Works on fresh /create-blueprint output (greenfield mode) or an existing codebase (adopt mode, with an optional two-direction spec audit). Multi-developer safe.
savantly-net/claude-plugins · ★ 1 · AI & Automation · score 77
Install: claude install-skill savantly-net/claude-plugins
# Session Flywheel You are scaffolding a documentation-driven dev process whose core loop is: **every session cold-starts from a `NEXT_SESSION.md` pointer, and every session's last act is rewriting it** — so context compounds across sessions instead of evaporating. The system was extracted from the viddry project (2026-07, Jeremy) after its lessons were learned the hard way; you are installing the *end state*, including the fixes. ## The architecture — one fact, one home | File | Holds | Changes when | |---|---|---| | `requirements/functional.md`, `non-functional.md` | The spec, **with a per-row Status column** — the authoritative per-requirement view | A story lands or a requirement-level decision is made (same commit) | | `STATUS.md` | Phases, gates, spikes, infrastructure, open decisions, story one-liners | Work lands | | `<workstream>/NEXT_SESSION.md` | **Session state only**: goal, human's decision queue, live workspace/infra state, baseline | Rewritten at every session end | | Root `NEXT_SESSION.md` | **Index of active workstreams** — one line each: owner, goal, state | A workstream's state changes | | `docs/HANDBOOK.md` | **Standing knowledge**: framework traps, test rules, how to run things, conventions | Something is learned — and an entry is replaced or merged to make room, because the file is capped | | `docs/limits.json` | **A byte cap for each tracked document**, enforced by a test | A session compacts a file and lowers its cap | | Epic files (`plan/epics/`) |