---
title: "loomwork"
description: "SDD lifecycle glue for superpowers + compound-engineering: status-frontmatter convention, drift audit, pre-merge close-out, and strategy/close-out hook gates. One loom, one status surface."
canonical: https://agentpluginsdirectory.com/plugins/loomwork
last-updated: 2026-09-18
---

# loomwork
SDD lifecycle glue for superpowers + compound-engineering: status-frontmatter convention, drift audit, pre-merge close-out, and strategy/close-out hook gates. One loom, one status surface.
- Slug: loomwork
- Publisher: Pavlo Kvas
- Repository: https://github.com/kvasanova/loomwork
- Manifest: plugin.json
- Version: 0.4.1
- Category (editorial): other
- Skills: 4 (audit, close-out, init, split-agents-md)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-07-15
- Repository last pushed: 2026-09-17
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/loomwork
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What loomwork does, in the publisher's words

One loom, one status surface. SDD lifecycle glue for running superpowers and compound-engineering in one repo without the conflict: a status-frontmatter convention, a drift audit, a pre-merge close-out procedure, and hook gates that enforce both.

superpowers is an execution engine with no roadmap anchor, no solved-problem knowledge base, and no document-review pass. compound-engineering has those, but a looser execution pipeline. Installed together they collide: two brainstorm→plan pipelines, two status surfaces that drift apart. loomwork is the integration doctrine as a plugin:

- One status-tracking surface. Spec frontmatter + acceptance checkboxes are the only "what's built" tracker. No second tool buys a sync engine: only a second source of truth that drifts.
- Cherry-pick, don't merge. From compound-engineering take exactly: ce-strategy → STRATEGY.md (roadmap anchor), ce-compound → docs/solutions/ (knowledge base), ce-doc-review (adversarial design review). Don't run ce-brainstorm → ce-plan → ce-work: superpowers is the execution engine.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/kvasanova/loomwork/HEAD/README.md

## Skills

- audit: 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.
- close-out: 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.
- init: Initialize the current consumer repository for loomwork by scaffolding SDD directories, Cursor hook mirrors, and the marker-guarded AGENTS.md or CLAUDE.md guidance block. Use when setting up loomwork in a repository or refreshing copied Cursor hooks after a plugin update.
- split-agents-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 AGENT…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.