Run any Skill in Manus with one click

spec-review

Stars5

Forks1

UpdatedMay 13, 2026 at 00:02

Run the independent acceptance gate from Codex. Use when a change needs final verification against its spec, design, tasks, and execution evidence.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Catsofsuffering

Catsofsuffering/ccsm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	spec-review
description	Run the independent acceptance gate from Codex. Use when a change needs final verification against its spec, design, tasks, and execution evidence.
license	MIT

Review the change from Codex before archive.

Core contract

Codex performs the final acceptance gate.
Review compares the implementation against proposal, design, tasks, and verification evidence.
Archive only happens after Codex accepts the result.

Acceptance topology

The acceptance topology is distinct from execution routing. The topology roles are:

Decision owner (Codex): makes the final acceptance and archive decision. This is never delegated.
Optional acceptance reviewer (e.g., opencode): provides analysis that informs the decision, but the orchestrator makes the call. opencode is always additive, never the primary path.
Execution worker: implements bounded work and returns evidence. Workers never decide acceptance, never run spec-review, and never archive.

Archive is an explicit high-trust action owned by the decision owner. The execution path (orchestrator to execution worker) and the acceptance path (decision owner, optional reviewer) are separate concerns.

Steps

Select the active change with openspec status --change "<change-name>" --json.
Read proposal.md, design.md, tasks.md, and specs/**/*.md.
Inspect the current diff and the latest execution return packet.
Verify:
- tasks are complete
- constraints are satisfied
- required tests/checks were run
- no out-of-scope edits slipped in
If needed, run additional local checks.
Decide:
- Acceptance Passed and archive-ready
- Acceptance Failed with a bounded rework packet

Output

acceptance decision
supporting findings
rework packet or archive approval

Guardrails

Do not archive without verification evidence.
Do not delegate the final decision away from Codex.
Keep the result tied to the change contract, not personal preference.

More from this repository

same repository

spec-impl

Catsofsuffering/ccsm

Dispatch execution from Codex and keep acceptance in Codex. Use when the change is planned and ready for implementation.

2026-05-135

spec-fast

Catsofsuffering/ccsm

Orchestrate the full spec-driven workflow (spec-init to spec-review) automatically with bounded rework loops. Use when Codex should drive the complete change lifecycle without manual phase handoffs.

2026-05-065

spec-init

Catsofsuffering/ccsm

Start or resume the primary OpenSpec change flow from Codex. Use when Codex should pick the active change and create the next OpenSpec artifact directly.

2026-04-225

spec-plan

Catsofsuffering/ccsm

Prepare the execution handoff contract from Codex. Use when a change needs design, task refinement, and a bounded execution packet.

2026-04-225

spec-research

Catsofsuffering/ccsm

Research a requested change from Codex and turn findings into proposal-ready constraints. Use when a request needs bounded discovery before planning.

2026-04-225

frontend-design

Catsofsuffering/ccsm

Frontend design skill fused from Impeccable + custom extensions. Covers design philosophy, anti-AI-slop patterns, typography, color (OKLCH), spatial design, motion, interaction, responsive, UX writing, state management, engineering, and 4 style variants. Includes 20 command skills for audit/critique/polish/animate/etc.

2026-04-215

name	spec-review
description	Run the independent acceptance gate from Codex. Use when a change needs final verification against its spec, design, tasks, and execution evidence.
license	MIT

Review the change from Codex before archive.

Core contract

Codex performs the final acceptance gate.
Review compares the implementation against proposal, design, tasks, and verification evidence.
Archive only happens after Codex accepts the result.

Acceptance topology

The acceptance topology is distinct from execution routing. The topology roles are:

Decision owner (Codex): makes the final acceptance and archive decision. This is never delegated.
Optional acceptance reviewer (e.g., opencode): provides analysis that informs the decision, but the orchestrator makes the call. opencode is always additive, never the primary path.
Execution worker: implements bounded work and returns evidence. Workers never decide acceptance, never run spec-review, and never archive.

Steps

Select the active change with openspec status --change "<change-name>" --json.
Read proposal.md, design.md, tasks.md, and specs/**/*.md.
Inspect the current diff and the latest execution return packet.
Verify:
- tasks are complete
- constraints are satisfied
- required tests/checks were run
- no out-of-scope edits slipped in
If needed, run additional local checks.
Decide:
- Acceptance Passed and archive-ready
- Acceptance Failed with a bounded rework packet

Output

acceptance decision
supporting findings
rework packet or archive approval

Guardrails

Do not archive without verification evidence.
Do not delegate the final decision away from Codex.
Keep the result tied to the change contract, not personal preference.