osx-review-artifacts

Review OpenSpec artifact changes for consistency and completeness before implementation.

6|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-review-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: osx-review-artifacts
Source: https://github.com/amauryconstant/openspec-extended/tree/main/resources/opencode/skills/osx-review-artifacts
Command: npx skills add https://github.com/amauryconstant/openspec-extended --skill osx-review-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a rigorous pre-implementation review of OpenSpec artifacts to catch structural and content gaps before applying changes, reducing the risk of incomplete specifications and misaligned changes.

Core Features & Use Cases

  • Cross-artifact validation: checks proposal.md, specs/, design.md, and tasks.md for consistency and completeness.
  • Quality enforcement: ensures required sections exist (Why, What Changes, Capabilities, Impact) and that scenarios, tasks, and formats meet OpenSpec guidelines.
  • Actionable reporting: prioritizes issues by severity (Critical, Warning, Suggestion) and outputs a structured review report with file/line references for fixes.

Quick Start

Review the change 'add-auth' proposal and all related artifacts to identify critical issues before apply.

Frequently Asked Questions about osx-review-artifacts

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

FAQPage Schema
How do I review OpenSpec artifacts for consistency before implementation?

Pre-implementation review of OpenSpec artifacts checks proposal.md, specs/, design.md, and tasks.md for cross-artifact consistency and completeness. It ensures required sections exist, scenarios are testable, and task formats meet guidelines.

What is cross-artifact validation for OpenSpec proposal changes?

Cross-artifact validation checks proposal.md, specs/, design.md, and tasks.md for consistency and completeness. It ensures required sections exist (Why, What Changes, Capabilities, Impact) and that scenarios, tasks, and formats meet OpenSpec guidelines.

How do I check if OpenSpec specs contain testable scenarios and proper formats?

Quality enforcement checks that OpenSpec artifacts conform to ADDED/MODIFIED/Removed formats, contain testable scenarios, and provide actionable task guidance. It flags critical issues by severity for remediation.

Can I get a structured report of issues found in OpenSpec design and tasks files?

Actionable reporting prioritizes issues by severity (Critical, Warning, Suggestion) and outputs a structured review report with file/line references for fixes. It helps remediate faulty specifications before implementation.

What sections are required in an OpenSpec proposal.md for it to pass review?

Required sections include Why, What Changes, Capabilities, and Impact. The review ensures these sections exist in proposal.md and that scenarios, tasks, and formats meet OpenSpec guidelines.

Why does my OpenSpec change deployment fail due to incomplete specifications?

Incomplete specifications with missing required sections, untestable scenarios, or inconsistent task formats cause deployment issues. Pre-implementation review catches structural and content gaps across artifacts before applying changes.