OpenSpec
PassAudited by ClawScan on May 13, 2026.
Overview
This instruction-only skill is coherent for OpenSpec-based project planning, with the main cautions being scoped project-file changes and persistent spec/instruction files.
This skill appears safe to install if you want OpenSpec-driven planning in repositories. Before use, make sure the OpenSpec tools available in your environment are trusted, run the workflow in the intended project directory, and review archived or generated spec files because they can influence future agent work.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The skill can update and move OpenSpec files in the repository as part of a normal close-out workflow.
Archiving mutates project specification state and uses a yes flag, but the workflow also tells the agent to validate and avoid archiving incomplete work unless the user accepts it.
`openspec_archive { changeName: "<change-name>", yes: true }` rolls the change's specs into the main spec set and moves the folderUse it in a version-controlled project and review the change state before archiving, especially when work is incomplete.
An agent could use less-specific OpenSpec subcommands if it chooses the escape hatch.
The escape-hatch tool broadens the available OpenSpec command surface beyond the enumerated safe workflow, though it is still framed as OpenSpec-specific rather than arbitrary shell execution.
`openspec_run` | Escape hatch for `openspec` subcommands not surfaced above
Prefer the named OpenSpec tools and use openspec_run only for clearly relevant OpenSpec commands after confirming the target project and intended effect.
Future sessions may rely on project-local specs and task lists when deciding what to implement next.
These persistent project files are intended to guide future agent work, so stale or tampered OpenSpec artifacts could influence later implementation decisions.
Specs and proposals live under `openspec/` in the project. Each in-flight change gets its own folder with `proposal.md`, `specs/`, `design.md`, and `tasks.md`.
Review OpenSpec files in untrusted or unfamiliar repositories, and treat them as project context that should not override explicit user instructions.
This review covers the instruction files, not the external OpenSpec tool package that may execute the referenced operations.
The skill itself contains no code to install, but it relies on environment-provided OpenSpec tooling whose implementation is not included in the reviewed artifacts.
Source: unknown; Homepage: none; No install spec — this is an instruction-only skill.
Use OpenSpec tools from a trusted installation source and keep them pinned or reviewed according to your normal project security practices.