openspec-ff-change

To generate OpenSpec artifacts from a Jira ticket automatically, provide the ticket ID or change description to initiate the fast-forward process. The tool fetches ticket content via Jira MCP and scaffolds the complete set of implementation-ready files, avoiding manual step-by-step creation.

The correct build order for OpenSpec change artifacts is determined by enforcing mandatory steps and honoring applyRequires dependencies. The automation orchestrates this sequence internally, building dependent artifacts in the correct order to ensure valid change scaffolding.

Yes, you can scaffold a complete OpenSpec change using a brief description. The tool derives a kebab-case change name from your input and orchestrates the artifact build order, producing ready-to-implement files without requiring a full Jira ticket.

No, the OpenSpec fast-forward process does not require manual step-by-step creation. It automates the generation of all required artifacts, deriving the change name and enforcing dependency sequencing to produce implementation-ready files with minimal user input.

You need a Jira MCP integration only if you want to fetch ticket content directly. The tool can also initiate the fast-forward process using a user-provided kebab-case change name or a direct description of the change instead of a Jira ticket.