1---2name: openspec-ff-change3description: 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.4license: MIT5compatibility: Requires openspec CLI.6metadata:7 author: openspec8 version: "1.0"9 generatedBy: "1.4.1"10---1112Fast-forward through artifact creation - generate everything needed to start implementation in one go.1314**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.1516**Steps**17181. **If no clear input provided, ask what they want to build**1920 Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:21 > "What change do you want to work on? Describe what you want to build or fix."2223 From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).2425 **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.26272. **Create the change directory**28 ```bash29 openspec new change "<name>"30 ```31 This creates a scaffolded change in the planning home resolved by the CLI.32333. **Get the artifact build order**34 ```bash35 openspec status --change "<name>" --json36 ```37 Parse the JSON to get:38 - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)39 - `artifacts`: list of all artifacts with their status and dependencies40 - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.41424. **Create artifacts in sequence until apply-ready**4344 Use the **TodoWrite tool** to track progress through the artifacts.4546 Loop through artifacts in dependency order (artifacts with no pending dependencies first):4748 a. **For each artifact that is `ready` (dependencies satisfied)**:49 - Get instructions:50 ```bash51 openspec instructions <artifact-id> --change "<name>" --json52 ```53 - The instructions JSON includes:54 - `context`: Project background (constraints for you - do NOT include in output)55 - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)56 - `template`: The structure to use for your output file57 - `instruction`: Schema-specific guidance for this artifact type58 - `resolvedOutputPath`: Resolved path or pattern to write the artifact59 - `dependencies`: Completed artifacts to read for context60 - Read any completed dependency files for context61 - Create the artifact file using `template` as the structure and write it to `resolvedOutputPath`62 - Apply `context` and `rules` as constraints - but do NOT copy them into the file63 - Show brief progress: "✓ Created <artifact-id>"6465 b. **Continue until all `applyRequires` artifacts are complete**66 - After creating each artifact, re-run `openspec status --change "<name>" --json`67 - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array68 - Stop when all `applyRequires` artifacts are done6970 c. **If an artifact requires user input** (unclear context):71 - Use **AskUserQuestion tool** to clarify72 - Then continue with creation73745. **Show final status**75 ```bash76 openspec status --change "<name>"77 ```7879**Output**8081After completing all artifacts, summarize:82- Change name and location83- List of artifacts created with brief descriptions84- What's ready: "All artifacts created! Ready for implementation."85- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."8687**Artifact Creation Guidelines**8889- Follow the `instruction` field from `openspec instructions` for each artifact type90- The schema defines what each artifact should contain - follow it91- Read dependency artifacts for context before creating new ones92- Use `template` as the structure for your output file - fill in its sections93- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file94 - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact95 - These guide what you write, but should never appear in the output9697**Guardrails**98- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)99- Always read dependency artifacts before creating a new one100- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum101- If a change with that name already exists, suggest continuing that change instead102- Verify each artifact file exists after writing before proceeding to next