opsx-approve

Review OpenSpec change designs and update approval status in .openspec.yaml.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill opsx-approve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-approve
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/.claude/skills/opsx-approve
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill opsx-approve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the decision step for spec-driven changes by helping you review the proposal, design, tasks, and spec artifacts in one pass before approving or rejecting implementation.

Core Features & Use Cases

  • Change Review: Summarizes the proposal, specification requirements, design approach, and task list for a clear approval decision.
  • Approval or Rejection: Updates the approval status in the project metadata with a timestamp and optional reviewer comment.
  • Use Case: Use it when a change is ready for implementation and you need a concise, consistent sign-off process with traceable feedback.

Quick Start

Ask this Skill to review the named OpenSpec change and approve it, or reject it with a comment if the design needs revision.

Frequently Asked Questions about opsx-approve

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

FAQPage Schema
How do I review and approve OpenSpec change designs?

Reviewing OpenSpec change designs involves reading proposal, spec, design, and task artifacts, then writing the approval status with timestamps and comments into the .openspec.yaml file.

What is the OpenSpec change approval process?

OpenSpec change approval summarizes proposal requirements, design approaches, and task lists to provide a consistent sign-off decision with traceable feedback for active changes.

How do I record a rejection for an OpenSpec change?

Recording an OpenSpec change rejection requires updating the approval status in .openspec.yaml with a timestamp and an optional reviewer comment explaining the required revisions.

When do I need to use OpenSpec design review for spec changes?

OpenSpec design review is needed when a spec change is ready for implementation and requires a concise sign-off process to ensure traceable feedback before development proceeds.

Can I add reviewer comments to the .openspec.yaml approval status?

Yes, optional reviewer comments can be added to the .openspec.yaml approval status alongside timestamps to provide traceable feedback when approving or rejecting implementation.