[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CQY3E3TE2KBMS4RMQSWK47":3,"skill-same:01M6CQY3E3TE2KBMS4RMQSWK47":63},{"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":27,"linkOnly":28,"markdownContent":29,"markdownBody":30,"frontMatter":31,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":14,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":37,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M6CQY3E3TE2KBMS4RMQSWK47","runbook-generator",null,"Generate operational runbooks documenting what needs to be running locally and in production for effective system testing and deployment.","dundas\u002Fagentbootup-public","dundas","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F627426?v=4","01M6CQVP2KHXEP7JH9WKKF59S7","David K. Dundas","01M6CQVP76D48NCMMXYDK9CBA8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Frunbook-generator\u002FSKILL.md",[],[19,20,21,22,23,24,25,26],"runbook","runbook generator","testing","documentation","deployment","generate","Production","system","2026-11-10 10:12:30",false,"---\nname: runbook-generator\ndescription: Generate operational runbooks documenting what needs to be running locally and in production for effective system testing and deployment.\ncategory: documentation\n---\n\n# Runbook Generator\n\n## Goal\nCreate a comprehensive operational runbook that answers \"what needs to be running\" for a system to be tested and deployed effectively, with startup checklists and smoke tests for both local and production environments.\n\n## Input Sources\n- **Codebase Analysis** - Automatically discover services, dependencies, and deployment patterns from the repository\n\n## Output\n- **Format:** Markdown (`.md`)\n- **Location:** Repository root\n- **Filename:** `RUNBOOK.md`\n\n---\n\n## Process\n\n### Phase 1: Environment & Architecture Discovery\n\n1. **Discover System Architecture**\n   Analyze the codebase to identify:\n\n   **Service Discovery:**\n   - `package.json` files and their `scripts` (start commands, dev commands)\n   - `docker-compose.yml` files (service definitions, ports, dependencies)\n   - Deployment configs (`fly.toml`, `vercel.json`, `Dockerfile`, K8s manifests)\n   - Multiple service directories (backend, frontend, worker, api, etc.)\n\n   **Dependency Discovery:**\n   - `.env.example` files (required environment variables, external services)\n   - Database configs (PostgreSQL, MongoDB, Redis, etc.)\n   - External APIs and storage backends (S3, Mech Storage, etc.)\n   - Authentication providers (OAuth, Auth0, Clerk, etc.)\n\n   **Port & Health Check Discovery:**\n   - Service ports from configs\n   - Health check endpoints (`\u002Fhealth`, `\u002Fstatus`, `\u002Fping`)\n   - API base URLs\n\n   **Runtime Discovery:**\n   - CLI tools or daemons that must run (background workers, polling agents)\n   - Hook systems or integrations\n   - Build\u002Fbundle requirements\n\n2. **GATE: Environment Strategy**\n   Ask the user:\n   ```\n   Which environments does this system have?\n   a) Local\u002FDevelopment only\n   b) Local + Staging\n   c) Local + Production\n   d) Local + Staging + Production\n\n   Where are production secrets stored?\n   (e.g., 1Password, AWS Secrets Manager, Fly.io secrets, Vercel env vars, etc.)\n   ```\n\n3. **Ask About Testing Scope**\n   ```\n   What level of local testing should the runbook support?\n   a) Minimum (just the core services, no external dependencies)\n   b) Full local stack (all services + external deps or local stubs)\n   c) Hybrid (local services + remote staging dependencies)\n   ```\n\n### Phase 2: Runbook Generation\n\n4. **Generate \"System Pieces\" Section**\n   Document the system architecture:\n   ```markdown\n   ## System Pieces (What Talks To What)\n\n   **Runs on developer machine:**\n   - [CLI tool name] (what it does)\n   - [Background daemon] (what it polls\u002Fmonitors)\n   - [Hook system] (what it intercepts)\n\n   **Runs as services:**\n   - [Service 1] (`path\u002F`) - what it does, what it exposes\n   - [Service 2] (`path\u002F`) - what it does, dependencies\n\n   **External dependencies:**\n   - [Database\u002FStorage] - why it's needed\n   - [Third-party API] - what features depend on it\n   ```\n\n5. **Generate \"Local Testing\" Section**\n\n   **Minimum Requirements:**\n   ```markdown\n   ## Local Testing (What Must Be Running)\n\n   ### Minimum to test \"[core functionality]\"\n   1. **[Service 1] running locally** on `http:\u002F\u002Flocalhost:XXXX`\n   2. **[Service 2] running locally** on `http:\u002F\u002Flocalhost:YYYY`\n\n   Docs:\n   - [Link to relevant local dev guide with line number]\n   ```\n\n   **Full Local E2E:**\n   ```markdown\n   ### Full local end-to-end (closest to real usage)\n   In addition to the minimum above:\n   3. **[Daemon\u002FCLI] running** (`command to start`)\n   4. **[Hook system] enabled** (`command to enable`)\n   5. **[Dependencies]** (database seeded, external service configured)\n\n   Environment variables required:\n   - `VAR_NAME` (example value, what it controls)\n   - `API_KEY` (where to get it)\n   ```\n\n   **Local Bring-Up Checklist:**\n   ```markdown\n   ### Local bring-up checklist\n\n   **1) Configure environment**\n   - Copy `.env.example` → `.env` and fill required values\n   - Required vars: [list critical ones]\n\n   **2) Start [Service 1]**\n   - From repo root: `bun run dev:service1`\n   - Or directly: `cd service1 && npm run dev`\n   - Or via Docker: `docker-compose up service1`\n\n   **3) Start [Service 2]**\n   - [Commands...]\n\n   **4) Smoke checks**\n   - Service 1 health: `curl http:\u002F\u002Flocalhost:3000\u002Fhealth`\n   - Service 2 loads: open `http:\u002F\u002Flocalhost:5173`\n   - [Other verification commands]\n   ```\n\n6. **Generate \"Production Testing\" Section**\n\n   **Minimum Production Deployment:**\n   ```markdown\n   ## Production Testing (What Must Be Running)\n\n   ### Minimum production deployment\n   - **[Service 1] deployed** (platform name)\n   - **[Service 2] deployed** (platform name)\n   - **[Database\u002FStorage] configured** (provider name)\n   - **Production secrets configured** (list critical secrets)\n\n   Docs:\n   - Deployment guide: `DEPLOYMENT_GUIDE.md:1`\n   - Production setup: `path\u002FPRODUCTION_SETUP.md:1`\n   ```\n\n   **Production Smoke Test Checklist:**\n   ```markdown\n   ### Production smoke test checklist\n   1. Service 1 is up: `GET \u002Fhealth` returns 200\n   2. Service 2 is up: homepage loads\n   3. Authentication works: login flow completes\n   4. API key creation works: can generate keys in UI\n   5. Core flow works end-to-end:\n      - [Step 1]\n      - [Step 2]\n      - [Step 3]\n      - Confirm expected outcome\n\n   Automated test scripts:\n   - `path\u002Fto\u002Ftest-script.sh` (what it tests)\n   ```\n\n7. **Generate \"Notes \u002F Common Gotchas\" Section**\n   Document common failure modes discovered during analysis:\n   ```markdown\n   ## Notes \u002F Common Gotchas\n\n   - If [Service] can't talk to [Dependency] (bad creds\u002Fnetwork), [what breaks]\n   - If testing [feature] across [architecture detail], [config vars] need to match [topology]\n   - Port conflicts: If you see [error], check if [service] is already running\n   - Missing dependencies: [Service] requires [dependency] to be installed\n   - Environment mismatches: [Common mistake and how to fix it]\n   ```\n\n### Phase 3: Review & Save\n\n8. **Present Draft for Review**\n   Show the generated runbook to the user before saving:\n   ```\n   I've generated a runbook with the following sections:\n   - System architecture (X services, Y dependencies)\n   - Local testing requirements (minimum + full E2E)\n   - Production deployment requirements\n   - Startup checklists with copy-pasteable commands\n   - Smoke test verification steps\n   - Common gotchas\n\n   Would you like me to save this to RUNBOOK.md?\n   ```\n\n9. **Save Runbook**\n   Save to `RUNBOOK.md` at repository root\n\n10. **Summarize Next Steps**\n    ```\n    Runbook created at RUNBOOK.md:1\n\n    To use this runbook:\n    - For local development: Follow \"Local Testing\" section\n    - For deployment: Follow \"Production Testing\" section\n    - For troubleshooting: Check \"Common Gotchas\" section\n\n    To update this runbook when infrastructure changes:\n    - Re-run this skill to regenerate\n    - Or manually edit RUNBOOK.md\n    ```\n\n---\n\n## Output Format Template\n\nThe generated `RUNBOOK.md` should follow this structure:\n\n```markdown\n# [Project Name] Runbook (Local + Production)\n\nThis runbook answers: \"what needs to be running\" for [Project] to be tested effectively.\n\n## System Pieces (What Talks To What)\n\n**Runs on the developer machine**\n- [List CLI tools, daemons, hooks]\n\n**Runs as services**\n- [List backend services, frontends, APIs]\n\n**External dependencies**\n- [List databases, storage, third-party APIs]\n\n## Local Testing (What Must Be Running)\n\n### Minimum to test \"[core functionality]\"\n[Numbered list with ports and docs references]\n\n### Full local end-to-end (closest to real usage)\n[Additional requirements beyond minimum]\n\n### Local bring-up checklist\n**1) Configure [thing]**\n[Copy-pasteable commands]\n\n**2) Start [service]**\n[Copy-pasteable commands]\n\n**3) Smoke checks**\n[Verification curl commands]\n\n## Production Testing (What Must Be Running)\n\n### Minimum production deployment\n[List deployed services, dependencies, secrets]\n\n### Production smoke test checklist\n[Numbered verification steps with expected outcomes]\n\n## Notes \u002F Common Gotchas\n\n[Bulleted list of common failure modes and solutions]\n```\n\n---\n\n## Interaction Model\n\n- **Automated Discovery:** Scan codebase for services\u002Fdependencies\u002Fconfigs\n- **User Confirmation:** Ask about environment strategy and testing scope\n- **Draft Review:** Present runbook before saving\n- **Iterative:** Update based on user corrections\n\n---\n\n## Target Audience\n\nThe runbook should be usable by:\n- A new developer joining the project (onboarding)\n- An AI agent setting up the development environment\n- An SRE deploying to production\n- A QA engineer validating deployment health\n\n---\n\n## Key Principles\n\n1. **Discovery over Assumptions** - Scan actual configs, don't guess structure\n2. **Copy-Pasteable Commands** - Every command should work as-is\n3. **Environment-Aware** - Different requirements for local vs production\n4. **Smoke Tests Included** - Verification steps for each service\n5. **Reference Existing Docs** - Link to deeper guides with line numbers (e.g., `README.md:42`)\n\n---\n\n## Integration with Other Skills\n\n- **After deployment changes:** Re-run runbook-generator to update RUNBOOK.md\n- **Before test-plan-generator:** Use RUNBOOK.md to understand prerequisites\n- **After prd-writer:** May need runbook updates if new services are added\n","# Runbook Generator\n\n## Goal\nCreate a comprehensive operational runbook that answers \"what needs to be running\" for a system to be tested and deployed effectively, with startup checklists and smoke tests for both local and production environments.\n\n## Input Sources\n- **Codebase Analysis** - Automatically discover services, dependencies, and deployment patterns from the repository\n\n## Output\n- **Format:** Markdown (`.md`)\n- **Location:** Repository root\n- **Filename:** `RUNBOOK.md`\n\n---\n\n## Process\n\n### Phase 1: Environment & Architecture Discovery\n\n1. **Discover System Architecture**\n   Analyze the codebase to identify:\n\n   **Service Discovery:**\n   - `package.json` files and their `scripts` (start commands, dev commands)\n   - `docker-compose.yml` files (service definitions, ports, dependencies)\n   - Deployment configs (`fly.toml`, `vercel.json`, `Dockerfile`, K8s manifests)\n   - Multiple service directories (backend, frontend, worker, api, etc.)\n\n   **Dependency Discovery:**\n   - `.env.example` files (required environment variables, external services)\n   - Database configs (PostgreSQL, MongoDB, Redis, etc.)\n   - External APIs and storage backends (S3, Mech Storage, etc.)\n   - Authentication providers (OAuth, Auth0, Clerk, etc.)\n\n   **Port & Health Check Discovery:**\n   - Service ports from configs\n   - Health check endpoints (`\u002Fhealth`, `\u002Fstatus`, `\u002Fping`)\n   - API base URLs\n\n   **Runtime Discovery:**\n   - CLI tools or daemons that must run (background workers, polling agents)\n   - Hook systems or integrations\n   - Build\u002Fbundle requirements\n\n2. **GATE: Environment Strategy**\n   Ask the user:\n   ```\n   Which environments does this system have?\n   a) Local\u002FDevelopment only\n   b) Local + Staging\n   c) Local + Production\n   d) Local + Staging + Production\n\n   Where are production secrets stored?\n   (e.g., 1Password, AWS Secrets Manager, Fly.io secrets, Vercel env vars, etc.)\n   ```\n\n3. **Ask About Testing Scope**\n   ```\n   What level of local testing should the runbook support?\n   a) Minimum (just the core services, no external dependencies)\n   b) Full local stack (all services + external deps or local stubs)\n   c) Hybrid (local services + remote staging dependencies)\n   ```\n\n### Phase 2: Runbook Generation\n\n4. **Generate \"System Pieces\" Section**\n   Document the system architecture:\n   ```markdown\n   ## System Pieces (What Talks To What)\n\n   **Runs on developer machine:**\n   - [CLI tool name] (what it does)\n   - [Background daemon] (what it polls\u002Fmonitors)\n   - [Hook system] (what it intercepts)\n\n   **Runs as services:**\n   - [Service 1] (`path\u002F`) - what it does, what it exposes\n   - [Service 2] (`path\u002F`) - what it does, dependencies\n\n   **External dependencies:**\n   - [Database\u002FStorage] - why it's needed\n   - [Third-party API] - what features depend on it\n   ```\n\n5. **Generate \"Local Testing\" Section**\n\n   **Minimum Requirements:**\n   ```markdown\n   ## Local Testing (What Must Be Running)\n\n   ### Minimum to test \"[core functionality]\"\n   1. **[Service 1] running locally** on `http:\u002F\u002Flocalhost:XXXX`\n   2. **[Service 2] running locally** on `http:\u002F\u002Flocalhost:YYYY`\n\n   Docs:\n   - [Link to relevant local dev guide with line number]\n   ```\n\n   **Full Local E2E:**\n   ```markdown\n   ### Full local end-to-end (closest to real usage)\n   In addition to the minimum above:\n   3. **[Daemon\u002FCLI] running** (`command to start`)\n   4. **[Hook system] enabled** (`command to enable`)\n   5. **[Dependencies]** (database seeded, external service configured)\n\n   Environment variables required:\n   - `VAR_NAME` (example value, what it controls)\n   - `API_KEY` (where to get it)\n   ```\n\n   **Local Bring-Up Checklist:**\n   ```markdown\n   ### Local bring-up checklist\n\n   **1) Configure environment**\n   - Copy `.env.example` → `.env` and fill required values\n   - Required vars: [list critical ones]\n\n   **2) Start [Service 1]**\n   - From repo root: `bun run dev:service1`\n   - Or directly: `cd service1 && npm run dev`\n   - Or via Docker: `docker-compose up service1`\n\n   **3) Start [Service 2]**\n   - [Commands...]\n\n   **4) Smoke checks**\n   - Service 1 health: `curl http:\u002F\u002Flocalhost:3000\u002Fhealth`\n   - Service 2 loads: open `http:\u002F\u002Flocalhost:5173`\n   - [Other verification commands]\n   ```\n\n6. **Generate \"Production Testing\" Section**\n\n   **Minimum Production Deployment:**\n   ```markdown\n   ## Production Testing (What Must Be Running)\n\n   ### Minimum production deployment\n   - **[Service 1] deployed** (platform name)\n   - **[Service 2] deployed** (platform name)\n   - **[Database\u002FStorage] configured** (provider name)\n   - **Production secrets configured** (list critical secrets)\n\n   Docs:\n   - Deployment guide: `DEPLOYMENT_GUIDE.md:1`\n   - Production setup: `path\u002FPRODUCTION_SETUP.md:1`\n   ```\n\n   **Production Smoke Test Checklist:**\n   ```markdown\n   ### Production smoke test checklist\n   1. Service 1 is up: `GET \u002Fhealth` returns 200\n   2. Service 2 is up: homepage loads\n   3. Authentication works: login flow completes\n   4. API key creation works: can generate keys in UI\n   5. Core flow works end-to-end:\n      - [Step 1]\n      - [Step 2]\n      - [Step 3]\n      - Confirm expected outcome\n\n   Automated test scripts:\n   - `path\u002Fto\u002Ftest-script.sh` (what it tests)\n   ```\n\n7. **Generate \"Notes \u002F Common Gotchas\" Section**\n   Document common failure modes discovered during analysis:\n   ```markdown\n   ## Notes \u002F Common Gotchas\n\n   - If [Service] can't talk to [Dependency] (bad creds\u002Fnetwork), [what breaks]\n   - If testing [feature] across [architecture detail], [config vars] need to match [topology]\n   - Port conflicts: If you see [error], check if [service] is already running\n   - Missing dependencies: [Service] requires [dependency] to be installed\n   - Environment mismatches: [Common mistake and how to fix it]\n   ```\n\n### Phase 3: Review & Save\n\n8. **Present Draft for Review**\n   Show the generated runbook to the user before saving:\n   ```\n   I've generated a runbook with the following sections:\n   - System architecture (X services, Y dependencies)\n   - Local testing requirements (minimum + full E2E)\n   - Production deployment requirements\n   - Startup checklists with copy-pasteable commands\n   - Smoke test verification steps\n   - Common gotchas\n\n   Would you like me to save this to RUNBOOK.md?\n   ```\n\n9. **Save Runbook**\n   Save to `RUNBOOK.md` at repository root\n\n10. **Summarize Next Steps**\n    ```\n    Runbook created at RUNBOOK.md:1\n\n    To use this runbook:\n    - For local development: Follow \"Local Testing\" section\n    - For deployment: Follow \"Production Testing\" section\n    - For troubleshooting: Check \"Common Gotchas\" section\n\n    To update this runbook when infrastructure changes:\n    - Re-run this skill to regenerate\n    - Or manually edit RUNBOOK.md\n    ```\n\n---\n\n## Output Format Template\n\nThe generated `RUNBOOK.md` should follow this structure:\n\n```markdown\n# [Project Name] Runbook (Local + Production)\n\nThis runbook answers: \"what needs to be running\" for [Project] to be tested effectively.\n\n## System Pieces (What Talks To What)\n\n**Runs on the developer machine**\n- [List CLI tools, daemons, hooks]\n\n**Runs as services**\n- [List backend services, frontends, APIs]\n\n**External dependencies**\n- [List databases, storage, third-party APIs]\n\n## Local Testing (What Must Be Running)\n\n### Minimum to test \"[core functionality]\"\n[Numbered list with ports and docs references]\n\n### Full local end-to-end (closest to real usage)\n[Additional requirements beyond minimum]\n\n### Local bring-up checklist\n**1) Configure [thing]**\n[Copy-pasteable commands]\n\n**2) Start [service]**\n[Copy-pasteable commands]\n\n**3) Smoke checks**\n[Verification curl commands]\n\n## Production Testing (What Must Be Running)\n\n### Minimum production deployment\n[List deployed services, dependencies, secrets]\n\n### Production smoke test checklist\n[Numbered verification steps with expected outcomes]\n\n## Notes \u002F Common Gotchas\n\n[Bulleted list of common failure modes and solutions]\n```\n\n---\n\n## Interaction Model\n\n- **Automated Discovery:** Scan codebase for services\u002Fdependencies\u002Fconfigs\n- **User Confirmation:** Ask about environment strategy and testing scope\n- **Draft Review:** Present runbook before saving\n- **Iterative:** Update based on user corrections\n\n---\n\n## Target Audience\n\nThe runbook should be usable by:\n- A new developer joining the project (onboarding)\n- An AI agent setting up the development environment\n- An SRE deploying to production\n- A QA engineer validating deployment health\n\n---\n\n## Key Principles\n\n1. **Discovery over Assumptions** - Scan actual configs, don't guess structure\n2. **Copy-Pasteable Commands** - Every command should work as-is\n3. **Environment-Aware** - Different requirements for local vs production\n4. **Smoke Tests Included** - Verification steps for each service\n5. **Reference Existing Docs** - Link to deeper guides with line numbers (e.g., `README.md:42`)\n\n---\n\n## Integration with Other Skills\n\n- **After deployment changes:** Re-run runbook-generator to update RUNBOOK.md\n- **Before test-plan-generator:** Use RUNBOOK.md to understand prerequisites\n- **After prd-writer:** May need runbook updates if new services are added\n",{"name":5,"category":22,"description":7},"main","47b89745588c3057f0ccd0517a2eb8967df27054","templates\u002F.claude\u002Fskills\u002Frunbook-generator","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public","https:\u002F\u002Fgithub.com\u002Fdundas","derivative.io","2026-09-02 20:12:15",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add dundas\u002Fagentbootup-public --skill runbook-generator",{"tool":45,"command":46},"bunx","bunx skills add dundas\u002Fagentbootup-public --skill runbook-generator",{"tool":48,"command":49},"pnpm","pnpm dlx skills add dundas\u002Fagentbootup-public --skill runbook-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Frunbook-generator\u002FSKILL.md",true,[53,59],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"reference.md","REFERENCE","参考文档",10680,"https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Frunbook-generator\u002Freference.md",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"skill-bundle-manifest.json",1027,"https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Frunbook-generator\u002Fskill-bundle-manifest.json",[64,78,96,115,124,146],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":75,"publishedAt":27},"01M6CQZ7DFJB965BJJ5ZZ54CXY","fixture-skill","Secret-free recovery fixture skill.","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftests\u002Fruntime-adapters\u002Ffixtures\u002Fhermes\u002F0.18.2-darwin-arm64-real\u002Froot\u002Fskills\u002Ffixture-skill\u002FSKILL.md",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[76,77],"fixture skill","recovery",{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":27},"01M6CQZ4NN0KVH1Z4E1Y1GJ3X9","user-story-generator","Generate standalone user stories for features without creating a full PRD. Perfect for backlog grooming and story refinement.","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Fuser-story-generator\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[90,91,92,93,94,22,24,95],"user story generator","Story","user story","user","prd","backlog",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":108,"publishedAt":27},"01M6CQZ16VC27HMWM31CCKK6BC","user-journey-mapper","Map user flows and journeys through your application for UX design and workflow visualization, independent of testing.","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Fuser-journey-mapper\u002FSKILL.md",[102,105],{"categoryNo":103,"categoryName":104,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":106,"categoryName":107,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000032","设计师",[109,110,93,22,111,112,113,114,21],"user journey mapper","journey","ux","visualization","workflow","design",{"skillNo":116,"name":117,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":27},"01M6CQYXSQQJ4Z5CRAX2SSMHW1","transcript-query","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Ftranscript-query\u002FSKILL.md",[],[121,122,123],"transcript","transcript query","query",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":134,"publishedAt":27},"01M6CQYT7A1G4CPQTZKXR5TCK9","test-plan-generator","Generate comprehensive E2E test plans from PRDs, task lists, or descriptions with environment-aware prerequisites and issue tracking.","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Ftest-plan-generator\u002FSKILL.md",[130,131],{"categoryNo":103,"categoryName":104,"taxonomyType":73,"taxonomyTypeDesc":74},{"categoryNo":132,"categoryName":133,"taxonomyType":73,"taxonomyTypeDesc":74},"01JBSEEDCAT000000000000010","后端与接口",[135,136,137,138,139,140,141,142,143,144,24,145],"plan","test plan generator","test plan","test","task","issue","e2e test","environment","tracking","quality","e2e",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":27},"01M6CQYQAWFSPTYE2VTJJVW72G","tasklist-generator","Generate high-level tasks and gated sub-tasks from a PRD, with agent assignments, commit\u002FPR strategy, and relevant files.","https:\u002F\u002Fgithub.com\u002Fdundas\u002Fagentbootup-public\u002Fblob\u002Fmain\u002Ftemplates\u002F.claude\u002Fskills\u002Ftasklist-generator\u002FSKILL.md",[152],{"categoryNo":71,"categoryName":72,"taxonomyType":73,"taxonomyTypeDesc":74},[154,155,156,157,94,24,158,159,160,113],"tasklist generator","gated","files","strategy","tasks","pr","commit"]