spec-fix

Automatically fix specification and implementation discrepancies from spec-check findings.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/nok0321/claude-pipeline --skill spec-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-fix
Source: https://github.com/nok0321/claude-pipeline/tree/main/skills/spec-fix
Command: npx skills add https://github.com/nok0321/claude-pipeline --skill spec-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

spec-fix automatically repairs discrepancies between specifications and implementations by analyzing findings from /spec-check. It uses heuristics such as robustness, test presence, and git blame to decide fix directions and can iterate until no diffs remain, supporting synchronization after design changes and correction of constraint violations. For large features, it may delegate to impl-orchestrator and escalate Diverged decisions to Tier 1.

Core Features & Use Cases

  • Bidirectional auto-fix of Missing, Diverged, Extra, and Constraint between spec and code.
  • Iterative repair with the --loop option until convergence.
  • Flexible control with --spec-wins and --impl-wins, and clear escalation paths.

Quick Start

Run /spec-check to identify findings and then run /spec-fix to automatically repair them until convergence.

Frequently Asked Questions about spec-fix

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

FAQPage Schema
How do I automatically fix discrepancies between specifications and code?

To fix specification and code discrepancies automatically, run spec-fix after spec-check to repair Missing, Diverged, Extra, and Constraint findings using heuristics like test presence and git blame to determine the correct fix direction.

Can I iterate spec implementation repairs until there are no diffs left?

Yes, you can iterate spec implementation repairs until convergence by using the --loop option. This repeatedly applies fixes until no discrepancies remain between the specification and the implementation.

How does bidirectional spec implementation auto-fix decide whether to update the spec or the code?

Bidirectional spec implementation auto-fix decides update directions using heuristics such as robustness, test presence, and git blame, while also offering --spec-wins and --impl-wins modes for manual directional control.

What happens when ambiguous diverged findings occur during specification and implementation synchronization?

When ambiguous Diverged findings occur during specification and implementation synchronization, the auto-fix process escalates decisions to Tier 1 and may delegate large feature repairs to impl-orchestrator for resolution.

Do I need to run spec-check before fixing spec and implementation mismatches?

Yes, you need to run spec-check first to identify findings. Spec-fix consumes the Missing, Diverged, Extra, and Constraint findings generated by spec-check to automatically repair mismatches between specs and code.