workflowlisted

The SWE loop binding every implementation session in this repo - fire whenever code is about to be written, changed, or resumed, at every chunk start and end, and whenever unsure what the next step is. Covers orient -> plan -> implement -> verify -> document -> commit (NEVER push) -> reflect. Nested lazy parts; load references/scale.md when work outgrows one context window (massive task/refactor, flood of tasks, mass research); load references/rot-check.md before a release, after a long repo gap, or on "rot check"/"is anything stale". Not for scaffolding new stacks (bootstrap) or skill hygiene (skill-manager).
Stepkar2004/init-configurator · ★ 1 · AI & Automation · score 74

Install: claude install-skill Stepkar2004/init-configurator

# workflow — the loop every implementation session runs > One skill fires for all SWE work; the less-common parts load lazily from `references/` > when their trigger row matches. Do not rely on separate sibling skills auto-triggering > for scale or rot-check — this file is their front door. ## The loop 0. **Orient.** Read `docs/state/now.md`, then the active plan (`docs/plans/` when the repo keeps phase plans, else the current chunk in `docs/state/roadmap.md`). Know the chunk's goal and acceptance criteria before touching code. If no chunk is defined, defining one IS the first task. 1. **Plan the chunk.** Smallest end-to-end slice; name the files to touch and the tests that will prove it. If scope grows mid-chunk beyond the plan, stop — re-plan or split; never "just keep going". 2. **Implement.** Follow the constitution (CLAUDE.md) and the architecture rules in the active plan — they are constraints, not suggestions. 3. **Verify — the forgettable steps, in order:** - New behavior ⇒ new test; changed behavior ⇒ changed test. Same chunk, no IOUs. - Run the repo's gates: `project.yaml` declares them as tasks; the constitution (CLAUDE.md) and the pre-commit / CI configs are the full set. - User-visible behavior ⇒ actually run it — a green unit test is not a seen behavior. 4. **Document in the same chunk.** Update whatever the change made stale: README, the plan doc, an ADR for any new decision (`docs/decisions/`), docstrings. The test: "wo