Openspec Propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
Install
npx skills add rpamis/comet --skill openspec-proposegit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/dependency/openspec/openspec-propose ~/.claude/skills/openspec-proposePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
Propose a new change - create the change and generate all artifacts in one step. I'll create a change with artifacts: - proposal.md (what & why) - design.md (how) - tasks.md (implementation steps) When ready to implement, run /opsx:apply --- **Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build. **Steps** 1. **If no clear input provided, ask what they want to build** Use the **AskUserQuestion tool** (open-ended, no preset options) to ask: > "What change do you want to work on? Describe what you want to build or fix." From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`). **IMPORTANT**: Do NOT proceed without understanding what the user wants to build. 2. **Create the change directory** ```bash openspec new change "<name>" ``` This creates a scaffolded change at `openspec/changes/<name>/` with `.openspec.yaml`. 3. **Get the artifact build order** ```bash openspec status --change "<name>" --json ``` Parse the JSON to get: - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`) - `artifacts`: list of all artifacts with their status and dependencies 4. **Create artifacts in sequence until apply-ready** Use the **TodoWrite tool** to track progress through the artifacts. Loop through artifacts in dependency order (artifacts with no pending dependencies first):
Details
- Skill name
openspec-propose- Repository
- rpamis/comet
- Path
eval/local/skills/benchmarks/dependency/openspec/openspec-propose/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Openspec Propose skill do?
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
How do I install the Openspec Propose skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill openspec-propose. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Openspec Propose popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Sred Project Organizer
1.2kgetsentry/skills
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
Openspec Onboard
3.3krpamis/comet
Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work.
Sred Work Summary
1.2kgetsentry/skills
Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.