Feature Request: Add /opsx:repair command to support spec-consistent repair after /opsx:apply

[clay-good]

Note

Moved from issue #821, originally opened by @jiangjiang01 on 2026-03-10. Continuing the conversation here in Discussions — the original issue thread (including any comments) stays available at #821 for the record.

---

Background

In a typical OpenSpec workflow, development usually follows this sequence:

/opsx:propose
→ generate proposal/spec/design/tasks

/opsx:apply
→ generate implementation code from tasks

local testing

/opsx:archive
→ archive the change into the system spec

However, during real-world development, bugs or inconsistencies are often discovered during local testing after /opsx:apply.

Current Problem

When an issue is found during testing, developers currently need to manually instruct the AI agent to:

1. Fix the implementation code
2. Update spec.md if the specification is incomplete or incorrect
3. Update design.md if the architecture changes
4. Update tasks.md to reflect the updated implementation steps

This creates several problems:

• repetitive manual instructions
• risk of spec and code becoming inconsistent
• additional cognitive overhead for developers
• slower iteration loops during debugging

Proposed Solution

Introduce a new command:

/opsx:repair

Issue discovered during testing:

Expected Behavior

The command should guide the AI agent to perform a spec-consistency repair cycle:

1. Analyze the root cause of the issue

2. Determine whether the problem is caused by:

   • incorrect implementation
   • incomplete or incorrect specification

3. If the implementation is incorrect:

   • update the code implementation
   • keep the spec unchanged

4. If the specification is incomplete or incorrect:

   • update spec.md
   • update design.md if needed
   • update tasks.md
   • update the implementation accordingly

5. Ensure the implementation satisfies the specification

6. Keep the change ready for /opsx:archive

Example Workflow

Current workflow

/opsx:propose
/opsx:apply
test
(manually instruct AI to fix code and update spec/design/tasks)
/opsx:archive

Proposed workflow

/opsx:propose
/opsx:apply
test
/opsx:repair
/opsx:archive

Benefits

• Reduces repetitive instructions to AI agents
• Keeps spec, tasks, and code consistent
• Improves developer experience during iterative debugging
• Makes OpenSpec workflows smoother in real-world development

Context

This would be particularly useful when OpenSpec is used with AI coding tools such as:

• Cursor
• Claude Code
• Codex CLI
• GitHub Copilot

where iterative testing and debugging after code generation is very common.

Summary

Adding /opsx:repair would formalize the Spec Consistency Repair Loop in OpenSpec workflows and significantly improve the developer experience when iterating on generated implementations.

Happy to help test or refine the command behavior if needed.

This command could internally reuse the existing change context and simply trigger a repair loop across spec/design/tasks/implementation.