clone-gen2-migration-epic

Clones the SWC-1727 Jira migration epic template and seven child stories for a target component.

1.5k|261|Updated Nov 19, 2018
One-click install
npx skills add https://github.com/adobe/spectrum-web-components --skill clone-gen2-migration-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clone-gen2-migration-epic
Source: https://github.com/adobe/spectrum-web-components/tree/main/.ai/skills/jira-epic/clone-gen2-migration-epic
Command: npx skills add https://github.com/adobe/spectrum-web-components --skill clone-gen2-migration-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Setting up a new Spectrum Web Components gen2 migration in Jira requires manually recreating an epic and seven child stories with correct summaries, story points, labels, and dependency links, which is repetitive and error-prone.

Core Features & Use Cases

  • Template Cloning: Fetches SWC-1727 and its seven child stories, then creates new issues with all [COMPONENT] placeholders replaced by the target component name.
  • Structured Linking: Links stories to the new epic via Child-Issue, attaches the epic under SWC-1607, and applies the full "is blocked by" dependency chain between stories.
  • Use Case: A developer starting the migration of the action-button component asks to clone the migration template, and receives a fully linked epic with seven stories, correct story points, and a summary table of new Jira keys.

Quick Start

Ask the assistant to clone the migration epic template for your component, for example: create the migration epic for action-button.

Frequently Asked Questions about clone-gen2-migration-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new component migration epic in Jira for Spectrum Web Components?

Provide the component name, such as action-button, and the skill clones the SWC-1727 template epic plus its seven child stories. It replaces all [COMPONENT] placeholders, creates issues sequentially, and links them with the correct dependency chain.

What Jira issues does the SWC migration template include?

The template includes one epic and seven stories covering accessibility recommendations, analysis and migration planning, foundations, S2 visual fidelity, code style and testing, Storybook documentation, and final review. Each story carries predefined story points from the template.

Why are Jira issues created one at a time instead of in parallel?

Issues are created with batchSize 1 because parallel batch creation causes non-sequential key assignment. Sequential creation guarantees predictable key ordering so stories can be linked to the epic and each other correctly.

What placeholders remain after cloning the migration epic?

Markers like [PLACEHOLDER: ...] are intentionally left intact for manual updates. These include the Figma design link, Stackblitz link, 1st-gen component source path, and 1st-gen test path, which the engineer fills in after creation.

What happens if a Jira issue creation or link call fails?

If an issue creation fails, the process stops and reports the failed step rather than skipping silently. Link failures are reported but treated as recoverable, since links can be added manually in Jira afterward.