Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fengshao1227/openspec-ff-change
Fast-forward through OpenSpec artifact creation.
Passed 5 of 12 test cases with the skill, and 3 of 12 without it.
and 3 more in the full report
6 fixed3 passed either way11 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
Artifact `proposal` has completed. Artifact `tasks` depends on `proposal`. What must be done before drafting `tasks`?
| Checked | Without skill | With skill |
|---|---|---|
| Reads the completed proposal artifact file for context before generating tasks | Missed | Passed |
The instructions your model reads when the skill loads.
Fast-forward through artifact creation - generate everything needed to start implementation in one go.
Input: The user's request should include a change name (kebab-case) OR a description of what they want to build.
Steps
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.
Create the change directory
openspec new change "<name>"
This creates a scaffolded change at openspec/changes/<name>/.
Get the artifact build order
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 dependenciesCreate 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):
a. For each artifact that is ready (dependencies satisfied):
openspec instructions <artifact-id> --change "<name>" --json
test cases passed, vs 3 / 12 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.