kvasanova/loomwork
SDD lifecycle for superpowers: status-frontmatter convention, drift audit, pre-merge close-out, and a close-out hook gate. One loom, one status surface.
Run the SDD drift linter — flags stale spec status, missing plan DONE banners, and missing/stale verified dates. Use monthly, before large SDD meta-work, or when spec/plan status looks wrong.
Use during finishing-a-development-branch (after tests pass, before integration) when the work was tracked by a plan or spec in the SDD docs dirs. Commit and push close-out to the feature branch — same PR, no post-merge follow-up.
Initialize the current consumer repository for loomwork, or upgrade one set up by an older loomwork version. Scaffolds the SDD spec and plan directories, removes the legacy marker-guarded doctrine block from AGENTS.md or CLAUDE.md and the old Cursor hook setup, and migrates an old STRATEGY.md into a short product context section. Use when setting up loomwork in a repository or re-running it after a loomwork upgrade.
Manual-only; use only when explicitly requested. Right before executing a plan in docs/superpowers/plans/, pick the model alias per task for subagent-driven-development's implementer and reviewer dispatches, so execution doesn't inherit the session default. The approved assignment lives in the session; writing it into the plan is optional and asked at the end. Invoke explicitly with a plan path, e.g. /loomwork:model-assignment docs/superpowers/plans/2026-09-20-feature.md.
Manual-only; use only when explicitly requested. Split a single-file agent guidance document into a tool-agnostic AGENTS.md plus thin host-specific files (CLAUDE.md, .github/copilot-instructions.md, and similar) that import it. Invoke explicitly when a repository has one oversized CLAUDE.md or AGENTS.md that mixes shared contributor knowledge with host-specific mechanics.