unslop

Merge file specs into a unit spec (spec granularity consolidation)

Run the adversarial quality pipeline on a managed file. Extracts behaviour, generates black-box tests, and validates via mutation.

Record a change request for a managed file

Check cross-spec coherence across related specs, including blocked-by constraint tracking

Grow test coverage on a managed file or unit using mutation-driven discovery

Extract cross-cutting patterns from the spec corpus into project-local domain skills

Infer a spec from existing code -- Archaeologist reads code and produces a candidate spec

Structured spec elicitation -- Socratic dialogue for creating or amending specs

Partition a unit spec into file specs (spec granularity splitting)

Regenerate all stale managed files from their specs

Render a Mermaid dependency graph of specs, concrete specs, and managed files

Review a spec for completeness and suggest tightening. Use --promote to promote a concrete spec to permanent.

Initialize unslop in the current project

Promote a concrete spec (.impl.md) from ephemeral to permanent

Create or edit a spec for a source file or directory

List managed files and their staleness status

Regenerate managed files from their specs

Bring existing code under spec-driven management

Run Saboteur verification synchronously on a managed file or unit

Detect intent drift between specs and code. Surfaces meaningful discrepancies and offers per-finding remediation.

Adversarial Quality framework — three-agent pipeline (Archaeologist → Mason → Saboteur) for mutation-gated test generation

Use when generating, reviewing, or promoting concrete specs — the implementation strategy layer between abstract specs (intent) and generated code. Activates during Stage B.1 of generation, during /unslop:harden --promote, and during takeover raising.

Use when generating or regenerating code from unslop spec files. Activates during /unslop:generate, /unslop:sync, and the generation step of /unslop:takeover.

Use when writing, drafting, reviewing, or editing unslop spec files (*.spec.md). Activates for spec creation, takeover spec drafting, and spec editing guidance.

Use when running the unslop takeover pipeline to bring existing code under spec management. Covers discovery, spec drafting, archiving, generation, and the convergence validation loop.

Use when the user wants to change, fix, refactor, add, or review code in a project managed by unslop (has a .unslop/ directory). Activates for any intent that would modify source files, ask about code quality, or plan structural changes. Routes the user to the correct unslop command based on their intent.

3 hooks across 3 events