openspec-ff-change — how to use openspec-ff-change how to use openspec-ff-change, openspec-ff-change setup guide, Jira MCP integration with openspec-ff-change, openspec-ff-change alternative tools, openspec-ff-change vs other development accelerators, installing openspec-ff-change for AI agents, what is openspec-ff-change and its benefits, openspec-ff-change for rapid artifact creation, openspec-ff-change and Jira ticket integration, openspec-ff-change best practices for developers

Fast-forward through artifact creation - generate everything needed to start implementation in one go.

Input: The user's request should include:

• A Jira ticket ID (e.g., SCRUM-123) - will fetch ticket content using Jira MCP
• A change name (kebab-case) - will use that name directly
• A description of what they want to build - will derive a kebab-case name

Steps

1. Determine input type and get context

   a. If input looks like a Jira ticket ID (matches pattern like SCRUM-123, PROJ-456, etc.):

   • Use getAccessibleAtlassianResources MCP tool to get the cloudId
   • Use getJiraIssue MCP tool with:
     • cloudId: from step above
     • issueIdOrKey: the provided ticket ID
   • Extract ticket content (title, description, acceptance criteria, etc.)
   • Derive a kebab-case change name from the ticket title:
     • Convert ticket title to lowercase
     • Replace spaces and special characters with hyphens
     • Remove any leading/trailing hyphens
     • Example: "Update Position API" → update-position-api, "Add User Auth" → add-user-auth
     • If ticket title is unclear or too long, use a shortened meaningful version
   • Use the derived kebab-case name as <name> for the change directory
   • Use ticket content as context for creating artifacts
   • Store ticket ID for reference (e.g., in proposal or as metadata)

   b. If input is a change name (kebab-case format):

   • Use the provided name directly
   • Check if change already exists, if so ask user if they want to continue it

   c. If input is a description:

   • Derive a kebab-case name (e.g., "add user authentication" → add-user-auth)

   d. If no input provided:

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

     "What change do you want to work on? Provide a Jira ticket ID (e.g., SCRUM-123), change name, or describe what you want to build."

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

2. Create the change directory

   bash
   1openspec new change "<name>"

   This creates a scaffolded change at openspec/changes/<name>/.

2.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."

3. Get the artifact build order

   bash
   1openspec 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:

     bash
     1openspec 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
   • CRITICAL for tasks artifact: If creating tasks.md:
     • Read openspec/config.yaml to get backend-specific rules (mandatory steps, branch naming, etc.)
     • Read .claude/rules/openspec-tasks-mandatory-steps.mdc to understand mandatory testing requirements and agent execution responsibilities
     • Task structure requirements
     • All mandatory steps that MUST be included (e.g., Step 0: Create Feature Branch)
   • If Jira ticket was provided: Use ticket content to inform artifact creation (especially proposal and tasks)
   • 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
   • For tasks artifact: Ensure all mandatory steps from config.yaml and the rule file are included:
     • Step 0: Create Feature Branch (MUST be first step for backend changes)
     • Review and Update Existing Unit Tests (MANDATORY)
     • Run Unit Tests and Verify Database State (MANDATORY)
     • Manual Endpoint Testing with curl (MANDATORY - AGENT MUST EXECUTE)
     • E2E Testing with Playwright MCP (MANDATORY if applicable - AGENT MUST EXECUTE)
     • Update Technical Documentation (MANDATORY)
   • For manual testing tasks: Include sub-tasks that make it clear the agent must execute tests (e.g., "Test GET endpoints with curl", "Restore database state", etc.)
   • Show brief progress: "✓ Created <artifact-id>"

   b. Continue until all applyRequires artifacts are complete

   • After creating each artifact, re-run 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

   bash
   1openspec 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
• For tasks.md: Read .claude/rules/openspec-tasks-mandatory-steps.mdc to ensure all mandatory steps are included with proper agent execution requirements
• 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