[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FBG096RKX00PCVNJN0PSM":3,"skill-same:01M79FBG096RKX00PCVNJN0PSM":45},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79FBG096RKX00PCVNJN0PSM","ralph-tui-create-beads",null,"Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.","BumpyClock\u002Fagent-templates","BumpyClock","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1883824?v=4","01M79EW0FDP9MFXH1FKH800S7T","Aditya Sharma","01M79EW0G27TTKZWTFQ8W5HVB4",2,"MIT","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fralph-tui-create-beads\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ralph-tui-create-beads\ndescription: \"Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.\"\n---\n\n# Ralph TUI - Create Beads\n\nConverts PRDs to beads (epic + child tasks) for ralph-tui autonomous execution.\n\n> **Note:** This skill is bundled with ralph-tui's Beads tracker plugin. Future tracker plugins (Linear, GitHub Issues, etc.) will bundle their own task creation skills.\n\n---\n\n## The Job\n\nTake a PRD (markdown file or text) and create beads in `.beads\u002Fbeads.jsonl`:\n1. **Extract Quality Gates** from the PRD's \"Quality Gates\" section\n2. Create an **epic** bead for the feature\n3. Create **child beads** for each user story (with quality gates appended)\n4. Set up **dependencies** between beads (schema → backend → UI)\n5. Output ready for `ralph-tui run --tracker beads`\n\n---\n\n## Step 1: Extract Quality Gates\n\nLook for the \"Quality Gates\" section in the PRD:\n\n```markdown\n## Quality Gates\n\nThese commands must pass for every user story:\n- `pnpm typecheck` - Type checking\n- `pnpm lint` - Linting\n\nFor UI stories, also include:\n- Verify in browser using dev-browser skill\n```\n\nExtract:\n- **Universal gates:** Commands that apply to ALL stories (e.g., `pnpm typecheck`)\n- **UI gates:** Commands that apply only to UI stories (e.g., browser verification)\n\n**If no Quality Gates section exists:** Ask the user what commands should pass, or use a sensible default like `npm run typecheck`.\n\n---\n\n## Output Format\n\nBeads use `bd create` command with **HEREDOC syntax** to safely handle special characters:\n\n```bash\n# Create epic (link back to source PRD)\nbd create --type=epic \\\n  --title=\"[Feature Name]\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\n[Feature description from PRD]\nEOF\n)\" \\\n  --external-ref=\"prd:.\u002Ftasks\u002Ffeature-name-prd.md\"\n\n# Create child bead (with quality gates in acceptance criteria)\nbd create \\\n  --parent=EPIC_ID \\\n  --title=\"[Story Title]\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\n[Story description with acceptance criteria INCLUDING quality gates]\nEOF\n)\" \\\n  --priority=[1-4]\n```\n\n> **CRITICAL:** Always use `\u003C\u003C'EOF'` (single-quoted) for the HEREDOC delimiter. This prevents shell interpretation of backticks, `$variables`, and `()` in descriptions.\n\n---\n\n## Story Size: The #1 Rule\n\n**Each story must be completable in ONE ralph-tui iteration (~one agent context window).**\n\nralph-tui spawns a fresh agent instance per iteration with no memory of previous work. If a story is too big, the agent runs out of context before finishing.\n\n### Right-sized stories:\n- Add a database column + migration\n- Add a UI component to an existing page\n- Update a server action with new logic\n- Add a filter dropdown to a list\n\n### Too big (split these):\n- \"Build the entire dashboard\" → Split into: schema, queries, UI components, filters\n- \"Add authentication\" → Split into: schema, middleware, login UI, session handling\n- \"Refactor the API\" → Split into one story per endpoint or pattern\n\n**Rule of thumb:** If you can't describe the change in 2-3 sentences, it's too big.\n\n---\n\n## Story Ordering: Dependencies First\n\nStories execute in dependency order. Earlier stories must not depend on later ones.\n\n**Correct order:**\n1. Schema\u002Fdatabase changes (migrations)\n2. Server actions \u002F backend logic\n3. UI components that use the backend\n4. Dashboard\u002Fsummary views that aggregate data\n\n**Wrong order:**\n1. ❌ UI component (depends on schema that doesn't exist yet)\n2. ❌ Schema change\n\n---\n\n## Dependencies with `bd dep add`\n\nUse the `bd dep add` command to specify which beads must complete first:\n\n```bash\n# Create the beads first\nbd create --parent=epic-123 --title=\"US-001: Add schema\" ...\nbd create --parent=epic-123 --title=\"US-002: Create API\" ...\nbd create --parent=epic-123 --title=\"US-003: Build UI\" ...\n\n# Then add dependencies (issue depends-on blocker)\nbd dep add ralph-tui-002 ralph-tui-001  # US-002 depends on US-001\nbd dep add ralph-tui-003 ralph-tui-002  # US-003 depends on US-002\n```\n\n**Syntax:** `bd dep add \u003Cissue> \u003Cdepends-on>` — the issue depends on (is blocked by) depends-on.\n\nralph-tui will:\n- Show blocked beads as \"blocked\" until dependencies complete\n- Never select a bead for execution while its dependencies are open\n- Include dependency context in the prompt when working on a bead\n\n**Correct dependency order:**\n1. Schema\u002Fdatabase changes (no dependencies)\n2. Backend logic (depends on schema)\n3. UI components (depends on backend)\n4. Integration\u002Fpolish (depends on UI)\n\n---\n\n## Acceptance Criteria: Quality Gates + Story-Specific\n\nEach bead's description should include acceptance criteria with:\n1. **Story-specific criteria** from the PRD (what this story accomplishes)\n2. **Quality gates** from the PRD's Quality Gates section (appended at the end)\n\n### Good criteria (verifiable):\n- \"Add `investorType` column to investor table with default 'cold'\"\n- \"Filter dropdown has options: All, Cold, Friend\"\n- \"Clicking toggle shows confirmation dialog\"\n\n### Bad criteria (vague):\n- ❌ \"Works correctly\"\n- ❌ \"User can do X easily\"\n- ❌ \"Good UX\"\n- ❌ \"Handles edge cases\"\n\n---\n\n## Conversion Rules\n\n1. **Extract Quality Gates** from PRD first\n2. **Each user story → one bead**\n3. **First story**: No dependencies (creates foundation)\n4. **Subsequent stories**: Depend on their predecessors (UI depends on backend, etc.)\n5. **Priority**: Based on dependency order, then document order (0=critical, 2=medium, 4=backlog)\n6. **All stories**: `status: \"open\"`\n7. **Acceptance criteria**: Story criteria + quality gates appended\n8. **UI stories**: Also append UI-specific gates (browser verification)\n\n---\n\n## Splitting Large PRDs\n\nIf a PRD has big features, split them:\n\n**Original:**\n> \"Add friends outreach track with different messaging\"\n\n**Split into:**\n1. US-001: Add investorType field to database\n2. US-002: Add type toggle to investor list UI\n3. US-003: Create friend-specific phase progression logic\n4. US-004: Create friend message templates\n5. US-005: Wire up task generation for friends\n6. US-006: Add filter by type\n7. US-007: Update new investor form\n8. US-008: Update dashboard counts\n\nEach is one focused change that can be completed and verified independently.\n\n---\n\n## Example\n\n**Input PRD:**\n```markdown\n# PRD: Friends Outreach\n\nAdd ability to mark investors as \"friends\" for warm outreach.\n\n## Quality Gates\n\nThese commands must pass for every user story:\n- `pnpm typecheck` - Type checking\n- `pnpm lint` - Linting\n\nFor UI stories, also include:\n- Verify in browser using dev-browser skill\n\n## User Stories\n\n### US-001: Add investorType field to investor table\n**Description:** As a developer, I need to categorize investors as 'cold' or 'friend'.\n\n**Acceptance Criteria:**\n- [ ] Add investorType column: 'cold' | 'friend' (default 'cold')\n- [ ] Generate and run migration successfully\n\n### US-002: Add type toggle to investor list rows\n**Description:** As Ryan, I want to toggle investor type directly from the list.\n\n**Acceptance Criteria:**\n- [ ] Each row has Cold | Friend toggle\n- [ ] Switching shows confirmation dialog\n- [ ] On confirm: updates type in database\n\n### US-003: Filter investors by type\n**Description:** As Ryan, I want to filter the list to see just friends or cold.\n\n**Acceptance Criteria:**\n- [ ] Filter dropdown: All | Cold | Friend\n- [ ] Filter persists in URL params\n```\n\n**Output beads:**\n```bash\n# Create epic (link back to source PRD)\nbd create --type=epic \\\n  --title=\"Friends Outreach Track\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nWarm outreach for deck feedback\nEOF\n)\" \\\n  --external-ref=\"prd:.\u002Ftasks\u002Ffriends-outreach-prd.md\"\n\n# US-001: No deps (first - creates schema)\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-001: Add investorType field to investor table\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs a developer, I need to categorize investors as 'cold' or 'friend'.\n\n## Acceptance Criteria\n- [ ] Add investorType column: 'cold' | 'friend' (default 'cold')\n- [ ] Generate and run migration successfully\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\nEOF\n)\" \\\n  --priority=1\n\n# US-002: UI story (gets browser verification too)\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-002: Add type toggle to investor list rows\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs Ryan, I want to toggle investor type directly from the list.\n\n## Acceptance Criteria\n- [ ] Each row has Cold | Friend toggle\n- [ ] Switching shows confirmation dialog\n- [ ] On confirm: updates type in database\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\n- [ ] Verify in browser using dev-browser skill\nEOF\n)\" \\\n  --priority=2\n\n# Add dependency: US-002 depends on US-001\nbd dep add ralph-tui-002 ralph-tui-001\n\n# US-003: UI story\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-003: Filter investors by type\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs Ryan, I want to filter the list to see just friends or cold.\n\n## Acceptance Criteria\n- [ ] Filter dropdown: All | Cold | Friend\n- [ ] Filter persists in URL params\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\n- [ ] Verify in browser using dev-browser skill\nEOF\n)\" \\\n  --priority=3\n\n# Add dependency: US-003 depends on US-002\nbd dep add ralph-tui-003 ralph-tui-002\n```\n\n---\n\n## Output Location\n\nBeads are written to: `.beads\u002Fbeads.jsonl`\n\nAfter creation, run ralph-tui:\n```bash\n# Work on a specific epic\nralph-tui run --tracker beads --epic ralph-tui-abc\n\n# Or let it pick the best task automatically\nralph-tui run --tracker beads\n```\n\nralph-tui will:\n1. Work on beads within the specified epic (or select the best available task)\n2. Close each bead when complete\n3. Close the epic when all children are done\n4. Output `\u003Cpromise>COMPLETE\u003C\u002Fpromise>` when epic is done\n\n---\n\n## Checklist Before Creating Beads\n\n- [ ] Extracted Quality Gates from PRD (or asked user if missing)\n- [ ] Each story is completable in one iteration (small enough)\n- [ ] Stories are ordered by dependency (schema → backend → UI)\n- [ ] Quality gates appended to every bead's acceptance criteria\n- [ ] UI stories have browser verification (if specified in Quality Gates)\n- [ ] Acceptance criteria are verifiable (not vague)\n- [ ] No story depends on a later story (only earlier stories)\n- [ ] Dependencies added with `bd dep add` after creating beads\n","# Ralph TUI - Create Beads\n\nConverts PRDs to beads (epic + child tasks) for ralph-tui autonomous execution.\n\n> **Note:** This skill is bundled with ralph-tui's Beads tracker plugin. Future tracker plugins (Linear, GitHub Issues, etc.) will bundle their own task creation skills.\n\n---\n\n## The Job\n\nTake a PRD (markdown file or text) and create beads in `.beads\u002Fbeads.jsonl`:\n1. **Extract Quality Gates** from the PRD's \"Quality Gates\" section\n2. Create an **epic** bead for the feature\n3. Create **child beads** for each user story (with quality gates appended)\n4. Set up **dependencies** between beads (schema → backend → UI)\n5. Output ready for `ralph-tui run --tracker beads`\n\n---\n\n## Step 1: Extract Quality Gates\n\nLook for the \"Quality Gates\" section in the PRD:\n\n```markdown\n## Quality Gates\n\nThese commands must pass for every user story:\n- `pnpm typecheck` - Type checking\n- `pnpm lint` - Linting\n\nFor UI stories, also include:\n- Verify in browser using dev-browser skill\n```\n\nExtract:\n- **Universal gates:** Commands that apply to ALL stories (e.g., `pnpm typecheck`)\n- **UI gates:** Commands that apply only to UI stories (e.g., browser verification)\n\n**If no Quality Gates section exists:** Ask the user what commands should pass, or use a sensible default like `npm run typecheck`.\n\n---\n\n## Output Format\n\nBeads use `bd create` command with **HEREDOC syntax** to safely handle special characters:\n\n```bash\n# Create epic (link back to source PRD)\nbd create --type=epic \\\n  --title=\"[Feature Name]\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\n[Feature description from PRD]\nEOF\n)\" \\\n  --external-ref=\"prd:.\u002Ftasks\u002Ffeature-name-prd.md\"\n\n# Create child bead (with quality gates in acceptance criteria)\nbd create \\\n  --parent=EPIC_ID \\\n  --title=\"[Story Title]\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\n[Story description with acceptance criteria INCLUDING quality gates]\nEOF\n)\" \\\n  --priority=[1-4]\n```\n\n> **CRITICAL:** Always use `\u003C\u003C'EOF'` (single-quoted) for the HEREDOC delimiter. This prevents shell interpretation of backticks, `$variables`, and `()` in descriptions.\n\n---\n\n## Story Size: The #1 Rule\n\n**Each story must be completable in ONE ralph-tui iteration (~one agent context window).**\n\nralph-tui spawns a fresh agent instance per iteration with no memory of previous work. If a story is too big, the agent runs out of context before finishing.\n\n### Right-sized stories:\n- Add a database column + migration\n- Add a UI component to an existing page\n- Update a server action with new logic\n- Add a filter dropdown to a list\n\n### Too big (split these):\n- \"Build the entire dashboard\" → Split into: schema, queries, UI components, filters\n- \"Add authentication\" → Split into: schema, middleware, login UI, session handling\n- \"Refactor the API\" → Split into one story per endpoint or pattern\n\n**Rule of thumb:** If you can't describe the change in 2-3 sentences, it's too big.\n\n---\n\n## Story Ordering: Dependencies First\n\nStories execute in dependency order. Earlier stories must not depend on later ones.\n\n**Correct order:**\n1. Schema\u002Fdatabase changes (migrations)\n2. Server actions \u002F backend logic\n3. UI components that use the backend\n4. Dashboard\u002Fsummary views that aggregate data\n\n**Wrong order:**\n1. ❌ UI component (depends on schema that doesn't exist yet)\n2. ❌ Schema change\n\n---\n\n## Dependencies with `bd dep add`\n\nUse the `bd dep add` command to specify which beads must complete first:\n\n```bash\n# Create the beads first\nbd create --parent=epic-123 --title=\"US-001: Add schema\" ...\nbd create --parent=epic-123 --title=\"US-002: Create API\" ...\nbd create --parent=epic-123 --title=\"US-003: Build UI\" ...\n\n# Then add dependencies (issue depends-on blocker)\nbd dep add ralph-tui-002 ralph-tui-001  # US-002 depends on US-001\nbd dep add ralph-tui-003 ralph-tui-002  # US-003 depends on US-002\n```\n\n**Syntax:** `bd dep add \u003Cissue> \u003Cdepends-on>` — the issue depends on (is blocked by) depends-on.\n\nralph-tui will:\n- Show blocked beads as \"blocked\" until dependencies complete\n- Never select a bead for execution while its dependencies are open\n- Include dependency context in the prompt when working on a bead\n\n**Correct dependency order:**\n1. Schema\u002Fdatabase changes (no dependencies)\n2. Backend logic (depends on schema)\n3. UI components (depends on backend)\n4. Integration\u002Fpolish (depends on UI)\n\n---\n\n## Acceptance Criteria: Quality Gates + Story-Specific\n\nEach bead's description should include acceptance criteria with:\n1. **Story-specific criteria** from the PRD (what this story accomplishes)\n2. **Quality gates** from the PRD's Quality Gates section (appended at the end)\n\n### Good criteria (verifiable):\n- \"Add `investorType` column to investor table with default 'cold'\"\n- \"Filter dropdown has options: All, Cold, Friend\"\n- \"Clicking toggle shows confirmation dialog\"\n\n### Bad criteria (vague):\n- ❌ \"Works correctly\"\n- ❌ \"User can do X easily\"\n- ❌ \"Good UX\"\n- ❌ \"Handles edge cases\"\n\n---\n\n## Conversion Rules\n\n1. **Extract Quality Gates** from PRD first\n2. **Each user story → one bead**\n3. **First story**: No dependencies (creates foundation)\n4. **Subsequent stories**: Depend on their predecessors (UI depends on backend, etc.)\n5. **Priority**: Based on dependency order, then document order (0=critical, 2=medium, 4=backlog)\n6. **All stories**: `status: \"open\"`\n7. **Acceptance criteria**: Story criteria + quality gates appended\n8. **UI stories**: Also append UI-specific gates (browser verification)\n\n---\n\n## Splitting Large PRDs\n\nIf a PRD has big features, split them:\n\n**Original:**\n> \"Add friends outreach track with different messaging\"\n\n**Split into:**\n1. US-001: Add investorType field to database\n2. US-002: Add type toggle to investor list UI\n3. US-003: Create friend-specific phase progression logic\n4. US-004: Create friend message templates\n5. US-005: Wire up task generation for friends\n6. US-006: Add filter by type\n7. US-007: Update new investor form\n8. US-008: Update dashboard counts\n\nEach is one focused change that can be completed and verified independently.\n\n---\n\n## Example\n\n**Input PRD:**\n```markdown\n# PRD: Friends Outreach\n\nAdd ability to mark investors as \"friends\" for warm outreach.\n\n## Quality Gates\n\nThese commands must pass for every user story:\n- `pnpm typecheck` - Type checking\n- `pnpm lint` - Linting\n\nFor UI stories, also include:\n- Verify in browser using dev-browser skill\n\n## User Stories\n\n### US-001: Add investorType field to investor table\n**Description:** As a developer, I need to categorize investors as 'cold' or 'friend'.\n\n**Acceptance Criteria:**\n- [ ] Add investorType column: 'cold' | 'friend' (default 'cold')\n- [ ] Generate and run migration successfully\n\n### US-002: Add type toggle to investor list rows\n**Description:** As Ryan, I want to toggle investor type directly from the list.\n\n**Acceptance Criteria:**\n- [ ] Each row has Cold | Friend toggle\n- [ ] Switching shows confirmation dialog\n- [ ] On confirm: updates type in database\n\n### US-003: Filter investors by type\n**Description:** As Ryan, I want to filter the list to see just friends or cold.\n\n**Acceptance Criteria:**\n- [ ] Filter dropdown: All | Cold | Friend\n- [ ] Filter persists in URL params\n```\n\n**Output beads:**\n```bash\n# Create epic (link back to source PRD)\nbd create --type=epic \\\n  --title=\"Friends Outreach Track\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nWarm outreach for deck feedback\nEOF\n)\" \\\n  --external-ref=\"prd:.\u002Ftasks\u002Ffriends-outreach-prd.md\"\n\n# US-001: No deps (first - creates schema)\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-001: Add investorType field to investor table\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs a developer, I need to categorize investors as 'cold' or 'friend'.\n\n## Acceptance Criteria\n- [ ] Add investorType column: 'cold' | 'friend' (default 'cold')\n- [ ] Generate and run migration successfully\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\nEOF\n)\" \\\n  --priority=1\n\n# US-002: UI story (gets browser verification too)\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-002: Add type toggle to investor list rows\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs Ryan, I want to toggle investor type directly from the list.\n\n## Acceptance Criteria\n- [ ] Each row has Cold | Friend toggle\n- [ ] Switching shows confirmation dialog\n- [ ] On confirm: updates type in database\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\n- [ ] Verify in browser using dev-browser skill\nEOF\n)\" \\\n  --priority=2\n\n# Add dependency: US-002 depends on US-001\nbd dep add ralph-tui-002 ralph-tui-001\n\n# US-003: UI story\nbd create --parent=ralph-tui-abc \\\n  --title=\"US-003: Filter investors by type\" \\\n  --description=\"$(cat \u003C\u003C'EOF'\nAs Ryan, I want to filter the list to see just friends or cold.\n\n## Acceptance Criteria\n- [ ] Filter dropdown: All | Cold | Friend\n- [ ] Filter persists in URL params\n- [ ] pnpm typecheck passes\n- [ ] pnpm lint passes\n- [ ] Verify in browser using dev-browser skill\nEOF\n)\" \\\n  --priority=3\n\n# Add dependency: US-003 depends on US-002\nbd dep add ralph-tui-003 ralph-tui-002\n```\n\n---\n\n## Output Location\n\nBeads are written to: `.beads\u002Fbeads.jsonl`\n\nAfter creation, run ralph-tui:\n```bash\n# Work on a specific epic\nralph-tui run --tracker beads --epic ralph-tui-abc\n\n# Or let it pick the best task automatically\nralph-tui run --tracker beads\n```\n\nralph-tui will:\n1. Work on beads within the specified epic (or select the best available task)\n2. Close each bead when complete\n3. Close the epic when all children are done\n4. Output `\u003Cpromise>COMPLETE\u003C\u002Fpromise>` when epic is done\n\n---\n\n## Checklist Before Creating Beads\n\n- [ ] Extracted Quality Gates from PRD (or asked user if missing)\n- [ ] Each story is completable in one iteration (small enough)\n- [ ] Stories are ordered by dependency (schema → backend → UI)\n- [ ] Quality gates appended to every bead's acceptance criteria\n- [ ] UI stories have browser verification (if specified in Quality Gates)\n- [ ] Acceptance criteria are verifiable (not vague)\n- [ ] No story depends on a later story (only earlier stories)\n- [ ] Dependencies added with `bd dep add` after creating beads\n",{"name":5,"description":7},"main","e24b64bdac040ad169ed16b14853eff1b20cd726","skills_archive\u002Fralph-tui-create-beads",0,"https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates","https:\u002F\u002Fgithub.com\u002FBumpyClock","2026-11-14 03:12:06",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add BumpyClock\u002Fagent-templates --skill ralph-tui-create-beads",{"tool":37,"command":38},"bunx","bunx skills add BumpyClock\u002Fagent-templates --skill ralph-tui-create-beads",{"tool":40,"command":41},"pnpm","pnpm dlx skills add BumpyClock\u002Fagent-templates --skill ralph-tui-create-beads","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fralph-tui-create-beads\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79FEE6E257MWVEBY43X0NVN","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79FEB8GTJC6ZHDK67T40R20","workflow-from-chats","Extract preferences from agent chats → skills, rules, workflow docs. For learning preferences, mining feedback, personalizing workflows.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fworkflow-from-chats\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79FE7TMNGVZZ0M8NV4N0X6N","winui3-csharp-app","WinUI 3 \u002F Windows App SDK desktop apps in C#\u002FXAML. MVVM, bindings, navigation, Mica\u002FAcrylic, windowing, packaging, performance.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwinui3-csharp-app\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79FE31HY46BHN67CQGB7MVJ","why","Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhy\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79FE0N7MGWDG8SCD60FWTV5","what-did-i-get-done","Summarize authored commits over a user-specified time period into a concise status update.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fwhat-did-i-get-done\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79FDYBJG9QNCQC0MMVBDT80","weekly-review","Produce a short weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work.","https:\u002F\u002Fgithub.com\u002FBumpyClock\u002Fagent-templates\u002Fblob\u002Fmain\u002Fskills_archive\u002Fweekly-review\u002FSKILL.md",[],[]]