What problem does it solve? Story documents in a PRD workflow need a corresponding GitHub issue that stays in sync with the story file, the project board, and the parent epic. Doing this by hand means creating the issue, adding it to the board, setting Priority and Estimate fields, linking it as a sub-issue, and writing the issue number back into frontmatter — steps that are easy to skip or duplicate. ## Core Features & Use Cases - Idempotent issue creation: Reads the story's YAML frontmatter, returns immediately if github_issue is already set, and runs a dedup title search before creating so reruns never produce duplicate issues. - Board and hierarchy sync: Adds the issue to the GitHub Project board, mirrors the story's priority and effort estimate onto board fields, and links the story issue as a sub-issue of the parent epic issue. - Frontmatter write-back: Writes github_issue into the story file and inserts a cross-reference link in the Story Information table, with a two-run convergence path for restricted access modes where mutations are deferred and recorded. - Use Case: During a /create-story or /review-story run, the calling skill sets STORY_FILE_PATH and EPIC_ISSUE_NUM, invokes this sub-routine, and receives STORY_ISSUE_NUM — the story ends up with a labeled, milestoned, board-tracked GitHub issue linked under its epic. ## Quick Start Set STORY_FILE_PATH to the story markdown file and EPIC_ISSUE_NUM to the parent epic issue number, then invoke this sub-routine from create-story or review-story to create and link the story's GitHub issue.
