agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/rayfin/.github/skills/openspec-ff-change/SKILL.md

openspec-ff-change

Skill646 starsChanged 24 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

19 rules. 11 are common, 0 are distinctive, and 8 are very specific to this project.

  • 11

    Common

    Most of the 60 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

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

    line 20
  2. Common:

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

    line 25
  3. Common:

    Use the TodoWrite tool to track progress through the artifacts.

    line 43
  4. Common:

    Read any completed dependency files for context

    line 59
  5. Very specific:

    Create the artifact file using template as the structure

    line 60
  6. Very specific:

    After creating each artifact, re-run npx openspec status --change "<name>" --json

    line 65
  7. Very specific:

    Check if every artifact ID in applyRequires has status: "done" in the artifacts array

    line 66
  8. Very specific:

    Stop when all applyRequires artifacts are done

    line 67
  9. Common:

    Use AskUserQuestion tool to clarify

    line 70
  10. Common:

    After completing all artifacts, summarize:

    line 80
  11. Very specific:

    Follow the instruction field from openspec instructions for each artifact type

    line 88
  12. Common:

    Read dependency artifacts for context before creating new ones

    line 90
  13. Very specific:

    Use template as the structure for your output file - fill in its sections

    line 91
  14. Very specific:

    Do NOT copy <context>, <rules>, <project_context> blocks into the artifact

    line 93
  15. Very specific:

    Create ALL artifacts needed for implementation (as defined by schema's apply.requires)

    line 97
  16. Common:

    Always read dependency artifacts before creating a new one

    line 98
  17. Common:

    If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum

    line 99
  18. Common:

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

    line 100
  19. Common:

    Verify each artifact file exists after writing before proceeding to next

    line 101

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

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

  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. Create the change directory
    npx openspec new change "<name>"
    This creates a scaffolded change at openspec/changes/<name>/.
  3. Get the artifact build order
    npx 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 dependencies

  4. Create 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):

    • Get instructions:
      npx openspec instructions <artifact-id> --change "<name>" --json
    • The instructions JSON includes:
      • context: Project background (constraints for you - do NOT include in output)
      • rules: Artifact-specific rules (constraints for you - do NOT include in output)
      • template: The structure to use for your output file
      • instruction: Schema-specific guidance for this artifact type
      • outputPath: Where to write the artifact
      • dependencies: Completed artifacts to read for context
    • Read any completed dependency files for context
    • Create the artifact file using template as the structure
    • Apply context and rules as constraints - but do NOT copy them into the file
    • Show brief progress: "✓ Created <artifact-id>"

    b. Continue until all applyRequires artifacts are complete

    • After creating each artifact, re-run npx openspec status --change "<name>" --json
    • Check if every artifact ID in applyRequires has status: "done" in the artifacts array
    • Stop when all applyRequires artifacts are done

    c. If an artifact requires user input (unclear context):

    • Use AskUserQuestion tool to clarify
    • Then continue with creation
  5. Show final status
    npx openspec status --change "<name>"

Output

After completing all artifacts, summarize:

  • Change name and location
  • List of artifacts created with brief descriptions
  • What's ready: "All artifacts created! Ready for implementation."
  • Prompt: "Run /opsx:apply or ask me to implement to start working on the tasks."

Artifact Creation Guidelines

  • Follow the instruction field from openspec instructions for each artifact type
  • The schema defines what each artifact should contain - follow it
  • Read dependency artifacts for context before creating new ones
  • Use template as the structure for your output file - fill in its sections
  • IMPORTANT: context and rules are constraints for YOU, not content for the file
    • Do NOT copy <context>, <rules>, <project_context> blocks into the artifact
    • These guide what you write, but should never appear in the output

Guardrails

  • Create ALL artifacts needed for implementation (as defined by schema's apply.requires)
  • Always read dependency artifacts before creating a new one
  • If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum
  • If a change with that name already exists, suggest continuing that change instead
  • Verify each artifact file exists after writing before proceeding to next

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