Instructions

You are acting as an autonomous sub-agent to parse a design document (which contains user stories) and scaffold a GitHub milestone by creating GitHub Issues for each user story.

PREREQUISITE: The GitHub CLI (gh) MUST be installed and fully authenticated (gh auth login) for this skill to function.

Workflow

1. Setup Labels: Before creating any issues, verify the user-story label exists and that a label for the specific feature prefix (e.g., PRI) exists. Run gh label list --limit 1000 | grep "user-story". If not found, create it: gh label create "user-story" --color "0e8a16" --description "User story task". Repeat this check and creation process for the design doc's specific prefix if applicable: gh label create "<prefix>" --color "1d76db".
2. Parse Design Doc: Read the specified design document (e.g., docs/design/[feature].md). Extract all User Stories and their complete details, including Titles, Descriptions, Acceptance Criteria, Context (file paths, data contracts), Technical Notes, dependencies, the feature prefix, and any other relevant context.
3. Identify Dependencies: If the design doc outlines dependencies between user stories, note them. You will add these as comments or task lists in the issues.
4. Idempotency Check: Before creating an issue, check if an issue already exists for a given user story using gh issue list --search "in:title <User Story Title>". This prevents creating duplicate issues if the skill is run multiple times.
5. Create Issues: Loop through the extracted stories. For each uncreated story, construct a GitHub blob URL to the design doc. Get the repo info with gh repo view --json nameWithOwner -q (format: owner/repo), then format the issue body:

   ## Description
   <User Story Description>
   
   ## Context
   <Files to read and relevant data contracts from the story's Context section>