publish

# /ouroboros:publish Convert a Seed specification into structured GitHub Issues for team workflows. ## Usage ``` ooo publish [seed_path] /ouroboros:publish [seed_path] ``` **Trigger keywords:** "publish to github", "create issues from seed", "seed to issues" ## Instructions When the user invokes this skill: ### Step 1: Prerequisite Check **1a. Verify `gh` CLI is installed:** ```bash command -v gh >/dev/null 2>&1 && echo "OK" || echo "MISSING" ``` If missing, tell the user: ``` GitHub CLI (gh) is not installed. Install it: https://cli.github.com/ ``` Stop. **1b. Verify `gh` is authenticated:** ```bash gh auth status ``` If not authenticated, tell the user: ``` GitHub CLI is not authenticated. Run: gh auth login ``` Stop. ### Step 2: Locate the Seed Ouroboros stores seeds in `~/.ouroboros/seeds/`: - **Interview seeds**: `~/.ouroboros/seeds/{seed_id}.yaml` (YAML) - **PM seeds**: `~/.ouroboros/seeds/pm_seed_{id}.json` (JSON) Determine the Seed source in this priority order: 1. **Explicit path argument**: If the user provided a file path (`.yaml` or `.json`), read it directly 2. **Most recent seed file**: Search for the most recent seed in the standard location: ```bash ls -t ~/.ouroboros/seeds/*.yaml ~/.ouroboros/seeds/*.json 2>/dev/null | head -5 ``` If multiple seeds exist, present the top candidates via AskUserQuestion and let the user choose. 3. **Conversation context**: If `ooo seed` or `ooo pm` was just run in this conversation and the seed path...