write-next-story-from-shell-story

To convert shell story bullets into full Jira stories, the Skill loads the epic's Shell Stories section, identifies the next unwritten target, and generates a complete User Story Description with Acceptance Criteria in Gherkin format. It anchors the scope analysis directly to the shell bullets.

Yes, you can generate Gherkin acceptance criteria by providing a Jira epic key. The Skill loads only the Figma screens referenced in the target shell story, performs scope analysis, and outputs Non-Functional Requirements and Developer Notes alongside the Gherkin criteria.

Linking dependency stories happens automatically during ticket creation. After generating the full Jira story under the specified epic, the Skill links any identified dependency stories as blockers and marks the original shell story as complete in the epic upon success.

No, a specific shell story ID is optional. You can begin generating the full Jira story by providing just the Jira epic key, and the Skill will automatically identify and convert the next unwritten shell story in the epic's queue.

Scope analysis is performed by loading only the specific Figma screens referenced by the target shell story bullets. This targeted loading prevents full file processing and anchors the generated story description strictly to the relevant design frames.

Shell stories are marked complete in the epic only upon successful story generation and ticket creation. If the process fails to create the Jira issue under the specified epic or link dependencies, the shell story status remains unchanged to prevent data loss.