ElasticKnown publisherelastic/terraform-provider-elasticstack/.agents/skills/openspec-new-change/SKILL.mdopenspec-new-change
Skill210 starsChanged 6 months agoApache-2.0View on GitHub
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
We split this skill into the rules it gives an agent
12 rules. 8 are common, 1 is distinctive, and 3 are very specific to this project.
8
Common
Most of the 62 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 13
Start a new change using the experimental artifact-driven approach.
- Distinctive: line 23
Ask the user (open-ended, no preset options):
- Common: line 28
IMPORTANT: Do NOT proceed without understanding what the user wants to build.
- Very specific: line 32
Use the default schema (omit --schema) unless the user explicitly requests a different workflow.
- Very specific: line 44
Add --schema <name> only if the user requested a specific workflow.
- Very specific: line 51
Use the returned planningHome, changeRoot, artifactPaths, and nextSteps instead of assuming repo-local paths.
- Common: line 55
Check the status output to find the first artifact with status "ready".
- Common: line 65
After completing the steps, summarize:
- Common: line 73
Do NOT create any artifacts yet - just show the instructions
- Common: line 74
Do NOT advance beyond showing the first artifact template
- Common: line 75
If the name is invalid (not kebab-case), ask for a valid name
- Common: line 76
If a change with that name already exists, suggest continuing that change instead
“Common” is measured: kept by at least 6 in 10 of the 62 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Start a new change using the experimental artifact-driven approach.
Store selection: If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run openspec store list --json to discover registered store ids, then pass --store <id> on the commands that read or write specs and changes (new change, status, instructions, list, show, validate, archive, doctor, context, schemas, view). Once selected, treat --store <id> as sticky for the rest of the workflow. Every unscoped example of those commands below is shorthand: before running it, append the flag. For example, run openspec status --change "<name>" --json --store "<id>", not the unscoped form shown below. Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local openspec/ root.
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
Ask the user (open-ended, no preset options):
"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.
Determine the workflow schema
Use the default schema (omit
--schema) unless the user explicitly requests a different workflow.Use a different schema only if the user mentions:
- A specific schema name → use
--schema <name> - "show workflows" or "what workflows" → run
openspec schemas --jsonand let them choose
Otherwise: Omit
--schemato use the default.- A specific schema name → use
- Create the change directory
Addopenspec new change "<name>"--schema <name>only if the user requested a specific workflow. This creates a scaffolded change in the planning home resolved by the CLI. - Show the artifact status
Use the returnedopenspec status --change "<name>" --jsonplanningHome,changeRoot,artifactPaths, andnextStepsinstead of assuming repo-local paths. - Get instructions for the first artifact
The first artifact depends on the schema (e.g.,
proposalfor spec-driven). Check the status output to find the first artifact with status "ready".
This outputs the template and context for creating the first artifact.openspec instructions <first-artifact-id> --change "<name>" - STOP and wait for user direction
Output
After completing the steps, summarize:
- Change name and location
- Schema/workflow being used and its artifact sequence
- Current status (0/N artifacts complete)
- The template for the first artifact
- Prompt: "Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue."
Guardrails
- Do NOT create any artifacts yet - just show the instructions
- Do NOT advance beyond showing the first artifact template
- If the name is invalid (not kebab-case), ask for a valid name
- If a change with that name already exists, suggest continuing that change instead
- Pass --schema if using a non-default workflow
Other versions67 projects use a version of this.
Word for word · 1
- elastic/terraform-provider-ec★ 183100% same
Edited · 62
- Fission-AI/OpenSpec★ 74k60% same
- alibaba/druid★ 28k86% same
- PBH-BTN/PeerBanHelper★ 6.3k83% same
- fengshao1227/ccg-workflow★ 5.9k86% same
- Soju06/codex-lb★ 3.3k87% same
- Draculabo/AntigravityManager★ 2.4k86% same
- microsoft/rayfin★ 64682% same
- mckinsey/agents-at-scale-ark★ 42986% same
- jerrywu001/cc-sessions-viewer★ 41186% same
- atilladeniz/Kubeli★ 38787% same
52 more not listed
Wrote their own version · 4
- studyzy/imewlconverter★ 10ksame name
- studyzy/OpenSpec-cn★ 1.2ksame name
- charliehzm/medharness★ 85same name
- minghaoZhangZ/shipkit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use openspec-ff-change, openspec-bulk-archive-change and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillopenspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Also in 57 projects that use this
- MicrosoftSkill
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
Also in 53 projects that use this
studyzySkilldraft-openspec-docs
OpenSpec 文档的协作式页面起草模式。在目标页面内部构建一份草稿计划（目的、结构、编号起草步骤），与用户一起迭代，然后按已批准的步骤逐章节起草，并在完成后清理自身。在页面需要从头重写，或一个新区块需要用户参与塑形时使用。
Also in 3 projects that use this
- studyzySkill
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is complete, what the next release step is, or to continue a release paused for human approval.
Also in 3 projects that use this
Microsoft AzureSkillopenspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
Also in 12 projects that use this
VercelSkillvercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 3 projects that use this
- +1 more from microsoft
- +2 more from studyzy
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- existing-entity-requirementsSkill
- flaky-test-catcherSkill
- new-entity-requirementsSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-implementation-loopSkill
- openspec-plus-applySkill
- openspec-plus-designSkill
- openspec-plus-proposalSkill
- openspec-plus-specSkill
- openspec-plus-tasksSkill
- openspec-plus-tddSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- pr-monitoring-loopSkill
- requirements-verificationSkill
- schema-coverageSkill
- agentic-workflowsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.