[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72YY5PF5JZ9FN6CKWCJSGZA":3,"skill-same:01M72YY5PF5JZ9FN6CKWCJSGZA":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":45},"01M72YY5PF5JZ9FN6CKWCJSGZA","prd-stress-test",null,"Run a multi-agent PRD review to answer: Is this PRD ready to build?","enigmaicon-eng\u002FAI-Enterprise-OS","enigmaicon-eng","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F269773191?v=4","01M72YXXYN7Q7BYRHV8RAVYNWD","01M72YXXZPW35H56D6F1XSK84D",2,"MIT","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fprd-stress-test\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: prd-stress-test\ndescription: \"Run a multi-agent PRD review to answer: Is this PRD ready to build?\"\nuser-invocable: true\ndisable-model-invocation: true\nargument-hint: \"\u003Cpath-to-prd.md>\"\nallowed-tools: Read, Glob, Grep, Task\n---\n\n# PRD Stress Test\n\nRun a multi-agent PRD review to answer: **\"Is this PRD ready to build?\"** Three reviewers analyze different dimensions in parallel, cross-reference findings, and deliver a consolidated review report.\n\n## Usage\n\n```bash\n\u002Fagent-teams:prd-stress-test path\u002Fto\u002Fprd.md\n```\n\n---\n\n## Overview\n\nThis command spawns three specialist reviewers to stress-test a PRD from different angles:\n\n- **market-fit-reviewer**: Does this solve a real problem for a real market?\n- **feasibility-reviewer**: Are the requirements clear and buildable?\n- **scope-reviewer**: Is this appropriately sized for V1?\n\nAfter parallel review, reviewers cross-reference findings to catch conflicts (e.g., scope-reviewer wants to cut a feature that market-fit-reviewer considers critical). The lead compiles everything into a consolidated review report with per-dimension scores and an actionable revision checklist.\n\n**What you get:**\n\n- Three independent review dimensions scored 1-5\n- Blocking issues (must fix before building)\n- Suggestions (nice to fix)\n- Conflicts between reviewers\n- Overall verdict: READY TO BUILD \u002F NEEDS REVISION \u002F MAJOR REWORK\n- Specific revision checklist\n\n---\n\n## PRD to Review\n\nRead the PRD at: $ARGUMENTS\n\n---\n\n## Instructions\n\n### Pre-Flight Check\n\n1. Verify Agent Teams is available in your Claude Code version.\n   If teammates cannot be spawned, display:\n\n   ```\n   This command requires Claude Code's Agent Teams feature.\n   Check https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code for setup instructions.\n   ```\n\n   If not available, stop.\n\n2. Read the PRD file from the path in the \"PRD to Review\" section above.\n   - If file not found, display error and stop:\n     ```\n     Error: PRD file not found at [path].\n     Please provide a valid path to a PRD markdown file.\n     ```\n\n---\n\n### Phase 1: PRD Intake\n\n1. Parse the PRD content and identify key sections (features, requirements, target users, etc.).\n\n2. Check for existing product context:\n   - Read `.claude\u002Fproduct-context\u002Fproduct-info.md` if it exists\n   - Read `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md` if it exists\n\n3. Display briefing:\n\n```\n── PRD Stress Test ────────────────────────────────────────\n\nPRD: [file path]\nTitle: [extracted title or first heading]\n\nAssembling your review team:\n  1. market-fit-reviewer   → Market fit and differentiation\n  2. feasibility-reviewer  → Technical feasibility and requirements clarity\n  3. scope-reviewer        → Scope appropriateness and MVP sizing\n\nPhase 1: Parallel Review (3 reviewers working simultaneously)\nPhase 2: Cross-Reference (reviewers check each other's findings)\nPhase 3: Consolidated Report (verdict with revision checklist)\n\nStarting review...\n───────────────────────────────────────────────────────────\n```\n\n---\n\n### Phase 2: Parallel Review\n\nSpawn 3 teammates simultaneously using Agent Teams:\n\n**Teammate 1: market-fit-reviewer**\n\n```\nPrompt: \"Review this PRD for market fit. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\n[Include any product context found in Phase 1]\n\nYour job: Evaluate target user clarity, problem validation, value proposition,\ndifferentiation, and market context. Use your market-fit-reviewer expertise.\n\nDeliver your review in the standard market-fit-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\n**Teammate 2: feasibility-reviewer**\n\n```\nPrompt: \"Review this PRD for technical feasibility and requirements clarity. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\nYour job: Evaluate requirements clarity, acceptance criteria, technical\nfeasibility, edge cases, and integration points. Flag every ambiguity.\nUse your feasibility-reviewer expertise.\n\nDeliver your review in the standard feasibility-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\n**Teammate 3: scope-reviewer**\n\n```\nPrompt: \"Review this PRD for scope appropriateness. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\nYour job: Assess total scope, classify every feature as MUST-HAVE \u002F CUT FROM V1 \u002F\nDEFER TO V2, identify scope creep, and estimate effort reduction from cuts.\nUse your scope-reviewer expertise. Apply the 3-Feature MVP Rule.\n\nDeliver your review in the standard scope-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\nWait for all three reviewers to complete their reviews.\n\n---\n\n### Phase 3: Cross-Reference\n\nSend each reviewer the other two reviewers' findings to flag conflicts.\n\n**To market-fit-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nFEASIBILITY REVIEW:\n[feasibility-reviewer output]\n\nSCOPE REVIEW:\n[scope-reviewer output]\n\nSpecifically check:\n- Are features you consider critical for differentiation marked 'CUT' by scope-reviewer?\n- Do feasibility concerns affect market-critical features?\nFlag conflicts and explain your position.\"\n```\n\n**To feasibility-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nMARKET FIT REVIEW:\n[market-fit-reviewer output]\n\nSCOPE REVIEW:\n[scope-reviewer output]\n\nSpecifically check:\n- Do features market-fit-reviewer considers critical have clear requirements?\n- Do scope cuts remove technically risky components (positive) or create gaps?\nFlag conflicts and explain your position.\"\n```\n\n**To scope-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nMARKET FIT REVIEW:\n[market-fit-reviewer output]\n\nFEASIBILITY REVIEW:\n[feasibility-reviewer output]\n\nSpecifically check:\n- Are features you marked 'CUT' considered critical by market-fit-reviewer?\n- Do your cuts align with feasibility concerns?\nFlag conflicts and explain your position. Be willing to reconsider cuts if\nmarket-fit evidence is strong.\"\n```\n\nWait for all three cross-reference responses.\n\n---\n\n### Phase 4: Consolidated Report\n\nAs the lead agent, compile all findings into the PRD Review Report.\n\n1. Read all review reports and cross-reference responses.\n\n2. Invoke the `team-deliverables` skill for the PRD review report template.\n\n3. Score each dimension using the rubrics from `team-deliverables`:\n   - **Market Fit** (1-5): From market-fit-reviewer\n   - **Feasibility** (1-5): From feasibility-reviewer\n   - **Scope** (1-5): From scope-reviewer\n\n4. Compile blocking issues from all three reviewers.\n\n5. Document reviewer conflicts:\n   - Where scope-reviewer and market-fit-reviewer disagree on cuts\n   - Where feasibility-reviewer flags risks in market-critical features\n   - Provide resolution recommendation for each conflict\n\n6. Determine verdict:\n   - **READY TO BUILD**: All scores 4+, no blocking issues, conflicts resolved\n   - **NEEDS REVISION**: Average score 3+, blocking issues are fixable, no fundamental problems\n   - **MAJOR REWORK**: Any score below 2, or fundamental problems across dimensions\n\n7. Generate revision checklist:\n   - **Must Fix (Blocking)**: Issues from all reviewers marked as blocking\n   - **Should Fix (Important)**: Non-blocking but significant improvements\n   - **Nice to Fix (Polish)**: Minor improvements\n\n8. Present the completed report to the user.\n\n---\n\n### Phase 5: Cleanup\n\n1. Shut down all three teammates.\n\n2. Display completion:\n\n```\nPRD stress test complete.\n\nVerdict: [READY TO BUILD \u002F NEEDS REVISION \u002F MAJOR REWORK]\nScores: Market Fit [X]\u002F5 | Feasibility [X]\u002F5 | Scope [X]\u002F5\n\n[If NEEDS REVISION or MAJOR REWORK]:\nUse the revision checklist above to address the findings,\nthen run the stress test again to verify.\n```\n\n---\n\n## Error Handling\n\n- If a reviewer fails to produce output, note the gap in the report and proceed with available reviews.\n- If the PRD is very short or missing major sections, note this upfront but still run the review (the reviews will surface the gaps).\n- If the PRD file is not markdown, attempt to read it anyway and note any parsing issues.\n\n## Related\n\n- `\u002Fagent-teams:validation-sprint` - Validate the idea before writing a PRD\n- `\u002Fagent-teams:competitive-war-room` - Research competitors referenced in the PRD\n","# PRD Stress Test\n\nRun a multi-agent PRD review to answer: **\"Is this PRD ready to build?\"** Three reviewers analyze different dimensions in parallel, cross-reference findings, and deliver a consolidated review report.\n\n## Usage\n\n```bash\n\u002Fagent-teams:prd-stress-test path\u002Fto\u002Fprd.md\n```\n\n---\n\n## Overview\n\nThis command spawns three specialist reviewers to stress-test a PRD from different angles:\n\n- **market-fit-reviewer**: Does this solve a real problem for a real market?\n- **feasibility-reviewer**: Are the requirements clear and buildable?\n- **scope-reviewer**: Is this appropriately sized for V1?\n\nAfter parallel review, reviewers cross-reference findings to catch conflicts (e.g., scope-reviewer wants to cut a feature that market-fit-reviewer considers critical). The lead compiles everything into a consolidated review report with per-dimension scores and an actionable revision checklist.\n\n**What you get:**\n\n- Three independent review dimensions scored 1-5\n- Blocking issues (must fix before building)\n- Suggestions (nice to fix)\n- Conflicts between reviewers\n- Overall verdict: READY TO BUILD \u002F NEEDS REVISION \u002F MAJOR REWORK\n- Specific revision checklist\n\n---\n\n## PRD to Review\n\nRead the PRD at: $ARGUMENTS\n\n---\n\n## Instructions\n\n### Pre-Flight Check\n\n1. Verify Agent Teams is available in your Claude Code version.\n   If teammates cannot be spawned, display:\n\n   ```\n   This command requires Claude Code's Agent Teams feature.\n   Check https:\u002F\u002Fdocs.anthropic.com\u002Fen\u002Fdocs\u002Fclaude-code for setup instructions.\n   ```\n\n   If not available, stop.\n\n2. Read the PRD file from the path in the \"PRD to Review\" section above.\n   - If file not found, display error and stop:\n     ```\n     Error: PRD file not found at [path].\n     Please provide a valid path to a PRD markdown file.\n     ```\n\n---\n\n### Phase 1: PRD Intake\n\n1. Parse the PRD content and identify key sections (features, requirements, target users, etc.).\n\n2. Check for existing product context:\n   - Read `.claude\u002Fproduct-context\u002Fproduct-info.md` if it exists\n   - Read `.claude\u002Fproduct-context\u002Fcompetitive-landscape.md` if it exists\n\n3. Display briefing:\n\n```\n── PRD Stress Test ────────────────────────────────────────\n\nPRD: [file path]\nTitle: [extracted title or first heading]\n\nAssembling your review team:\n  1. market-fit-reviewer   → Market fit and differentiation\n  2. feasibility-reviewer  → Technical feasibility and requirements clarity\n  3. scope-reviewer        → Scope appropriateness and MVP sizing\n\nPhase 1: Parallel Review (3 reviewers working simultaneously)\nPhase 2: Cross-Reference (reviewers check each other's findings)\nPhase 3: Consolidated Report (verdict with revision checklist)\n\nStarting review...\n───────────────────────────────────────────────────────────\n```\n\n---\n\n### Phase 2: Parallel Review\n\nSpawn 3 teammates simultaneously using Agent Teams:\n\n**Teammate 1: market-fit-reviewer**\n\n```\nPrompt: \"Review this PRD for market fit. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\n[Include any product context found in Phase 1]\n\nYour job: Evaluate target user clarity, problem validation, value proposition,\ndifferentiation, and market context. Use your market-fit-reviewer expertise.\n\nDeliver your review in the standard market-fit-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\n**Teammate 2: feasibility-reviewer**\n\n```\nPrompt: \"Review this PRD for technical feasibility and requirements clarity. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\nYour job: Evaluate requirements clarity, acceptance criteria, technical\nfeasibility, edge cases, and integration points. Flag every ambiguity.\nUse your feasibility-reviewer expertise.\n\nDeliver your review in the standard feasibility-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\n**Teammate 3: scope-reviewer**\n\n```\nPrompt: \"Review this PRD for scope appropriateness. Score 1-5.\n\nPRD CONTENT:\n[full PRD content]\n\nYour job: Assess total scope, classify every feature as MUST-HAVE \u002F CUT FROM V1 \u002F\nDEFER TO V2, identify scope creep, and estimate effort reduction from cuts.\nUse your scope-reviewer expertise. Apply the 3-Feature MVP Rule.\n\nDeliver your review in the standard scope-reviewer output format.\nScore 1-5 using the team-deliverables rubric.\"\n```\n\nWait for all three reviewers to complete their reviews.\n\n---\n\n### Phase 3: Cross-Reference\n\nSend each reviewer the other two reviewers' findings to flag conflicts.\n\n**To market-fit-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nFEASIBILITY REVIEW:\n[feasibility-reviewer output]\n\nSCOPE REVIEW:\n[scope-reviewer output]\n\nSpecifically check:\n- Are features you consider critical for differentiation marked 'CUT' by scope-reviewer?\n- Do feasibility concerns affect market-critical features?\nFlag conflicts and explain your position.\"\n```\n\n**To feasibility-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nMARKET FIT REVIEW:\n[market-fit-reviewer output]\n\nSCOPE REVIEW:\n[scope-reviewer output]\n\nSpecifically check:\n- Do features market-fit-reviewer considers critical have clear requirements?\n- Do scope cuts remove technically risky components (positive) or create gaps?\nFlag conflicts and explain your position.\"\n```\n\n**To scope-reviewer:**\n\n```\n\"Here are your fellow reviewers' findings. Flag any conflicts with your review.\n\nMARKET FIT REVIEW:\n[market-fit-reviewer output]\n\nFEASIBILITY REVIEW:\n[feasibility-reviewer output]\n\nSpecifically check:\n- Are features you marked 'CUT' considered critical by market-fit-reviewer?\n- Do your cuts align with feasibility concerns?\nFlag conflicts and explain your position. Be willing to reconsider cuts if\nmarket-fit evidence is strong.\"\n```\n\nWait for all three cross-reference responses.\n\n---\n\n### Phase 4: Consolidated Report\n\nAs the lead agent, compile all findings into the PRD Review Report.\n\n1. Read all review reports and cross-reference responses.\n\n2. Invoke the `team-deliverables` skill for the PRD review report template.\n\n3. Score each dimension using the rubrics from `team-deliverables`:\n   - **Market Fit** (1-5): From market-fit-reviewer\n   - **Feasibility** (1-5): From feasibility-reviewer\n   - **Scope** (1-5): From scope-reviewer\n\n4. Compile blocking issues from all three reviewers.\n\n5. Document reviewer conflicts:\n   - Where scope-reviewer and market-fit-reviewer disagree on cuts\n   - Where feasibility-reviewer flags risks in market-critical features\n   - Provide resolution recommendation for each conflict\n\n6. Determine verdict:\n   - **READY TO BUILD**: All scores 4+, no blocking issues, conflicts resolved\n   - **NEEDS REVISION**: Average score 3+, blocking issues are fixable, no fundamental problems\n   - **MAJOR REWORK**: Any score below 2, or fundamental problems across dimensions\n\n7. Generate revision checklist:\n   - **Must Fix (Blocking)**: Issues from all reviewers marked as blocking\n   - **Should Fix (Important)**: Non-blocking but significant improvements\n   - **Nice to Fix (Polish)**: Minor improvements\n\n8. Present the completed report to the user.\n\n---\n\n### Phase 5: Cleanup\n\n1. Shut down all three teammates.\n\n2. Display completion:\n\n```\nPRD stress test complete.\n\nVerdict: [READY TO BUILD \u002F NEEDS REVISION \u002F MAJOR REWORK]\nScores: Market Fit [X]\u002F5 | Feasibility [X]\u002F5 | Scope [X]\u002F5\n\n[If NEEDS REVISION or MAJOR REWORK]:\nUse the revision checklist above to address the findings,\nthen run the stress test again to verify.\n```\n\n---\n\n## Error Handling\n\n- If a reviewer fails to produce output, note the gap in the report and proceed with available reviews.\n- If the PRD is very short or missing major sections, note this upfront but still run the review (the reviews will surface the gaps).\n- If the PRD file is not markdown, attempt to read it anyway and note any parsing issues.\n\n## Related\n\n- `\u002Fagent-teams:validation-sprint` - Validate the idea before writing a PRD\n- `\u002Fagent-teams:competitive-war-room` - Research competitors referenced in the PRD\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":24,"user-invocable":25,"disable-model-invocation":25},"Read, Glob, Grep, Task","\u003Cpath-to-prd.md>",true,"main","a4b48842f3e48549adf3dc335a8837c66da99497","agents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fprd-stress-test",0,"https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng","2026-05-17 16:00:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":25},[35,38,41],{"tool":36,"command":37},"npx","npx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill prd-stress-test",{"tool":39,"command":40},"bunx","bunx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill prd-stress-test",{"tool":42,"command":43},"pnpm","pnpm dlx skills add enigmaicon-eng\u002FAI-Enterprise-OS --skill prd-stress-test","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fagents\u002Fplugins\u002Fagent-teams\u002Fskills\u002Fprd-stress-test\u002FSKILL.md",[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72ZGWW03JSE1T3TKK5NZ11Y","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72ZGT3FJT7QRM1VNQRKR0XD","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72ZGQ69DCF0SBP9JXFPWKJS","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72ZGNF126QT0MQ2D3DNGZRN","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-superpowers\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72ZGHVJ9S0YXMNBHQGQ95BY","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72ZGFNZCHFY2FS3ZD9MCYV9","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Fenigmaicon-eng\u002FAI-Enterprise-OS\u002Fblob\u002Fmain\u002Fexamples\u002Fsuperpowers\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[]]