[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CX2P0J2S7HVBEV633VXFVP":3,"skill-same:01M6CX2P0J2S7HVBEV633VXFVP":61},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":45,"ownerDescription":46,"updatedAt":47,"install":48,"resources":60},"01M6CX2P0J2S7HVBEV633VXFVP","dot-ai-prd-next",null,"Analyze existing PRD to identify and recommend the single highest-priority task to work on next","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-next\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32],"prd","dot","dot ai prd next","dot ai","next","work on","analyze","work","task","2026-11-10 10:12:30",false,"---\nname: dot-ai-prd-next\ndescription: Analyze existing PRD to identify and recommend the single highest-priority task to work on next\nuser-invocable: true\n---\n\n# PRD Next - Work On the Next Task\n\n## Instructions\n\nYou are helping analyze an existing Product Requirements Document (PRD) to suggest the single highest-priority task to work on next, then discuss its design if the user confirms they want to work on it.\n\n## Process Overview\n\n1. **Check Context Clarity** - Determine if PRD is obvious from recent conversation\n2. **Auto-Detect Target PRD** - If context unclear, intelligently determine which PRD to analyze\n3. **Analyze Current Implementation** - Understand what's implemented vs what's missing (skip if recent context available)\n4. **Identify the Single Best Next Task** - Find the one task that should be worked on next\n5. **Present Recommendation** - Give clear rationale and wait for confirmation\n6. **Design Discussion** - If confirmed, dive into implementation design details\n7. **Implementation** - User implements the task\n8. **Update Progress** - Prompt user to run \u002Fprd-update-progress\n\n## Step 0: Context Awareness Check\n\n**FIRST: Check if PRD context is already clear from recent conversation:**\n\n**Skip detection\u002Fanalysis 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 6 (Single Task Recommendation) using the known PRD \n- Use conversation history to understand current state and recent progress\n- Proceed directly with task recommendation based on known PRD status\n\n**If context is unclear:**\n- Continue to Step 1 (PRD Detection) for full analysis\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   - `prds\u002F12-documentation-testing.md`\n   - `prds\u002F13-cicd-documentation-testing.md`\n\n5. **Fallback to User Choice** - Only if context detection fails, ask user to specify\n\n**PRD Detection Implementation:**\n```bash\n# Use these tools to gather context:\n# 1. Check git branch: gitStatus shows current branch\n# 2. Check git status: Look for modified PRD files  \n# 3. List PRDs: Use LS or Glob to find prds\u002F*.md files\n# 4. Recent commits: Use Bash 'git log --oneline -n 5' for recent context\n```\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**Example Detection Outputs:**\n```markdown\n? **Auto-detected PRD 12** (Documentation Testing)\n- Branch: `feature\u002Fprd-12-documentation-testing` ✅\n- Modified files: `prds\u002F12-documentation-testing.md` ✅\n- Recent commits mention PRD 12 features ✅\n```\n\n**Once PRD is identified:**\n- Read the PRD file from `prds\u002F[issue-id]-[feature-name].md`\n- Analyze completion status across all sections\n- Identify patterns in completed vs remaining work\n\n## Step 2: Documentation & Implementation Analysis (Only if Context Unclear)\n\nBefore assessing task priorities, analyze both the documented specifications and current implementation state:\n\n### Documentation Analysis (Documentation-First PRDs)\nFor PRDs using the documentation-first approach:\n- **Read referenced documentation**: Check the \"Content Location Map\" in PRD to find where feature specs live\n- **Understand target state**: What functionality is documented but not yet implemented\n- **Check documentation completeness**: Are all user workflows and examples fully documented\n- **Validate cross-references**: Do all documentation links and references work correctly\n\n### Code Discovery\n- **Search for related files**: Use Grep\u002FGlob to find files related to the feature\n- **Identify key modules**: Locate main implementation files mentioned in PRD\n- **Find test files**: Discover existing test coverage for the feature\n- **Check dependencies**: Review imports and module relationships\n\n### Implementation vs Documentation Gap Analysis\n- **Compare docs vs code**: What's documented vs actually implemented\n- **Partial implementations**: Identify half-finished features or TODO comments\n- **Documentation validation**: Can documented examples and commands actually work\n- **Architecture alignment**: Does current code match documented behavior and PRD architecture decisions\n- **Quality assessment**: Code style, error handling, test coverage gaps\n\n### Technical Feasibility Analysis\n- **Dependency conflicts**: Are PRD requirements compatible with existing code\n- **Breaking changes**: Will remaining tasks require refactoring existing code\n- **Integration points**: How new work connects with current implementation\n- **Technical debt**: Issues that might block or slow future work\n\n## Step 3: Completion Assessment (Only if Context Unclear)\n\n### Analyze Checkbox States\nCount and categorize all checkboxes:\n- **Completed**: `[x]` items\n- **Pending**: `[ ]` items  \n- **Deferred**: `[~]` items\n- **Blocked**: `[!]` items\n\n### Phase Analysis\nFor each implementation phase:\n- Calculate completion percentage\n- Identify bottlenecks or stalled work\n- Assess readiness to move to next phase\n\n### Requirement Coverage\nReview requirement categories:\n- **Functional Requirements**: Core feature completion\n- **Non-Functional Requirements**: Quality and performance aspects\n- **Success Criteria**: Measurable outcomes\n- **Dependencies**: External requirements\n- **Risk Mitigation**: Risk management progress\n\n## Step 4: Dependency Analysis (Only if Context Unclear)\n\n### Identify Critical Path Items\nLook for items that:\n- **Block other work** - Must be completed before others can start\n- **Enable major capabilities** - Unlock significant value when completed\n- **Resolve current blockers** - Remove impediments to progress\n\n### Dependency Patterns\n\n#### PRD-Level Dependencies\n- **Sequential dependencies** - A must be done before B\n- **Parallel opportunities** - Multiple items that can be worked simultaneously  \n- **Foundation requirements** - Core capabilities needed by multiple features\n- **Integration points** - Items that connect different parts of the system\n\n#### Code-Level Dependencies  \n- **Import dependencies** - Modules that depend on others being implemented first\n- **Interface contracts** - APIs\u002Ftypes that must be defined before consumers\n- **Database schema** - Data model changes needed before business logic\n- **Test dependencies** - Tests that require certain infrastructure or mocks\n- **Build\u002Fdeployment** - Configuration changes that affect multiple components\n\n## Step 5: Strategic Value Assessment (Only if Context Unclear)\n\n### High-Value Next Steps\nPrioritize items that:\n- **Unblock multiple other items** - High leverage impact\n- **Deliver user-visible value** - Direct user benefit\n- **Reduce technical risk** - Address major uncertainties\n- **Enable validation** - Allow testing of key assumptions\n- **Provide learning** - Generate insights for future work\n\n### Low-Priority Items\nIdentify items that:\n- **Have many dependencies** - Can't be started yet\n- **Are nice-to-have** - Don't impact core value proposition\n- **Are optimization-focused** - Improve existing working features\n- **Require external dependencies** - Waiting on others\n\n## Step 6: Single Task Recommendation\n\n**Note**: If you arrived here from Step 0 (clear context), use the conversation history and known PRD state to make your recommendation. If you came through the full analysis, use your detailed findings.\n\nPresent findings in this focused format:\n\n```markdown\n# Next Task Recommendation: [Feature Name]\n\n## Recommended Task: [Specific Task Name]\n\n**Why this task**: [2-3 sentences explaining why this is the highest priority right now]\n\n**What it unlocks**: [What becomes possible after completing this]\n\n**Dependencies**: [What's already complete that makes this ready to work on]\n\n**Success criteria**: [How you'll know it's done]\n\n---\n\n**Do you want to work on this task?** \n\nIf yes, I'll help you design the implementation approach. If no, let me know what you'd prefer to work on instead.\n```\n\n## Step 7: Design Discussion (If Confirmed)\n\nIf the user confirms they want to work on the recommended task, then dive into:\n\n### Implementation Planning\n- **Architecture approach**: How this fits into existing codebase\n- **Key components**: What needs to be built\u002Fmodified\n- **Integration points**: How it connects with existing code\n- **Testing strategy**: How to validate the implementation\n\n### Design Decisions\n- **Technical choices**: Framework\u002Flibrary decisions to make\n- **Interface design**: APIs, data structures, user interfaces\n- **Error handling**: How to handle failure cases\n- **Performance considerations**: Scalability and optimization needs\n\n### Implementation Steps\n- **Step-by-step breakdown**: Logical sequence of implementation\n- **Quick wins**: Parts that can be completed first for validation\n- **Risk mitigation**: Addressing the biggest uncertainties first\n- **Testing checkpoints**: When and how to validate progress\n\n### Questions to Resolve\n- **Open decisions**: Design choices that need to be made\n- **Clarifications needed**: Requirements that need more detail\n- **Assumptions to validate**: Things we're assuming that should be confirmed\n\n## Success Criteria\n\nThis command should:\n- ✅ Identify the single highest-value task to work on next based on current PRD state\n- ✅ Provide clear, compelling rationale for why this specific task should be prioritized\n- ✅ Wait for user confirmation before proceeding\n- ✅ If confirmed, provide detailed implementation design guidance\n- ✅ Keep teams focused on the most important work rather than overwhelming them with options\n- ✅ Enable immediate action by transitioning from recommendation to design discussion\n\n## Step 8: Update Progress After Completion\n\n**CRITICAL: Do NOT update the PRD yourself. Do NOT edit PRD files directly. Your job is to prompt the user to run the update command.**\n\nAfter the user completes the task implementation, output ONLY this message:\n\n---\n\n**Task implementation complete.**\n\nTo update PRD progress and commit your work, run `\u002Fprd-update-progress`.\n\n---\n\nThen STOP. Do not proceed further. The `\u002Fprd-update-progress` command handles PRD updates, progress tracking, and commits. This separation ensures proper workflow and avoids duplicate\u002Fconflicting updates.\n\n","# PRD Next - Work On the Next Task\n\n## Instructions\n\nYou are helping analyze an existing Product Requirements Document (PRD) to suggest the single highest-priority task to work on next, then discuss its design if the user confirms they want to work on it.\n\n## Process Overview\n\n1. **Check Context Clarity** - Determine if PRD is obvious from recent conversation\n2. **Auto-Detect Target PRD** - If context unclear, intelligently determine which PRD to analyze\n3. **Analyze Current Implementation** - Understand what's implemented vs what's missing (skip if recent context available)\n4. **Identify the Single Best Next Task** - Find the one task that should be worked on next\n5. **Present Recommendation** - Give clear rationale and wait for confirmation\n6. **Design Discussion** - If confirmed, dive into implementation design details\n7. **Implementation** - User implements the task\n8. **Update Progress** - Prompt user to run \u002Fprd-update-progress\n\n## Step 0: Context Awareness Check\n\n**FIRST: Check if PRD context is already clear from recent conversation:**\n\n**Skip detection\u002Fanalysis 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 6 (Single Task Recommendation) using the known PRD \n- Use conversation history to understand current state and recent progress\n- Proceed directly with task recommendation based on known PRD status\n\n**If context is unclear:**\n- Continue to Step 1 (PRD Detection) for full analysis\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   - `prds\u002F12-documentation-testing.md`\n   - `prds\u002F13-cicd-documentation-testing.md`\n\n5. **Fallback to User Choice** - Only if context detection fails, ask user to specify\n\n**PRD Detection Implementation:**\n```bash\n# Use these tools to gather context:\n# 1. Check git branch: gitStatus shows current branch\n# 2. Check git status: Look for modified PRD files  \n# 3. List PRDs: Use LS or Glob to find prds\u002F*.md files\n# 4. Recent commits: Use Bash 'git log --oneline -n 5' for recent context\n```\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**Example Detection Outputs:**\n```markdown\n? **Auto-detected PRD 12** (Documentation Testing)\n- Branch: `feature\u002Fprd-12-documentation-testing` ✅\n- Modified files: `prds\u002F12-documentation-testing.md` ✅\n- Recent commits mention PRD 12 features ✅\n```\n\n**Once PRD is identified:**\n- Read the PRD file from `prds\u002F[issue-id]-[feature-name].md`\n- Analyze completion status across all sections\n- Identify patterns in completed vs remaining work\n\n## Step 2: Documentation & Implementation Analysis (Only if Context Unclear)\n\nBefore assessing task priorities, analyze both the documented specifications and current implementation state:\n\n### Documentation Analysis (Documentation-First PRDs)\nFor PRDs using the documentation-first approach:\n- **Read referenced documentation**: Check the \"Content Location Map\" in PRD to find where feature specs live\n- **Understand target state**: What functionality is documented but not yet implemented\n- **Check documentation completeness**: Are all user workflows and examples fully documented\n- **Validate cross-references**: Do all documentation links and references work correctly\n\n### Code Discovery\n- **Search for related files**: Use Grep\u002FGlob to find files related to the feature\n- **Identify key modules**: Locate main implementation files mentioned in PRD\n- **Find test files**: Discover existing test coverage for the feature\n- **Check dependencies**: Review imports and module relationships\n\n### Implementation vs Documentation Gap Analysis\n- **Compare docs vs code**: What's documented vs actually implemented\n- **Partial implementations**: Identify half-finished features or TODO comments\n- **Documentation validation**: Can documented examples and commands actually work\n- **Architecture alignment**: Does current code match documented behavior and PRD architecture decisions\n- **Quality assessment**: Code style, error handling, test coverage gaps\n\n### Technical Feasibility Analysis\n- **Dependency conflicts**: Are PRD requirements compatible with existing code\n- **Breaking changes**: Will remaining tasks require refactoring existing code\n- **Integration points**: How new work connects with current implementation\n- **Technical debt**: Issues that might block or slow future work\n\n## Step 3: Completion Assessment (Only if Context Unclear)\n\n### Analyze Checkbox States\nCount and categorize all checkboxes:\n- **Completed**: `[x]` items\n- **Pending**: `[ ]` items  \n- **Deferred**: `[~]` items\n- **Blocked**: `[!]` items\n\n### Phase Analysis\nFor each implementation phase:\n- Calculate completion percentage\n- Identify bottlenecks or stalled work\n- Assess readiness to move to next phase\n\n### Requirement Coverage\nReview requirement categories:\n- **Functional Requirements**: Core feature completion\n- **Non-Functional Requirements**: Quality and performance aspects\n- **Success Criteria**: Measurable outcomes\n- **Dependencies**: External requirements\n- **Risk Mitigation**: Risk management progress\n\n## Step 4: Dependency Analysis (Only if Context Unclear)\n\n### Identify Critical Path Items\nLook for items that:\n- **Block other work** - Must be completed before others can start\n- **Enable major capabilities** - Unlock significant value when completed\n- **Resolve current blockers** - Remove impediments to progress\n\n### Dependency Patterns\n\n#### PRD-Level Dependencies\n- **Sequential dependencies** - A must be done before B\n- **Parallel opportunities** - Multiple items that can be worked simultaneously  \n- **Foundation requirements** - Core capabilities needed by multiple features\n- **Integration points** - Items that connect different parts of the system\n\n#### Code-Level Dependencies  \n- **Import dependencies** - Modules that depend on others being implemented first\n- **Interface contracts** - APIs\u002Ftypes that must be defined before consumers\n- **Database schema** - Data model changes needed before business logic\n- **Test dependencies** - Tests that require certain infrastructure or mocks\n- **Build\u002Fdeployment** - Configuration changes that affect multiple components\n\n## Step 5: Strategic Value Assessment (Only if Context Unclear)\n\n### High-Value Next Steps\nPrioritize items that:\n- **Unblock multiple other items** - High leverage impact\n- **Deliver user-visible value** - Direct user benefit\n- **Reduce technical risk** - Address major uncertainties\n- **Enable validation** - Allow testing of key assumptions\n- **Provide learning** - Generate insights for future work\n\n### Low-Priority Items\nIdentify items that:\n- **Have many dependencies** - Can't be started yet\n- **Are nice-to-have** - Don't impact core value proposition\n- **Are optimization-focused** - Improve existing working features\n- **Require external dependencies** - Waiting on others\n\n## Step 6: Single Task Recommendation\n\n**Note**: If you arrived here from Step 0 (clear context), use the conversation history and known PRD state to make your recommendation. If you came through the full analysis, use your detailed findings.\n\nPresent findings in this focused format:\n\n```markdown\n# Next Task Recommendation: [Feature Name]\n\n## Recommended Task: [Specific Task Name]\n\n**Why this task**: [2-3 sentences explaining why this is the highest priority right now]\n\n**What it unlocks**: [What becomes possible after completing this]\n\n**Dependencies**: [What's already complete that makes this ready to work on]\n\n**Success criteria**: [How you'll know it's done]\n\n---\n\n**Do you want to work on this task?** \n\nIf yes, I'll help you design the implementation approach. If no, let me know what you'd prefer to work on instead.\n```\n\n## Step 7: Design Discussion (If Confirmed)\n\nIf the user confirms they want to work on the recommended task, then dive into:\n\n### Implementation Planning\n- **Architecture approach**: How this fits into existing codebase\n- **Key components**: What needs to be built\u002Fmodified\n- **Integration points**: How it connects with existing code\n- **Testing strategy**: How to validate the implementation\n\n### Design Decisions\n- **Technical choices**: Framework\u002Flibrary decisions to make\n- **Interface design**: APIs, data structures, user interfaces\n- **Error handling**: How to handle failure cases\n- **Performance considerations**: Scalability and optimization needs\n\n### Implementation Steps\n- **Step-by-step breakdown**: Logical sequence of implementation\n- **Quick wins**: Parts that can be completed first for validation\n- **Risk mitigation**: Addressing the biggest uncertainties first\n- **Testing checkpoints**: When and how to validate progress\n\n### Questions to Resolve\n- **Open decisions**: Design choices that need to be made\n- **Clarifications needed**: Requirements that need more detail\n- **Assumptions to validate**: Things we're assuming that should be confirmed\n\n## Success Criteria\n\nThis command should:\n- ✅ Identify the single highest-value task to work on next based on current PRD state\n- ✅ Provide clear, compelling rationale for why this specific task should be prioritized\n- ✅ Wait for user confirmation before proceeding\n- ✅ If confirmed, provide detailed implementation design guidance\n- ✅ Keep teams focused on the most important work rather than overwhelming them with options\n- ✅ Enable immediate action by transitioning from recommendation to design discussion\n\n## Step 8: Update Progress After Completion\n\n**CRITICAL: Do NOT update the PRD yourself. Do NOT edit PRD files directly. Your job is to prompt the user to run the update command.**\n\nAfter the user completes the task implementation, output ONLY this message:\n\n---\n\n**Task implementation complete.**\n\nTo update PRD progress and commit your work, run `\u002Fprd-update-progress`.\n\n---\n\nThen STOP. Do not proceed further. The `\u002Fprd-update-progress` command handles PRD updates, progress tracking, and commits. This separation ensures proper workflow and avoids duplicate\u002Fconflicting updates.\n\n",{"name":5,"description":7,"user-invocable":38},true,"main","6faa9f452f568fc9aa9b1c17ee728de11b760cb7",".claude\u002Fskills\u002Fdot-ai-prd-next",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":49,"prompt":59,"zipAvailable":38},[50,53,56],{"tool":51,"command":52},"npx","npx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-next",{"tool":54,"command":55},"bunx","bunx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-next",{"tool":57,"command":58},"pnpm","pnpm dlx skills add vfarcic\u002Fdot-ai-headlamp --skill dot-ai-prd-next","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvfarcic\u002Fdot-ai-headlamp\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fdot-ai-prd-next\u002FSKILL.md",[],[62,87,105,120,134,144],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":33},"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",[],[25,27,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86],"visualization","delete","repo","deployment","kubernetes","capabilities","search","logs","knowledge","history","project","session","ingest","queries","natural language","query","scaffolding","knowledge base",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":33},"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",[],[25,94,27,95,96,97,98,99,100,101,102,103,104],"docs","write","dot ai write docs","write documentation","commands","use","documentation","examples","doc","capture","user",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"publishedAt":33},"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",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,113,25,114,27,115,116,117,31,118,119,104],"worktree","dot ai worktree prd","create","git","git worktree","branch","context",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":33},"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",[],[27,127,25,128,129,130,131,132,133],"dot ai version","version","diagnostics","health","system","system health","get",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":33},"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",[],[27,141,25,115,70,142,143],"dot ai users","list","manage",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":33},"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",[],[27,151,25,152,115,153,154,155],"dot ai tag release","release","run","changelog","ready"]