autospec-sweep

Validate autospec configuration and emit bounded remediation gaps.

3|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/berlinguyinca/autospec --skill autospec-sweep
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autospec-sweep
Source: https://github.com/berlinguyinca/autospec/tree/main/skills/autospec-sweep
Command: npx skills add https://github.com/berlinguyinca/autospec --skill autospec-sweep

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, git, gh, jq, yq, ajv, rg, bats, and includes scripts (resource) components.

What problem does it solve?

autospec-sweep reduces the drift between what your product team wrote down (specs), what your users read (docs), what your quality system expects (tests), and what the repository actually does (code), so improvements remain auditable and reviewable over time.

Core Features & Use Cases

  • Tracks and reconciles reality vs. specs: Detects spec-vs-reality mismatches and ensures updates happen in the right order (spec first when needed).
  • Emits bounded, actionable gaps: Produces structured “gap” JSON describing missing/incorrect behaviors, documentation targets, and weak test coverage.
  • Runs continuous improvement gates: Executes the configured test commands every sweep run and can trigger remediation through issue-filing and downstream implementation flows.
  • Keeps documentation audiences/scopes aligned: Treats documentation.audiences[] and documentation.scopes[] as the source of truth and creates separate documentation gaps so different readers get the correct content.

Quick Start

Run the sweep by executing: /autospec-sweep init, then /autospec-sweep configure, then /autospec-sweep run.

Frequently Asked Questions about autospec-sweep

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect documentation drift between product specs and code?

To track spec mismatches, run the sweep workflow which validates configuration against schema, executes test commands, and outputs bounded gap JSON detailing missing behaviors and weak test coverage for review.

How do I automate gap remediation when test coverage diverges from specifications?

Automate gap remediation by running the sweep workflow which routes emitted structured gaps into GitHub issues or downstream implementation flows, ensuring spec updates happen before code changes.

Do I need GitHub CLI and jq installed to run spec validation workflows?

Yes, running spec validation workflows requires curl, git, gh, jq, yq, ajv, rg, and bats installed to validate schemas, execute tests, and route remediation gaps into GitHub issues.

Can I use continuous improvement gates to validate E2E test expectations?

Yes, continuous improvement gates execute configured test commands during every sweep run, including deploy prerequisites required for E2E testing, to validate test expectations against actual code behavior.

What is the best way to align documentation audiences with repository behavior?

Align documentation audiences by treating audiences and scopes as the source of truth, creating separate documentation gaps during the sweep so different readers receive correct content.