agentleFS
Sign inStart free
practicajspracticajs/the-frontend-testing-skill/.claude/skills/openspec-new-change/SKILL.md

openspec-new-change

Skill13 starsChanged 26 days agoMITView 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.

66 other projects use a version of this, 48 of them edited; 5 new projects in the last 4 weeks, against 4 the 4 before.

Adopted by

Rising: 5 new projects took it in the last 4 weeks, 1.3× the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 2 new projectsWeek of Oct 4: 2 new projectsWeek of Oct 11: 1 new projectWeek of Oct 18: 2 new projectsWeek of Oct 25: 2 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 9 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use draft-openspec-docs, release-openspec and 3 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.
  • goernSkill

    draft-openspec-docs

    Collaborative page-drafting mode for the OpenSpec docs. Builds a scratch plan inside the target page (purpose, structure, numbered draft steps), iterates on it with the user, then drafts one section per approved step and cleans up after itself. Use when a page needs a from-scratch rewrite or a new page is being shaped with the user in the loop.

    Also in 3 projects that use this

  • goernSkill

    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 AzureSkill

    openspec-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 11 projects that use this

  • +2 more from goern

The file

We split this skill into the rules it gives an agent

11 rules. 9 are common, 0 are distinctive, and 2 are very specific to this project.

  • 9

    Common

    Most of the 48 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Start a new change using the experimental artifact-driven approach.

    line 12
  2. Common:

    Use the AskUserQuestion tool (open-ended, no preset options) to ask:

    line 20
  3. Common:

    IMPORTANT: Do NOT proceed without understanding what the user wants to build.

    line 25
  4. Very specific:

    Use the default schema (omit --schema) unless the user explicitly requests a different workflow.

    line 29
  5. Very specific:

    Add --schema <name> only if the user requested a specific workflow.

    line 41
  6. Common:

    Check the status output to find the first artifact with status "ready".

    line 52
  7. Common:

    After completing the steps, summarize:

    line 62
  8. Common:

    Do NOT create any artifacts yet - just show the instructions

    line 70
  9. Common:

    Do NOT advance beyond showing the first artifact template

    line 71
  10. Common:

    If the name is invalid (not kebab-case), ask for a valid name

    line 72
  11. Common:

    If a change with that name already exists, suggest continuing that change instead

    line 73

“Common” is measured: kept by at least 6 in 10 of the 48 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Start a new change using the experimental artifact-driven approach.

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. 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 --json and let them choose

    Otherwise: Omit --schema to use the default.

  3. Create the change directory
    openspec new change "<name>"
    Add --schema <name> only if the user requested a specific workflow. This creates a scaffolded change at openspec/changes/<name>/ with the selected schema.
  4. Show the artifact status
    openspec status --change "<name>"
    This shows which artifacts need to be created and which are ready (dependencies satisfied).
  5. Get instructions for the first artifact The first artifact depends on the schema (e.g., proposal for spec-driven). Check the status output to find the first artifact with status "ready".
    openspec instructions <first-artifact-id> --change "<name>"
    This outputs the template and context for creating the first artifact.
  6. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free