Agent skill
openspec-cli
Guidelines for using the OpenSpec CLI tool in non-interactive environments. Use this skill when validating specifications or changes to ensure commands run successfully without user intervention.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/openspec-cli
Metadata
Additional technical details for this skill
- short description
- Run OpenSpec validation non-interactively
SKILL.md
OpenSpec CLI Guidelines
This skill provides instructions for using the openspec command-line interface (CLI) effectively within the MCP environment, where interactive prompts are not supported.
Core Principles
- Non-Interactive Mode: Always use flags that bypass interactive prompts.
- Explicit Targets: Specify exactly what to validate to avoid ambiguity.
Validation Commands
The default openspec validate command triggers an interactive mode which will cause the agent to hang or fail. Use the following explicit commands instead:
Validate All
To validate the entire project:
openspec validate --all
Validate Changes
To validate only the currently changed files (useful for quick checks):
openspec validate --changes
Validate Specifications
To validate only the specification files:
openspec validate --specs
Validate Specific Item
To validate a specific item by name:
openspec validate <item-name>
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?