agentleFS
Sign inStart free
LIDR-academyLIDR-academy/AI4Devs-LTI-extended/.claude/skills/openspec-new-change/SKILL.md

openspec-new-change

Skill278 starsChanged 6 months 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.

We split this skill into the rules it gives an agent

16 rules. 9 are common, 5 are distinctive, and 2 are very specific to this project.

  • 9

    Common

    Most of the 62 edited versions we read keep these.

  • 5

    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. Distinctive:

    If the user has attached files to this conversation:

    line 45
  7. Distinctive:

    Check for any files in the conversation context (attached files will be visible in the file list)

    line 46
  8. Distinctive:

    Read the file to get its current path

    line 48
  9. Distinctive:

    Use the file system tools to copy/move the file, preserving the original filename

    line 50
  10. Distinctive:

    If files were moved, inform the user: "Moved N attached file(s) to the change directory root."

    line 51
  11. Common:

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

    line 61
  12. Common:

    After completing the steps, summarize:

    line 71
  13. Common:

    Do NOT create any artifacts yet - just show the instructions

    line 79
  14. Common:

    Do NOT advance beyond showing the first artifact template

    line 80
  15. Common:

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

    line 81
  16. Common:

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

    line 82

“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.

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.

3.5. Handle attached files (if any) If the user has attached files to this conversation:

  • Check for any files in the conversation context (attached files will be visible in the file list)
  • For each attached file:
    • Read the file to get its current path
    • Move it to the root of the change directory: openspec/changes/<name>/<filename>
    • Use the file system tools to copy/move the file, preserving the original filename
  • If files were moved, inform the user: "Moved N attached file(s) to the change directory root."
  1. Show the artifact status
    openspec status --change "<name>"
    This shows which artifacts need to be created and which are ready (dependencies satisfied).
  2. 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.
  3. 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.

Reviews can't be read right now.

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