draft-a-story-markdown-from-a-story-tracker-or-feature-descripti

# Draft a story markdown from a story tracker or feature description ## Overview This skill helps junior developers create technical story markdown by: 1. Gathering requirements from a story tracker or a provided feature description 2. Fetching Figma designs linked in the story (when applicable) 3. Exploring the codebase to discover relevant files and patterns 4. Generating a draft `story.md` for the developer to review and refine ## Instructions ### Phase 1: Gather Requirements #### Option A: Ticket ID provided When the input is a ticket ID (matching a pattern like `PROJ-123`, `86d2uf1mh`, `4821`, `AB#4821`). A bare integer is always a ticket ID, never a feature description: - Use the project's story tracker MCP tools (Jira, ClickUp, Azure DevOps) to fetch the story by its ticket ID and download its attachments. If no story tracker MCP tool is available, tell the developer the project has no story tracker MCP server configured (`/mcp` to check status) and ask them to paste the story details or provide a feature description instead — never guess at the story content. - Extract: - Type (Story, Task, Bug/Defect, etc.) - Summary (user story statement) - Description (context and background) - Acceptance criteria (requirements) - Subtasks (if any) - Figma links (URLs matching `figma.com/file/` or `figma.com/design/`) - Steps to reproduce, actual and expected behaviour (bug tickets) - Treat the ticket as a bug when its type is `Bug`, `Defect`, `Incident` or equ...