openspec-reflect

Generate gate-ready reports identifying drift and philosophy misalignment in OpenSpec change proposals.

19|5|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/digital-stoic-org/agent-skills --skill openspec-reflect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-reflect
Source: https://github.com/digital-stoic-org/agent-skills/tree/main/dstoic/skills/openspec-reflect
Command: npx skills add https://github.com/digital-stoic-org/agent-skills --skill openspec-reflect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-gate drift detection and philosophy alignment to ensure gate readiness before human reviews.

Core Features & Use Cases

  • Pre-gate self-check to verify acceptance criteria and detect scope drift
  • Philosophy alignment verification against OpenSpec Execution Philosophy
  • Gate-ready reporting with evidence and deviation flags

Quick Start

Run reflect with a change-id to generate a gate-ready report.

Frequently Asked Questions about openspec-reflect

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

FAQPage Schema
How do I detect scope drift before a project gate review?

To detect scope drift before a project gate review, you run pre-gate checks against change proposals to identify acceptance criteria deviations and scope changes. This generates a gate-ready report flagging deviations before human validation.

What is OpenSpec philosophy alignment verification?

OpenSpec philosophy alignment verification is a pre-gate check that evaluates execution philosophy within change proposals to ensure compliance. It identifies philosophy violations and generates a gate-ready report with recommended actions.

How do I generate a gate-ready report for OpenSpec change proposals?

To generate a gate-ready report for OpenSpec change proposals, you run a reflect check using the change-id. The output highlights criteria status, scope deviations, philosophy violations, and recommended actions for gate readiness.

Does OpenSpec pre-gate drift detection replace human validation?

OpenSpec pre-gate drift detection does not replace human validation. It serves as a self-check to verify acceptance criteria and flag scope or philosophy misalignment, ensuring gate readiness before the actual human review occurs.

When should I run pre-gate compliance checks on a change proposal?

You should run pre-gate compliance checks on a change proposal after drafting acceptance criteria and scope changes but before human validation. This ensures execution philosophy alignment and gate readiness prior to the official review.

What does a gate-ready report include for scope deviations?

A gate-ready report for scope deviations includes criteria status, evidence of scope changes, philosophy violations, and recommended actions. It provides a comprehensive overview to ensure gate readiness before human validation.