openspec-ff-change

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