expedite

Check OpenSpec change readiness and emit READY or BLOCKED exit codes.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-assistant --skill expedite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expedite
Source: https://github.com/jankneumann/agentic-assistant/tree/main/.agents/skills/expedite
Command: npx skills add https://github.com/jankneumann/agentic-assistant --skill expedite

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill prevents unsafe merge and cleanup actions by verifying that a change has passed required readiness checks and that no conflicting work is in progress.

Core Features & Use Cases

  • Read-only readiness gate: Produces a binary verdict (READY or BLOCKED) without mutating the worktree, registry, or remote state.
  • Active-agent exclusivity check: Refuses to proceed when other agents are still holding active worktrees.
  • Validation and rework verification: Validates the presence and outcomes of validation-report.md and interprets rework-report.json actions (block-cleanup, iterate, revise spec, or defer).
  • Machine-readable output option: Supports JSON output for automated workflows and CI-style parsing.

Quick Start

Run the readiness gate for a given OpenSpec change by executing: python skills/expedite/scripts/expedite.py <change-id> --json

Frequently Asked Questions about expedite

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

FAQPage Schema
How do I gate merge operations with readiness checks for OpenSpec changes?

Gate sync operations by probing for validation-report.md and rework-report.json, then emitting a READY or BLOCKED exit code. This readiness gate verifies active-agent exclusivity and validation outcomes without mutating the worktree, ensuring unsafe merges are blocked.

What does a rework report summary action mean for pre-cleanup workflow stages?

A rework report summary action determines whether pre-cleanup stages are blocked based on outcomes like block-cleanup, iterate, revise spec, or defer. The readiness gate interprets these actions consistently to prevent premature cleanup of active OpenSpec changes.

Can I get machine-readable JSON output from a validation report hard gate check?

Yes, you can get machine-readable JSON output by running the readiness gate script with the --json flag. This provides structured parsing of active-agent exclusivity, validation-report hard gates, and rework-report outcomes for automated CI-style workflows.

Does agent concurrency affect merge gating for pre-merge workflow stages?

Yes, agent concurrency affects merge gating because the readiness check enforces active-agent exclusivity. It refuses to proceed with sync-point operations when other agents are still holding active worktrees, preventing conflicting work from merging.

What's the best way to automate sync-point readiness verification without mutating remote state?

Automate sync-point readiness verification using a read-only gate that probes standard candidate paths for report files. It produces a binary READY or BLOCKED verdict and optional structured JSON without mutating the worktree, registry, or remote state.