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.
76
72%
Does it follow best practices?
Impact
69%
1.04xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/openspec-propose/SKILL.mdFull propose workflow with CLI commands
openspec new change
100%
90%
Status --json for build order
70%
50%
Instructions command per artifact
60%
40%
Dependency order respected
100%
90%
Template used as structure
90%
100%
No context/rules in output
100%
100%
TodoWrite for tracking
0%
0%
Re-check status after each artifact
37%
25%
Final status without --json
25%
25%
Brief progress messages
0%
25%
Dependency files read first
75%
62%
Ambiguous input handling and final summary format
AskUserQuestion used
0%
0%
Open-ended question format
0%
0%
Kebab-case change name
100%
100%
openspec new change used
100%
100%
All applyRequires artifacts created
100%
100%
Summary includes change location
100%
100%
Summary lists artifacts with descriptions
100%
100%
Readiness statement present
100%
100%
Next step prompt included
100%
100%
Context not in artifacts
100%
100%
Existing change handling and artifact verification workflow
Existing change handled
66%
50%
Dependencies read before creation
16%
100%
File verification logged
30%
20%
Stops at applyRequires completion
90%
100%
Commands logged in order
87%
100%
Artifact creation order logged
100%
100%
openspec instructions used per artifact
70%
100%
Final status documented
62%
100%
No context blocks in artifacts
100%
100%
TodoWrite used
0%
0%
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.