developer-workflow plugins

by ArcticFox2029

Makes a repository know itself and preserve the engineering context built while you work with it, so an agent stops rediscovering both. An architecture index and an impact map instead of scanning files; work state, session records and the decisions behind them instead of losing context between sessions; the procedures, tools and workflows you keep re-deriving. Everything is repository-local markdown, committed beside the code. For long-lived repos you revisit, not one-off scripts.

by kouko

Optional using-loom-workflow discovery routing and Loom workflow tools around the loom stations — persistent Outcome Maps, git memory, loom-memory (recall / record / reconcile / retire durable repository lessons), critique (proposal | complexity), recap, handoff, session distill, chat visualizations (tables / ASCII / Mermaid, reasoning pages), cross-executor second opinion, plus the standalone goal-create and dbt-model-style skills.