source-command-opsx-propose

Creates OpenSpec change proposals with proposal, design, and tasks artifacts via CLI commands.

Updated Jun 6, 2026
One-click install
npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-propose-jonathanlin768
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-command-opsx-propose
Source: https://github.com/jonathanlin768/CS2Match-Nakama/tree/main/.agents/skills/source-command-opsx-propose
Command: npx skills add https://github.com/jonathanlin768/CS2Match-Nakama --skill source-command-opsx-propose-jonathanlin768

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new feature or change without a structured plan leads to unclear requirements and missed implementation steps. This Skill scaffolds a complete OpenSpec change proposal, generating all required planning artifacts in one guided workflow. ## Core Features & Use Cases - One-Step Change Creation: Runs openspec new change to scaffold a change directory, then generates proposal.md, design.md, and tasks.md in dependency order. - Schema-Driven Artifacts: Fetches per-artifact instructions, templates, and rules from the OpenSpec CLI so each file follows the project's specification format. - Interactive Clarification: Asks the user what they want to build when no input is given, deriving a kebab-case change name from the description. - Use Case: A developer wants to add user authentication. They invoke the propose command with a description, and the Skill creates the change scaffold, writes the proposal, design, and task breakdown, then reports the change is ready for implementation. ## Quick Start Ask the AI to propose a new change by describing what you want to build, for example: run /opsx:propose to add user authentication.

Frequently Asked Questions about source-command-opsx-propose

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

FAQPage Schema
How do I create an OpenSpec change proposal?

Run the propose command with a change name or a description of what you want to build. The workflow runs openspec new change to scaffold the directory, then generates proposal.md, design.md, and tasks.md in dependency order.

What artifacts does an OpenSpec proposal generate?

It generates proposal.md describing what and why, design.md describing how, and tasks.md listing implementation steps. The exact set is determined by the schema's applyRequires field returned by openspec status.

Does the propose command require the openspec CLI?

Yes, the workflow depends on the openspec command-line tool for scaffolding changes, fetching artifact instructions, and checking status. Install it globally with npm before running the command.

What happens if I run propose without providing a change name?

The workflow asks what you want to build using an open-ended question, then derives a kebab-case name from your description, such as turning add user authentication into add-user-auth.

What if a change with the same name already exists?

The workflow asks whether you want to continue the existing change or create a new one, rather than overwriting or failing silently.