[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SZVVBPR0P71NFP4CAESC4":3,"skill-same:01M71SZVVBPR0P71NFP4CAESC4":82},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":71},"01M71SZVVBPR0P71NFP4CAESC4","product-enhance",null,"Use when you have specific product issues to triage or want to discover enhancement opportunities in an existing product through gap analysis. For exploring what a codebase could become, use \u002Fclaudna:product-vision.","Claudfather\u002FclauDNA","Claudfather","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F281278891?v=4","01M71SX82K0TBGQ394AB2G1T5Z","01M71SX83CE1S8YC06K9P3P962",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-enhance\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"product enhance","product","enhance","codebase","github","focus","gap","output","analysis","gap analysis","you","when","Existing","use","auto","true","issues","session","for","discover","2026-11-10 13:02:02",false,"---\nname: product-enhance\nuser-invocable: true\ndescription: \"Use when you have specific product issues to triage or want to discover enhancement opportunities in an existing product through gap analysis. For exploring what a codebase could become, use \u002Fclaudna:product-vision.\"\nargument-hint: \"[--auto] [--output github|session] [focus-area]\"\n---\n\n# Product Enhancement Discovery & Design\n\n> **Codex:** Read `..\u002F_shared\u002Fcodex-tools.md` before following this skill. Apply its tool, root and dispatch mappings throughout.\n\n**Persona:** Product-minded engineering lead. Think like a PM who can read code. Understand intent first, then produce phased design docs. Concrete observations ranked by impact — no buzzwords.\n\n## Arguments\n\nParse `$ARGUMENTS` at invocation:\n- `--auto`: Fully non-interactive. Implies `--output github`. Uses triage path, skips discovery\u002Finterview. See orchestration guide Section 10.\n- `--output github`: Write enhancement proposals as GitHub Issues. See output guide (`..\u002F_shared\u002Foutput-guide.md`).\n- `--output session`: Present findings in chat only, no persistence.\n- Remaining text is the focus area. If provided, use it as scope context in Step 1 instead of asking.\n\n## When NOT to use\n\n- For net-new feature brainstorming (divergent ideation) → use `\u002Fclaudna:product-vision`\n- For code quality\u002Ftech debt → use `\u002Fclaudna:audit tech-debt`\n- For security vulnerabilities → use `\u002Fclaudna:audit security`\n\n## Process Flow (authoritative)\n\n```dot\ndigraph product_enhance {\n    rankdir=TB;\n    node [fontname=\"Helvetica\" fontsize=10];\n    edge [fontname=\"Helvetica\" fontsize=9];\n\n    start [label=\"User invokes\\n\u002Fproduct-enhance\" shape=doublecircle];\n    enter_plan [label=\"EnterPlanMode\" shape=box style=\"filled,bold\" fillcolor=lightyellow];\n\n    entry [label=\"Step 1: Ask scope\\nand entry point\" shape=box];\n    recon [label=\"Step 1B: Codebase Recon\\nExplore subagents\" shape=box];\n    confirm_recon [label=\"Codebase picture\\naccurate?\" shape=diamond];\n\n    path_choice [label=\"Triage or\\nDiscovery?\" shape=diamond];\n\n    triage [label=\"Step 1C: Triage Intake\\nCollect user's list\" shape=box];\n    triage_validate [label=\"Validate items\\nvs codebase\" shape=box];\n    triage_confirm [label=\"Validation\\ncorrect?\" shape=diamond];\n\n    interview [label=\"Step 2: Intent Interview\\nGroups A → B → C\" shape=box];\n    gap [label=\"Step 3: Gap Analysis\\nIntent vs Implementation\" shape=box];\n    gap_confirm [label=\"Gap analysis\\naccurate?\" shape=diamond];\n\n    proposals [label=\"Step 4: Enhancement Proposals\\nRanked by impact:effort\" shape=box];\n    user_selects [label=\"User selects\\nenhancements?\" shape=diamond];\n\n    exit_plan [label=\"ExitPlanMode\" shape=box style=\"filled,bold\" fillcolor=lightyellow];\n\n    generate [label=\"Step 5: Generate Design Docs\\nPlan subagents\" shape=box];\n\n    done [label=\"Summary\\nReady for \u002Fclaudna:build\" shape=box style=filled fillcolor=lightgreen];\n\n    start -> enter_plan;\n    enter_plan -> entry;\n    entry -> recon;\n    recon -> confirm_recon;\n    confirm_recon -> recon [label=\"incorrect\"];\n    confirm_recon -> path_choice [label=\"confirmed\"];\n    path_choice -> triage [label=\"has list\"];\n    path_choice -> interview [label=\"discover\"];\n    triage -> triage_validate;\n    triage_validate -> triage_confirm;\n    triage_confirm -> triage_validate [label=\"corrections\"];\n    triage_confirm -> proposals [label=\"confirmed\"];\n    interview -> gap;\n    gap -> gap_confirm;\n    gap_confirm -> gap [label=\"corrections\"];\n    gap_confirm -> proposals [label=\"confirmed\"];\n    proposals -> user_selects;\n    user_selects -> proposals [label=\"adjust\"];\n    user_selects -> exit_plan [label=\"selected\"];\n    exit_plan -> generate;\n    generate -> done;\n}\n```\n\n## Procedure\n\n**Enter Plan Mode.** Call `EnterPlanMode`. Steps 1–4 are read-only. If the user declines, proceed normally.\n\n---\n\n### Step 1: Entry Point & Scope\n\nAsk the user: **\"Are you coming in with specific issues, or should we discover enhancement opportunities together?\"** Also ask what to focus on and what to skip.\n\n- **\"I have a list\"** → **Triage path.** Step 1B → Step 1C → Step 4 (skip 2–3).\n- **\"Let's discover\"** → **Discovery path.** Step 1B → Steps 2–3–4 in order.\n\n#### Step 1B: Codebase Reconnaissance\n\nScratch directory: `\u003Cscratch>\u002Fresearch\u002F`, with `\u003Cscratch>` a private directory made by `mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fproduct-enhance.XXXXXX\"`. Launch **Explore subagents** covering structure, modules, entry points, docs, tests, dependencies, recent git history. Do NOT read CLAUDE.md\u002FMEMORY.md in orchestrator. Disk-write per orchestration guide, Section 2. Present a `Codebase Context` summary; ask user to confirm.\n\n---\n\n### Step 1C: Triage Intake (Triage Path Only)\n\nCollect the user's list (any format). Launch **Explore subagents** to validate each item (responsible code, reproducibility, partial support, root causes). Disk-write to `research\u002F\u003Cissue-slug>.md`. Present a `Triage Validation` table, confirm, then skip to Step 4.\n\n---\n\n### Step 2: Intent Interview (Discovery Path Only)\n\nAsk questions one group at a time (A: Core Purpose, B: Current State, C: Aspirations), waiting between groups. See **`intent-interview-questions.md`** for the full list. Capture answers as structured notes.\n\n---\n\n### Step 3: Gap Analysis (Discovery Path Only)\n\nCompare Step 2 answers against Step 1B findings via **Explore subagents** (disk-write to `research\u002F\u003Cgap-slug>.md`). Present as a numbered table using the six categories from **`gap-categories.md`**. Ask user to confirm.\n\n---\n\n### Step 4: Enhancement Proposals\n\n**Both paths converge here.** Where findings share an evidenced cause, name it and consolidate overlapping proposals before ranking; keep unrelated findings separate rather than forcing a theme. Rank enhancements by impact-to-effort ratio (H\u002FM\u002FL for Impact, Effort, Risk). Each gets a 2-3 sentence description. Ask user to select by number; do NOT proceed until confirmed. Call `ExitPlanMode`.\n\n---\n\n### Step 5: Generate Phased Design Docs\n\nOutput lands in `documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F`, prefixed `01_`, `02_` by implementation order — Plan agents write the family to the session's scratch docs directory and the orchestrator publishes it with `\u002Fclaudna:publish \u003Cscratch-docs-dir> --to docs --dir documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F` (family mode; Section 3). `00_OVERVIEW.md`: context, dependency graph, parallel phases, total effort. Archive per Section 8; Plan agents per Section 9, reading from scratch research dir. Plan agents must also read `..\u002F_shared\u002Fplanning-standard.md`.\n\nPresent a `Product Enhancement Summary`, then direct user to `\u002Fclaudna:build`. **This skill produces plans, not code.**\n\n---\n\n### Step 5.5: Adversarial Review Pass\n\nFollow `..\u002F_shared\u002Fpre-handoff-checklist.md` for the full procedure. Run on each phase doc (`\u003CNN>_*.md`) and `00_OVERVIEW.md` in the session's scratch docs directory, before the family is published to `documentation\u002Fplanning\u002Fphases\u002F\u003Csession>\u002F`. Apply in all modes.\n\n---\n\n## Notes\n\n- **User gates everywhere.** Never auto-proceed between major steps.\n- **Subagent strategy.** Explore agents (Steps 1, 3) for analysis; Plan agents (Step 5) for docs. Disk-write pattern per orchestration guide. Context never flows through orchestrator.\n- **Intent-first.** Discovery's value is Steps 2–3. Without them, it's just a code generator.\n- Shared reminders: orchestration guide, Section 10.\n\n---\n\n## Output Targets\n\nThis skill supports `--output github` and `--output session` in addition to the default `docs` target.\n\nFollow the output guide at `..\u002F_shared\u002Foutput-guide.md`:\n- For `github`: write each finding as a doc (frontmatter + the Section 4 body skeleton) and delegate to `\u002Fclaudna:publish \u003Cfile> --to github-issue --repo \u003Crepo>` — publish validates, dedups, and applies labels from `tags:`. Apply `enhancement` label to all issues. Map impact ranking to priority labels.\n- For `session`: produce the doc, then `\u002Fclaudna:publish \u003Cfile> --to session` prints it to chat (Section 5)\n- For `docs` (default): follow the subagent workflow in the orchestration guide (publish step: `--dir documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F`)\n\nAfter creating issues, present the batch summary and return issue URLs for audit tracking.\n\n---\n\n## Autonomous Mode (--auto)\n\nWhen `--auto` is set (see orchestration guide Section 10):\n1. Skip Plan Mode and the intent interview (Steps 2-3) — use triage path only\n2. Run codebase reconnaissance (Step 1B) automatically with scope from `$ARGUMENTS`\n3. Auto-generate enhancement proposals from gap analysis (skip user selection)\n4. Create GitHub Issues for all proposals ranked High or Medium impact\n5. **Emit the structured-result shape** per `..\u002F_shared\u002Forchestration-guide.md` §10.C as the FINAL output of the run — a fenced ```json block with no text after:\n\n```json\n{\n  \"skill\": \"product-enhance\",\n  \"outcome\": \"completed\",\n  \"artifacts\": {\n    \"issues_created\": [\"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fissues\u002F123\", \"...\"],\n    \"proposals_ranked\": 8,\n    \"session_dir\": \"documentation\u002Fplanning\u002Fphases\u002F\u003Csession>\u002F\"\n  },\n  \"summary\": \"\u003C2-3 line digest of proposals filed>\",\n  \"next\": null,\n  \"errors\": [],\n  \"blocker_description\": null\n}\n```\n\n- `outcome` is `completed` on success, `blocked` if codebase reconnaissance can't run.\n","# Product Enhancement Discovery & Design\n\n> **Codex:** Read `..\u002F_shared\u002Fcodex-tools.md` before following this skill. Apply its tool, root and dispatch mappings throughout.\n\n**Persona:** Product-minded engineering lead. Think like a PM who can read code. Understand intent first, then produce phased design docs. Concrete observations ranked by impact — no buzzwords.\n\n## Arguments\n\nParse `$ARGUMENTS` at invocation:\n- `--auto`: Fully non-interactive. Implies `--output github`. Uses triage path, skips discovery\u002Finterview. See orchestration guide Section 10.\n- `--output github`: Write enhancement proposals as GitHub Issues. See output guide (`..\u002F_shared\u002Foutput-guide.md`).\n- `--output session`: Present findings in chat only, no persistence.\n- Remaining text is the focus area. If provided, use it as scope context in Step 1 instead of asking.\n\n## When NOT to use\n\n- For net-new feature brainstorming (divergent ideation) → use `\u002Fclaudna:product-vision`\n- For code quality\u002Ftech debt → use `\u002Fclaudna:audit tech-debt`\n- For security vulnerabilities → use `\u002Fclaudna:audit security`\n\n## Process Flow (authoritative)\n\n```dot\ndigraph product_enhance {\n    rankdir=TB;\n    node [fontname=\"Helvetica\" fontsize=10];\n    edge [fontname=\"Helvetica\" fontsize=9];\n\n    start [label=\"User invokes\\n\u002Fproduct-enhance\" shape=doublecircle];\n    enter_plan [label=\"EnterPlanMode\" shape=box style=\"filled,bold\" fillcolor=lightyellow];\n\n    entry [label=\"Step 1: Ask scope\\nand entry point\" shape=box];\n    recon [label=\"Step 1B: Codebase Recon\\nExplore subagents\" shape=box];\n    confirm_recon [label=\"Codebase picture\\naccurate?\" shape=diamond];\n\n    path_choice [label=\"Triage or\\nDiscovery?\" shape=diamond];\n\n    triage [label=\"Step 1C: Triage Intake\\nCollect user's list\" shape=box];\n    triage_validate [label=\"Validate items\\nvs codebase\" shape=box];\n    triage_confirm [label=\"Validation\\ncorrect?\" shape=diamond];\n\n    interview [label=\"Step 2: Intent Interview\\nGroups A → B → C\" shape=box];\n    gap [label=\"Step 3: Gap Analysis\\nIntent vs Implementation\" shape=box];\n    gap_confirm [label=\"Gap analysis\\naccurate?\" shape=diamond];\n\n    proposals [label=\"Step 4: Enhancement Proposals\\nRanked by impact:effort\" shape=box];\n    user_selects [label=\"User selects\\nenhancements?\" shape=diamond];\n\n    exit_plan [label=\"ExitPlanMode\" shape=box style=\"filled,bold\" fillcolor=lightyellow];\n\n    generate [label=\"Step 5: Generate Design Docs\\nPlan subagents\" shape=box];\n\n    done [label=\"Summary\\nReady for \u002Fclaudna:build\" shape=box style=filled fillcolor=lightgreen];\n\n    start -> enter_plan;\n    enter_plan -> entry;\n    entry -> recon;\n    recon -> confirm_recon;\n    confirm_recon -> recon [label=\"incorrect\"];\n    confirm_recon -> path_choice [label=\"confirmed\"];\n    path_choice -> triage [label=\"has list\"];\n    path_choice -> interview [label=\"discover\"];\n    triage -> triage_validate;\n    triage_validate -> triage_confirm;\n    triage_confirm -> triage_validate [label=\"corrections\"];\n    triage_confirm -> proposals [label=\"confirmed\"];\n    interview -> gap;\n    gap -> gap_confirm;\n    gap_confirm -> gap [label=\"corrections\"];\n    gap_confirm -> proposals [label=\"confirmed\"];\n    proposals -> user_selects;\n    user_selects -> proposals [label=\"adjust\"];\n    user_selects -> exit_plan [label=\"selected\"];\n    exit_plan -> generate;\n    generate -> done;\n}\n```\n\n## Procedure\n\n**Enter Plan Mode.** Call `EnterPlanMode`. Steps 1–4 are read-only. If the user declines, proceed normally.\n\n---\n\n### Step 1: Entry Point & Scope\n\nAsk the user: **\"Are you coming in with specific issues, or should we discover enhancement opportunities together?\"** Also ask what to focus on and what to skip.\n\n- **\"I have a list\"** → **Triage path.** Step 1B → Step 1C → Step 4 (skip 2–3).\n- **\"Let's discover\"** → **Discovery path.** Step 1B → Steps 2–3–4 in order.\n\n#### Step 1B: Codebase Reconnaissance\n\nScratch directory: `\u003Cscratch>\u002Fresearch\u002F`, with `\u003Cscratch>` a private directory made by `mktemp -d \"${TMPDIR:-\u002Ftmp}\u002Fproduct-enhance.XXXXXX\"`. Launch **Explore subagents** covering structure, modules, entry points, docs, tests, dependencies, recent git history. Do NOT read CLAUDE.md\u002FMEMORY.md in orchestrator. Disk-write per orchestration guide, Section 2. Present a `Codebase Context` summary; ask user to confirm.\n\n---\n\n### Step 1C: Triage Intake (Triage Path Only)\n\nCollect the user's list (any format). Launch **Explore subagents** to validate each item (responsible code, reproducibility, partial support, root causes). Disk-write to `research\u002F\u003Cissue-slug>.md`. Present a `Triage Validation` table, confirm, then skip to Step 4.\n\n---\n\n### Step 2: Intent Interview (Discovery Path Only)\n\nAsk questions one group at a time (A: Core Purpose, B: Current State, C: Aspirations), waiting between groups. See **`intent-interview-questions.md`** for the full list. Capture answers as structured notes.\n\n---\n\n### Step 3: Gap Analysis (Discovery Path Only)\n\nCompare Step 2 answers against Step 1B findings via **Explore subagents** (disk-write to `research\u002F\u003Cgap-slug>.md`). Present as a numbered table using the six categories from **`gap-categories.md`**. Ask user to confirm.\n\n---\n\n### Step 4: Enhancement Proposals\n\n**Both paths converge here.** Where findings share an evidenced cause, name it and consolidate overlapping proposals before ranking; keep unrelated findings separate rather than forcing a theme. Rank enhancements by impact-to-effort ratio (H\u002FM\u002FL for Impact, Effort, Risk). Each gets a 2-3 sentence description. Ask user to select by number; do NOT proceed until confirmed. Call `ExitPlanMode`.\n\n---\n\n### Step 5: Generate Phased Design Docs\n\nOutput lands in `documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F`, prefixed `01_`, `02_` by implementation order — Plan agents write the family to the session's scratch docs directory and the orchestrator publishes it with `\u002Fclaudna:publish \u003Cscratch-docs-dir> --to docs --dir documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F` (family mode; Section 3). `00_OVERVIEW.md`: context, dependency graph, parallel phases, total effort. Archive per Section 8; Plan agents per Section 9, reading from scratch research dir. Plan agents must also read `..\u002F_shared\u002Fplanning-standard.md`.\n\nPresent a `Product Enhancement Summary`, then direct user to `\u002Fclaudna:build`. **This skill produces plans, not code.**\n\n---\n\n### Step 5.5: Adversarial Review Pass\n\nFollow `..\u002F_shared\u002Fpre-handoff-checklist.md` for the full procedure. Run on each phase doc (`\u003CNN>_*.md`) and `00_OVERVIEW.md` in the session's scratch docs directory, before the family is published to `documentation\u002Fplanning\u002Fphases\u002F\u003Csession>\u002F`. Apply in all modes.\n\n---\n\n## Notes\n\n- **User gates everywhere.** Never auto-proceed between major steps.\n- **Subagent strategy.** Explore agents (Steps 1, 3) for analysis; Plan agents (Step 5) for docs. Disk-write pattern per orchestration guide. Context never flows through orchestrator.\n- **Intent-first.** Discovery's value is Steps 2–3. Without them, it's just a code generator.\n- Shared reminders: orchestration guide, Section 10.\n\n---\n\n## Output Targets\n\nThis skill supports `--output github` and `--output session` in addition to the default `docs` target.\n\nFollow the output guide at `..\u002F_shared\u002Foutput-guide.md`:\n- For `github`: write each finding as a doc (frontmatter + the Section 4 body skeleton) and delegate to `\u002Fclaudna:publish \u003Cfile> --to github-issue --repo \u003Crepo>` — publish validates, dedups, and applies labels from `tags:`. Apply `enhancement` label to all issues. Map impact ranking to priority labels.\n- For `session`: produce the doc, then `\u002Fclaudna:publish \u003Cfile> --to session` prints it to chat (Section 5)\n- For `docs` (default): follow the subagent workflow in the orchestration guide (publish step: `--dir documentation\u002Fplanning\u002Fphases\u002F\u003Csession_name>_\u003CYYYY-MM-DD>\u002F`)\n\nAfter creating issues, present the batch summary and return issue URLs for audit tracking.\n\n---\n\n## Autonomous Mode (--auto)\n\nWhen `--auto` is set (see orchestration guide Section 10):\n1. Skip Plan Mode and the intent interview (Steps 2-3) — use triage path only\n2. Run codebase reconnaissance (Step 1B) automatically with scope from `$ARGUMENTS`\n3. Auto-generate enhancement proposals from gap analysis (skip user selection)\n4. Create GitHub Issues for all proposals ranked High or Medium impact\n5. **Emit the structured-result shape** per `..\u002F_shared\u002Forchestration-guide.md` §10.C as the FINAL output of the run — a fenced ```json block with no text after:\n\n```json\n{\n  \"skill\": \"product-enhance\",\n  \"outcome\": \"completed\",\n  \"artifacts\": {\n    \"issues_created\": [\"https:\u002F\u002Fgithub.com\u002Forg\u002Frepo\u002Fissues\u002F123\", \"...\"],\n    \"proposals_ranked\": 8,\n    \"session_dir\": \"documentation\u002Fplanning\u002Fphases\u002F\u003Csession>\u002F\"\n  },\n  \"summary\": \"\u003C2-3 line digest of proposals filed>\",\n  \"next\": null,\n  \"errors\": [],\n  \"blocker_description\": null\n}\n```\n\n- `outcome` is `completed` on success, `blocked` if codebase reconnaissance can't run.\n",{"name":5,"description":7,"argument-hint":48,"user-invocable":49},"[--auto] [--output github|session] [focus-area]",true,"main","fc776f04574726e261087dbb521c1831bf0ea9d5","skills\u002Fproduct-enhance",1,"https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA","https:\u002F\u002Fgithub.com\u002FClaudfather","https:\u002F\u002Fcrog.gg","Rise of the machines","2026-11-08 21:32:41",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":49},[61,64,67],{"tool":62,"command":63},"npx","npx skills add Claudfather\u002FclauDNA --skill product-enhance",{"tool":65,"command":66},"bunx","bunx skills add Claudfather\u002FclauDNA --skill product-enhance",{"tool":68,"command":69},"pnpm","pnpm dlx skills add Claudfather\u002FclauDNA --skill product-enhance","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-enhance\u002FSKILL.md",[72,78],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"gap-categories.md","REFERENCE","参考文档",1773,"https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-enhance\u002Fgap-categories.md",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"intent-interview-questions.md",1791,"https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fproduct-enhance\u002Fintent-interview-questions.md",[83,107,117,140,164,179],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":43},"01M71T1STJ99BE1C0JYHCQW0XN","example-review","Use when you want to review pull requests with detailed, actionable feedback on code quality, correctness, and maintainability.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvalid-package\u002FSKILL.md",[],[90,91,92,93,94,95,96,97,98,33,34,36,99,100,101,102,103,104,105,106],"review","example","example review","actionable","pull requests","with","code","correctness","Bash","gh","gh pr","diff","view","pr","code quality","feedback","pull",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":43},"01M71T1RMCD30MAJC954JC7580","bad-skill","Too short","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Ffailing-package\u002FSKILL.md",[],[114,115,116],"bad","bad skill","short",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":43},"01M71T1NS97NJ2MQ993V7FBES7","worktree","Use when starting feature work that needs isolation from the current workspace, or when running multiple Claude sessions in parallel on different branches — creates and manages git worktrees. For fetching latest main into every existing worktree and branch across your sibling repos, use \u002Fclaudna:sync-branches instead.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fworktree\u002FSKILL.md",[],[119,124,125,126,127,128,129,130,131,132,133,134,34,135,50,136,137,138,41,139],"sync","repos","git","isolation","running","sessions","worktrees","work","across","needs","git worktrees","claude sessions","branches","branch","parallel","feature",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":43},"01M71T1HNVG1CZY8P904P6RB7P","weigh-development-paths","Use when at a development junction with multiple viable approaches — architecture choices, refactoring strategies, where to put new code, or which pattern to follow. Triggers on 'which approach', 'how should I', 'Option A vs B', or any point where the next step isn't obvious and the wrong choice creates rework.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fweigh-development-paths\u002FSKILL.md",[],[147,148,149,150,151,152,153,154,155,156,157,158,159,96,34,37,160,161,162,163],"development","weigh development paths","paths","next step","path","refactoring","choice","pattern","at","how","next","strategies","architecture","new","junction","option","which",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":43},"01M71T1ECV1T5E168GH70AY5B3","verify-completion","Use when about to claim work is complete, fixed, or passing -- requires running verification commands and confirming output before making any success claims.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fverify-completion\u002FSKILL.md",[],[171,172,173,174,128,38,175,176,131,177,178,30,34,36],"verify completion","verify","claim","complete","commands","about","verification","claims",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":190,"publishedAt":43},"01M71T1BC1HA7XQH0Q1H574FYS","vercel","Use for Vercel operations — deploy to production or preview (or roll back), view, filter, or debug deployment logs, or check project status (deployments, domains, env vars, config). Replaces \u002Fvercel-deploy, \u002Fvercel-logs, \u002Fvercel-status.","https:\u002F\u002Fgithub.com\u002FClaudfather\u002FclauDNA\u002Fblob\u002Fmain\u002Fskills\u002Fvercel\u002FSKILL.md",[185],{"categoryNo":186,"categoryName":187,"taxonomyType":188,"taxonomyTypeDesc":189},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[181,191,192,193,194,195,196,197,198,36,199,38,200,201,202,203,41,102,204,205],"inspection","check","filter","env","logs","preview","debug deployment","debug","deployments","domains","deployment","env vars","project","project status","back"]