[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CX2SM6AXH9YRTDC4JCZB8H":3,"skill-same:01M6CX2SM6AXH9YRTDC4JCZB8H":98},{"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":23,"publishedAt":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":36,"commitSha":37,"skillDirectory":38,"forksCount":39,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":42,"ownerDescription":43,"updatedAt":44,"install":45,"resources":57},"01M6CX2SM6AXH9YRTDC4JCZB8H","dot-ai-prd-start",null,"Start working on a PRD implementation","vfarcic\u002Fdot-ai-headlamp","vfarcic","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F5716227?v=4","01M6C41XBA7GK0NJG2D4GV11SC","Viktor Farcic","01M6CX1QQ81N9D052KA5HJE8YS",3,"MIT","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-prd-start\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29],"start","prd","dot","dot ai prd start","dot ai","implementation","2026-11-10 10:12:30",false,"---\nname: dot-ai-prd-start\ndescription: Start working on a PRD implementation\nuser-invocable: true\n---\n\n# PRD Start - Begin Implementation Work\n\n## Instructions\n\nYou are helping initiate active implementation work on a specific Product Requirements Document (PRD). This command sets up the implementation context (validates readiness, creates branch, prepares environment) then hands off to `\u002Fprd-next` for task identification.\n\n**IMPORTANT**: Do NOT include time estimates or effort estimates in your responses. Focus on setup and readiness without speculating on duration.\n\n## Process Overview\n\n1. **Select Target PRD** - Identify which PRD to implement\n2. **Validate PRD Readiness** - Ensure the PRD is ready for implementation\n3. **Set Up Implementation Context** - Create branch and prepare environment\n4. **Hand Off to prd-next** - Delegate task identification to the appropriate prompt\n\n## Step 0: Check for PRD Argument\n\n**If `prdNumber` argument is provided ({{prdNumber}}):**\n- Skip context check and auto-detection\n- Use PRD #{{prdNumber}} directly\n- Proceed to Step 2 (PRD Readiness Validation)\n\n**If `prdNumber` argument is NOT provided:**\n- Continue to context awareness check below\n\n## Step 0b: Context Awareness Check\n\n**Check if PRD context is already clear from recent conversation:**\n\n**Skip detection if recent conversation shows:**\n- **Recent PRD work discussed** - \"We just worked on PRD 29\", \"Just completed PRD update\", etc.\n- **Specific PRD mentioned** - \"PRD #X\", \"MCP Prompts PRD\", etc.\n- **PRD-specific commands used** - Recent use of `\u002Fprd-update-progress`, `\u002Fprd-start` with specific PRD\n- **Clear work context** - Discussion of specific features, tasks, or requirements for a known PRD\n\n**If context is clear:**\n- Skip to Step 2 (PRD Readiness Validation) using the known PRD\n\n**If context is unclear:**\n- Continue to Step 1 (PRD Detection)\n\n## Step 1: Smart PRD Detection (Only if Context Unclear)\n\n**Auto-detect the target PRD using these context clues (in priority order):**\n\n1. **Git Branch Analysis** - Check current branch name for PRD patterns:\n   - `feature\u002Fprd-12-*` → PRD 12\n   - `prd-13-*` → PRD 13\n   - `feature\u002Fprd-*` → Extract PRD number\n\n2. **Recent Git Commits** - Look at recent commit messages for PRD references:\n   - \"fix: PRD 12 documentation\" → PRD 12\n   - \"feat: implement prd-13 features\" → PRD 13\n\n3. **Git Status Analysis** - Check modified\u002Fstaged files for PRD clues:\n   - Modified `prds\u002F12-*.md` → PRD 12\n   - Changes in feature-specific directories\n\n4. **Available PRDs Discovery** - List all PRDs in `prds\u002F` directory\n\n5. **Fallback to User Choice** - Only if context detection fails, ask user to specify\n\n**Detection Logic:**\n- **High Confidence**: Branch name matches PRD pattern (e.g., `feature\u002Fprd-12-documentation-testing`)\n- **Medium Confidence**: Modified PRD files in git status or recent commits mention PRD\n- **Low Confidence**: Multiple PRDs available, use heuristics (most recent, largest)\n- **No Context**: Present available options to user\n\n**If context detection fails, ask the user:**\n\n```markdown\n## Which PRD would you like to start implementing?\n\nPlease provide the PRD number (e.g., \"12\", \"PRD 12\", or \"36\").\n\n**Not sure which PRD to work on?**\nExecute `dot-ai:prds-get` prompt to see all available PRDs organized by priority and readiness.\n\n**Your choice**: [Wait for user input]\n```\n\n**Once PRD is identified:**\n- Read the PRD file from `prds\u002F[issue-id]-[feature-name].md`\n\n## Step 2: PRD Readiness Validation\n\nBefore starting implementation, validate that the PRD is ready:\n\n### Requirements Validation\n- **Functional Requirements**: Are core requirements clearly defined and complete?\n- **Success Criteria**: Are measurable success criteria established?\n- **Dependencies**: Are all external dependencies identified and available?\n- **Risk Assessment**: Have major risks been identified and mitigation plans created?\n\n### Documentation Analysis\nFor documentation-first PRDs:\n- **Specification completeness**: Is the feature fully documented with user workflows?\n- **Integration points**: Are connections with existing features documented?\n- **API\u002FInterface definitions**: Are all interfaces and data structures specified?\n- **Examples and usage**: Are concrete usage examples provided?\n\n### Implementation Readiness Checklist\n```markdown\n## PRD Readiness Check\n- [ ] All functional requirements defined\n- [ ] Success criteria measurable\n- [ ] Dependencies available\n- [ ] Documentation complete\n- [ ] Integration points clear\n- [ ] Implementation approach decided\n```\n\n**If PRD is not ready:** Inform the user what's missing and suggest they complete PRD planning first.\n\n## Step 3: Implementation Context Setup\n\n**⚠️ MANDATORY: Complete this step BEFORE proceeding to Step 4**\n\n### Issue Assignment\n\n**Assign the GitHub issue to yourself to signal that work is in progress:**\n\n```bash\ngh issue edit [issue-id] --add-assignee @me\n```\n\nThis prevents others from picking up the same PRD and working on it in parallel.\n\n### Git Branch Management\n\n1. **Check current branch**: Run `git branch --show-current`\n2. **If on `main` or `master`**: Create and switch to feature branch:\n   ```bash\n   git checkout -b feature\u002Fprd-[issue-id]-[feature-name]\n   ```\n3. **If already on a feature branch**: Verify it's the correct branch for this PRD\n\n### Development Environment Setup\n- **Dependencies**: Install any new dependencies required by the PRD\n- **Configuration**: Set up any configuration needed for development\n- **Test data**: Prepare test data or mock services\n\n### Step 3 Checkpoint (REQUIRED)\n\n**You MUST display this confirmation before proceeding to Step 4:**\n\n```markdown\n## Environment Setup ✅\n- **Assignee**: @[username] ✅\n- **Branch**: `[current-branch-name]` ✅\n- **Status**: [Created new branch \u002F Already on correct branch \u002F Staying on main (reason)]\n```\n\n**DO NOT proceed to Step 4 until branch setup is confirmed.**\n\n## Step 4: Hand Off to prd-next\n\nOnce the implementation context is set up, present this message to the user:\n\n```markdown\n## Ready for Implementation ?\n\n**PRD**: [PRD Name] (#[PRD Number])\n**Assignee**: @[username]\n**Branch**: `[branch-name]`\n**Status**: Ready for development\n\n---\n\nTo identify and start working on your first task, run `\u002Fprd-next`.\n```\n\n**⚠️ STOP HERE - DO NOT:**\n- Identify or recommend tasks to work on\n- Analyze implementation priorities or critical paths\n- Start any implementation work\n- Continue beyond presenting the handoff message\n\n`\u002Fprd-next` handles all task identification and implementation guidance.\n\n## Success Criteria\n\nThis command should:\n- ✅ Successfully identify the target PRD for implementation\n- ✅ Validate that the PRD is ready for development work\n- ✅ Assign the GitHub issue to the current user to prevent duplicate work\n- ✅ Set up proper implementation context (branch, environment)\n- ✅ Hand off to `\u002Fprd-next` for task identification\n- ✅ Bridge the gap between PRD planning and development setup\n\n## Notes\n\n- This command focuses on **setup only** - it validates readiness, creates the branch, and prepares the environment\n- Once setup is complete, `\u002Fprd-next` handles all task identification, implementation guidance, and progress tracking\n\n","# PRD Start - Begin Implementation Work\n\n## Instructions\n\nYou are helping initiate active implementation work on a specific Product Requirements Document (PRD). This command sets up the implementation context (validates readiness, creates branch, prepares environment) then hands off to `\u002Fprd-next` for task identification.\n\n**IMPORTANT**: Do NOT include time estimates or effort estimates in your responses. Focus on setup and readiness without speculating on duration.\n\n## Process Overview\n\n1. **Select Target PRD** - Identify which PRD to implement\n2. **Validate PRD Readiness** - Ensure the PRD is ready for implementation\n3. **Set Up Implementation Context** - Create branch and prepare environment\n4. **Hand Off to prd-next** - Delegate task identification to the appropriate prompt\n\n## Step 0: Check for PRD Argument\n\n**If `prdNumber` argument is provided ({{prdNumber}}):**\n- Skip context check and auto-detection\n- Use PRD #{{prdNumber}} directly\n- Proceed to Step 2 (PRD Readiness Validation)\n\n**If `prdNumber` argument is NOT provided:**\n- Continue to context awareness check below\n\n## Step 0b: Context Awareness Check\n\n**Check if PRD context is already clear from recent conversation:**\n\n**Skip detection if recent conversation shows:**\n- **Recent PRD work discussed** - \"We just worked on PRD 29\", \"Just completed PRD update\", etc.\n- **Specific PRD mentioned** - \"PRD #X\", \"MCP Prompts PRD\", etc.\n- **PRD-specific commands used** - Recent use of `\u002Fprd-update-progress`, `\u002Fprd-start` with specific PRD\n- **Clear work context** - Discussion of specific features, tasks, or requirements for a known PRD\n\n**If context is clear:**\n- Skip to Step 2 (PRD Readiness Validation) using the known PRD\n\n**If context is unclear:**\n- Continue to Step 1 (PRD Detection)\n\n## Step 1: Smart PRD Detection (Only if Context Unclear)\n\n**Auto-detect the target PRD using these context clues (in priority order):**\n\n1. **Git Branch Analysis** - Check current branch name for PRD patterns:\n   - `feature\u002Fprd-12-*` → PRD 12\n   - `prd-13-*` → PRD 13\n   - `feature\u002Fprd-*` → Extract PRD number\n\n2. **Recent Git Commits** - Look at recent commit messages for PRD references:\n   - \"fix: PRD 12 documentation\" → PRD 12\n   - \"feat: implement prd-13 features\" → PRD 13\n\n3. **Git Status Analysis** - Check modified\u002Fstaged files for PRD clues:\n   - Modified `prds\u002F12-*.md` → PRD 12\n   - Changes in feature-specific directories\n\n4. **Available PRDs Discovery** - List all PRDs in `prds\u002F` directory\n\n5. **Fallback to User Choice** - Only if context detection fails, ask user to specify\n\n**Detection Logic:**\n- **High Confidence**: Branch name matches PRD pattern (e.g., `feature\u002Fprd-12-documentation-testing`)\n- **Medium Confidence**: Modified PRD files in git status or recent commits mention PRD\n- **Low Confidence**: Multiple PRDs available, use heuristics (most recent, largest)\n- **No Context**: Present available options to user\n\n**If context detection fails, ask the user:**\n\n```markdown\n## Which PRD would you like to start implementing?\n\nPlease provide the PRD number (e.g., \"12\", \"PRD 12\", or \"36\").\n\n**Not sure which PRD to work on?**\nExecute `dot-ai:prds-get` prompt to see all available PRDs organized by priority and readiness.\n\n**Your choice**: [Wait for user input]\n```\n\n**Once PRD is identified:**\n- Read the PRD file from `prds\u002F[issue-id]-[feature-name].md`\n\n## Step 2: PRD Readiness Validation\n\nBefore starting implementation, validate that the PRD is ready:\n\n### Requirements Validation\n- **Functional Requirements**: Are core requirements clearly defined and complete?\n- **Success Criteria**: Are measurable success criteria established?\n- **Dependencies**: Are all external dependencies identified and available?\n- **Risk Assessment**: Have major risks been identified and mitigation plans created?\n\n### Documentation Analysis\nFor documentation-first PRDs:\n- **Specification completeness**: Is the feature fully documented with user workflows?\n- **Integration points**: Are connections with existing features documented?\n- **API\u002FInterface definitions**: Are all interfaces and data structures specified?\n- **Examples and usage**: Are concrete usage examples provided?\n\n### Implementation Readiness Checklist\n```markdown\n## PRD Readiness Check\n- [ ] All functional requirements defined\n- [ ] Success criteria measurable\n- [ ] Dependencies available\n- [ ] Documentation complete\n- [ ] Integration points clear\n- [ ] Implementation approach decided\n```\n\n**If PRD is not ready:** Inform the user what's missing and suggest they complete PRD planning first.\n\n## Step 3: Implementation Context Setup\n\n**⚠️ MANDATORY: Complete this step BEFORE proceeding to Step 4**\n\n### Issue Assignment\n\n**Assign the GitHub issue to yourself to signal that work is in progress:**\n\n```bash\ngh issue edit [issue-id] --add-assignee @me\n```\n\nThis prevents others from picking up the same PRD and working on it in parallel.\n\n### Git Branch Management\n\n1. **Check current branch**: Run `git branch --show-current`\n2. **If on `main` or `master`**: Create and switch to feature branch:\n   ```bash\n   git checkout -b feature\u002Fprd-[issue-id]-[feature-name]\n   ```\n3. **If already on a feature branch**: Verify it's the correct branch for this PRD\n\n### Development Environment Setup\n- **Dependencies**: Install any new dependencies required by the PRD\n- **Configuration**: Set up any configuration needed for development\n- **Test data**: Prepare test data or mock services\n\n### Step 3 Checkpoint (REQUIRED)\n\n**You MUST display this confirmation before proceeding to Step 4:**\n\n```markdown\n## Environment Setup ✅\n- **Assignee**: @[username] ✅\n- **Branch**: `[current-branch-name]` ✅\n- **Status**: [Created new branch \u002F Already on correct branch \u002F Staying on main (reason)]\n```\n\n**DO NOT proceed to Step 4 until branch setup is confirmed.**\n\n## Step 4: Hand Off to prd-next\n\nOnce the implementation context is set up, present this message to the user:\n\n```markdown\n## Ready for Implementation ?\n\n**PRD**: [PRD Name] (#[PRD Number])\n**Assignee**: @[username]\n**Branch**: `[branch-name]`\n**Status**: Ready for development\n\n---\n\nTo identify and start working on your first task, run `\u002Fprd-next`.\n```\n\n**⚠️ STOP HERE - DO NOT:**\n- Identify or recommend tasks to work on\n- Analyze implementation priorities or critical paths\n- Start any implementation work\n- Continue beyond presenting the handoff message\n\n`\u002Fprd-next` handles all task identification and implementation guidance.\n\n## Success Criteria\n\nThis command should:\n- ✅ Successfully identify the target PRD for implementation\n- ✅ Validate that the PRD is ready for development work\n- ✅ Assign the GitHub issue to the current user to prevent duplicate work\n- ✅ Set up proper implementation context (branch, environment)\n- ✅ Hand off to `\u002Fprd-next` for task identification\n- ✅ Bridge the gap between PRD planning and development setup\n\n## Notes\n\n- This command focuses on **setup only** - it validates readiness, creates the branch, and prepares the environment\n- Once setup is complete, `\u002Fprd-next` handles all task identification, implementation guidance, and progress tracking\n\n",{"name":5,"description":7,"user-invocable":35},true,"main","6faa9f452f568fc9aa9b1c17ee728de11b760cb7",".claude\u002Fskills\u002Fdot-ai-prd-start",1,"https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp","https:\u002F\u002Fgithub.com\u002Fvfarcic","https:\u002F\u002Fyoutube.com\u002Fc\u002Fdevopstoolkit","Developer Advocate @Upbound","2026-06-19 10:10:13",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":35},[47,50,53],{"tool":48,"command":49},"npx","npx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-start",{"tool":51,"command":52},"bunx","bunx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-start",{"tool":54,"command":55},"pnpm","pnpm dlx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-start","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-prd-start\u002FSKILL.md",[58,64,68,74,78,82,86,90,94],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"LOCAL-SETUP.md","REFERENCE","参考文档",3056,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002FLOCAL-SETUP.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fida-mcp-cheatsheet.md",11252,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Freferences\u002Fida-mcp-cheatsheet.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002FIdaOpenHelpers.ps1","SCRIPT","脚本",956,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002FIdaOpenHelpers.ps1",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Finstall-autostart.ps1",2508,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Finstall-autostart.ps1",{"path":79,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":80,"sourceHtmlUrl":81},"scripts\u002Fopen.ps1",13100,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Fopen.ps1",{"path":83,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":84,"sourceHtmlUrl":85},"scripts\u002Frun-supervisor.py",1222,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Frun-supervisor.py",{"path":87,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":88,"sourceHtmlUrl":89},"scripts\u002Fstart-gui.ps1",3942,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Fstart-gui.ps1",{"path":91,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":92,"sourceHtmlUrl":93},"scripts\u002Fstart.ps1",18264,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Fstart.ps1",{"path":95,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":96,"sourceHtmlUrl":97},"scripts\u002Fwatchdog.ps1",2993,"https:\u002F\u002Fgithub.com\u002Fendman100\u002Fskill-router-nexus\u002Fblob\u002Fmain\u002FSecurity-and-Compliance\u002Freverse-skill-router\u002Fida-reverse\u002Fscripts\u002Fwatchdog.ps1",[99,124,142,158,172,182],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":30},"01M6CX45JYT898C3M792AXA5HS","dot-ai","Kubernetes cluster operations via dot-ai CLI - natural language cluster queries, AI-powered deployment recommendations, issue troubleshooting and remediation, Day 2 operations (scale, update, rollback, delete), resources, namespaces, events, logs, organizational knowledge base (ingest, search, query), organizational patterns\u002Fpolicies\u002Fcapabilities management, project scaffolding and repo audit, and session history and visualization. Run `dot-ai --help` for commands.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai\u002FSKILL.md",[],[26,28,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123],"visualization","delete","repo","deployment","kubernetes","capabilities","search","logs","knowledge","history","project","session","ingest","queries","natural language","query","scaffolding","knowledge base",{"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":130,"publishedAt":30},"01M6CX42HR85829TGFQ95E7283","dot-ai-write-docs","Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-write-docs\u002FSKILL.md",[],[26,131,28,132,133,134,135,136,137,138,139,140,141],"docs","write","dot ai write docs","write documentation","commands","use","documentation","examples","doc","capture","user",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":30},"01M6CX4023QEXSVV5C22GG68XW","dot-ai-worktree-prd","Create a git worktree for PRD work with a descriptive branch name. Infers PRD from context or asks user.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-worktree-prd\u002FSKILL.md",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,150,26,151,28,152,153,154,155,156,157,141],"worktree","dot ai worktree prd","create","git","git worktree","work","branch","context",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":30},"01M6CX3YETQD0A9BPXXQABX0MW","dot-ai-version","Get comprehensive system health and diagnostics","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-version\u002FSKILL.md",[],[28,165,26,166,167,168,169,170,171],"dot ai version","version","diagnostics","health","system","system health","get",{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":30},"01M6CX3X07RSJTPNSFEQRX9ACY","dot-ai-users","Manage users (create, list, delete)","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-users\u002FSKILL.md",[],[28,179,26,152,107,180,181],"dot ai users","list","manage",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":30},"01M6CX3T6YE6PVSBJGP2WSXM9J","dot-ai-tag-release","Create a release tag based on accumulated changelog fragments. Run when ready to cut a release.","https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-tag-release\u002FSKILL.md",[],[28,189,26,190,152,191,192,193],"dot ai tag release","release","run","changelog","ready"]