[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FMF11MNSHT2Y5R2CGYG07":3,"skill-same:01M70FMF11MNSHT2Y5R2CGYG07":73},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M70FMF11MNSHT2Y5R2CGYG07","architecture-decision-records",null,"Capture architectural decisions as numbered ADR markdown files in docs\u002Fadr\u002F with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.","mdnaimul22\u002Fhuman-skills","mdnaimul22","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64520358?v=4","01M70FH95MH2H796Q01TYSFZ03","Naimul","01M70FH96798CQR4YHA13F17GA",3,"MIT","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Farchitecture-decision-records\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"architecture decision records","architecture","decision","architecture decision","records","when","alternatives","trade-offs","with","as","frameworks","files","databases","use","context","README","decisions","adr","markdown","why","2026-11-10 10:12:30",false,"---\nname: architecture-decision-records\ndescription: Capture architectural decisions as numbered ADR markdown files in docs\u002Fadr\u002F with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.\nmetadata:\n  origin: ECC\n---\n\n# Architecture Decision Records\n\nCapture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.\n\n## When to Activate\n\n- User explicitly says \"let's record this decision\" or \"ADR this\"\n- User chooses between significant alternatives (framework, library, pattern, database, API design)\n- User says \"we decided to...\" or \"the reason we're doing X instead of Y is...\"\n- User asks \"why did we choose X?\" (read existing ADRs)\n- During planning phases when architectural trade-offs are discussed\n\n## ADR Format\n\nUse the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development:\n\n```markdown\n# ADR-NNNN: [Decision Title]\n\n**Date**: YYYY-MM-DD\n**Status**: proposed | accepted | deprecated | superseded by ADR-NNNN\n**Deciders**: [who was involved]\n\n## Context\n\nWhat is the issue that we're seeing that is motivating this decision or change?\n\n[2-5 sentences describing the situation, constraints, and forces at play]\n\n## Decision\n\nWhat is the change that we're proposing and\u002For doing?\n\n[1-3 sentences stating the decision clearly]\n\n## Alternatives Considered\n\n### Alternative 1: [Name]\n- **Pros**: [benefits]\n- **Cons**: [drawbacks]\n- **Why not**: [specific reason this was rejected]\n\n### Alternative 2: [Name]\n- **Pros**: [benefits]\n- **Cons**: [drawbacks]\n- **Why not**: [specific reason this was rejected]\n\n## Consequences\n\nWhat becomes easier or more difficult to do because of this change?\n\n### Positive\n- [benefit 1]\n- [benefit 2]\n\n### Negative\n- [trade-off 1]\n- [trade-off 2]\n\n### Risks\n- [risk and mitigation]\n```\n\n## Workflow\n\n### Capturing a New ADR\n\nWhen a decision moment is detected:\n\n1. **Initialize (first time only)** — if `docs\u002Fadr\u002F` does not exist, ask the user for confirmation before creating the directory, a `README.md` seeded with the index table header (see ADR Index Format below), and a blank `template.md` for manual use. Do not create files without explicit consent.\n2. **Identify the decision** — extract the core architectural choice being made\n3. **Gather context** — what problem prompted this? What constraints exist?\n4. **Document alternatives** — what other options were considered? Why were they rejected?\n5. **State consequences** — what are the trade-offs? What becomes easier\u002Fharder?\n6. **Assign a number** — scan existing ADRs in `docs\u002Fadr\u002F` and increment\n7. **Confirm and write** — present the draft ADR to the user for review. Only write to `docs\u002Fadr\u002FNNNN-decision-title.md` after explicit approval. If the user declines, discard the draft without writing any files.\n8. **Update the index** — append to `docs\u002Fadr\u002FREADME.md`\n\n### Reading Existing ADRs\n\nWhen a user asks \"why did we choose X?\":\n\n1. Check if `docs\u002Fadr\u002F` exists — if not, respond: \"No ADRs found in this project. Would you like to start recording architectural decisions?\"\n2. If it exists, scan `docs\u002Fadr\u002FREADME.md` index for relevant entries\n3. Read matching ADR files and present the Context and Decision sections\n4. If no match is found, respond: \"No ADR found for that decision. Would you like to record one now?\"\n\n### ADR Directory Structure\n\n```\ndocs\u002F\n└── adr\u002F\n    ├── README.md              ← index of all ADRs\n    ├── 0001-use-nextjs.md\n    ├── 0002-postgres-over-mongo.md\n    ├── 0003-rest-over-graphql.md\n    └── template.md            ← blank template for manual use\n```\n\n### ADR Index Format\n\n```markdown\n# Architecture Decision Records\n\n| ADR | Title | Status | Date |\n|-----|-------|--------|------|\n| [0001](0001-use-nextjs.md) | Use Next.js as frontend framework | accepted | 2026-01-15 |\n| [0002](0002-postgres-over-mongo.md) | PostgreSQL over MongoDB for primary datastore | accepted | 2026-01-20 |\n| [0003](0003-rest-over-graphql.md) | REST API over GraphQL | accepted | 2026-02-01 |\n```\n\n## Decision Detection Signals\n\nWatch for these patterns in conversation that indicate an architectural decision:\n\n**Explicit signals**\n- \"Let's go with X\"\n- \"We should use X instead of Y\"\n- \"The trade-off is worth it because...\"\n- \"Record this as an ADR\"\n\n**Implicit signals** (suggest recording an ADR — do not auto-create without user confirmation)\n- Comparing two frameworks or libraries and reaching a conclusion\n- Making a database schema design choice with stated rationale\n- Choosing between architectural patterns (monolith vs microservices, REST vs GraphQL)\n- Deciding on authentication\u002Fauthorization strategy\n- Selecting deployment infrastructure after evaluating alternatives\n\n## What Makes a Good ADR\n\n### Do\n- **Be specific** — \"Use Prisma ORM\" not \"use an ORM\"\n- **Record the why** — the rationale matters more than the what\n- **Include rejected alternatives** — future developers need to know what was considered\n- **State consequences honestly** — every decision has trade-offs\n- **Keep it short** — an ADR should be readable in 2 minutes\n- **Use present tense** — \"We use X\" not \"We will use X\"\n\n### Don't\n- Record trivial decisions — variable naming or formatting choices don't need ADRs\n- Write essays — if the context section exceeds 10 lines, it's too long\n- Omit alternatives — \"we just picked it\" is not a valid rationale\n- Backfill without marking it — if recording a past decision, note the original date\n- Let ADRs go stale — superseded decisions should reference their replacement\n\n## ADR Lifecycle\n\n```\nproposed → accepted → [deprecated | superseded by ADR-NNNN]\n```\n\n- **proposed**: decision is under discussion, not yet committed\n- **accepted**: decision is in effect and being followed\n- **deprecated**: decision is no longer relevant (e.g., feature removed)\n- **superseded**: a newer ADR replaces this one (always link the replacement)\n\n## Categories of Decisions Worth Recording\n\n| Category | Examples |\n|----------|---------|\n| **Technology choices** | Framework, language, database, cloud provider |\n| **Architecture patterns** | Monolith vs microservices, event-driven, CQRS |\n| **API design** | REST vs GraphQL, versioning strategy, auth mechanism |\n| **Data modeling** | Schema design, normalization decisions, caching strategy |\n| **Infrastructure** | Deployment model, CI\u002FCD pipeline, monitoring stack |\n| **Security** | Auth strategy, encryption approach, secret management |\n| **Testing** | Test framework, coverage targets, E2E vs integration balance |\n| **Process** | Branching strategy, review process, release cadence |\n\n## Integration with Other Skills\n\n- **Planner agent**: when the planner proposes architecture changes, suggest creating an ADR\n- **Code reviewer agent**: flag PRs that introduce architectural changes without a corresponding ADR\n","# Architecture Decision Records\n\nCapture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.\n\n## When to Activate\n\n- User explicitly says \"let's record this decision\" or \"ADR this\"\n- User chooses between significant alternatives (framework, library, pattern, database, API design)\n- User says \"we decided to...\" or \"the reason we're doing X instead of Y is...\"\n- User asks \"why did we choose X?\" (read existing ADRs)\n- During planning phases when architectural trade-offs are discussed\n\n## ADR Format\n\nUse the lightweight ADR format proposed by Michael Nygard, adapted for AI-assisted development:\n\n```markdown\n# ADR-NNNN: [Decision Title]\n\n**Date**: YYYY-MM-DD\n**Status**: proposed | accepted | deprecated | superseded by ADR-NNNN\n**Deciders**: [who was involved]\n\n## Context\n\nWhat is the issue that we're seeing that is motivating this decision or change?\n\n[2-5 sentences describing the situation, constraints, and forces at play]\n\n## Decision\n\nWhat is the change that we're proposing and\u002For doing?\n\n[1-3 sentences stating the decision clearly]\n\n## Alternatives Considered\n\n### Alternative 1: [Name]\n- **Pros**: [benefits]\n- **Cons**: [drawbacks]\n- **Why not**: [specific reason this was rejected]\n\n### Alternative 2: [Name]\n- **Pros**: [benefits]\n- **Cons**: [drawbacks]\n- **Why not**: [specific reason this was rejected]\n\n## Consequences\n\nWhat becomes easier or more difficult to do because of this change?\n\n### Positive\n- [benefit 1]\n- [benefit 2]\n\n### Negative\n- [trade-off 1]\n- [trade-off 2]\n\n### Risks\n- [risk and mitigation]\n```\n\n## Workflow\n\n### Capturing a New ADR\n\nWhen a decision moment is detected:\n\n1. **Initialize (first time only)** — if `docs\u002Fadr\u002F` does not exist, ask the user for confirmation before creating the directory, a `README.md` seeded with the index table header (see ADR Index Format below), and a blank `template.md` for manual use. Do not create files without explicit consent.\n2. **Identify the decision** — extract the core architectural choice being made\n3. **Gather context** — what problem prompted this? What constraints exist?\n4. **Document alternatives** — what other options were considered? Why were they rejected?\n5. **State consequences** — what are the trade-offs? What becomes easier\u002Fharder?\n6. **Assign a number** — scan existing ADRs in `docs\u002Fadr\u002F` and increment\n7. **Confirm and write** — present the draft ADR to the user for review. Only write to `docs\u002Fadr\u002FNNNN-decision-title.md` after explicit approval. If the user declines, discard the draft without writing any files.\n8. **Update the index** — append to `docs\u002Fadr\u002FREADME.md`\n\n### Reading Existing ADRs\n\nWhen a user asks \"why did we choose X?\":\n\n1. Check if `docs\u002Fadr\u002F` exists — if not, respond: \"No ADRs found in this project. Would you like to start recording architectural decisions?\"\n2. If it exists, scan `docs\u002Fadr\u002FREADME.md` index for relevant entries\n3. Read matching ADR files and present the Context and Decision sections\n4. If no match is found, respond: \"No ADR found for that decision. Would you like to record one now?\"\n\n### ADR Directory Structure\n\n```\ndocs\u002F\n└── adr\u002F\n    ├── README.md              ← index of all ADRs\n    ├── 0001-use-nextjs.md\n    ├── 0002-postgres-over-mongo.md\n    ├── 0003-rest-over-graphql.md\n    └── template.md            ← blank template for manual use\n```\n\n### ADR Index Format\n\n```markdown\n# Architecture Decision Records\n\n| ADR | Title | Status | Date |\n|-----|-------|--------|------|\n| [0001](0001-use-nextjs.md) | Use Next.js as frontend framework | accepted | 2026-01-15 |\n| [0002](0002-postgres-over-mongo.md) | PostgreSQL over MongoDB for primary datastore | accepted | 2026-01-20 |\n| [0003](0003-rest-over-graphql.md) | REST API over GraphQL | accepted | 2026-02-01 |\n```\n\n## Decision Detection Signals\n\nWatch for these patterns in conversation that indicate an architectural decision:\n\n**Explicit signals**\n- \"Let's go with X\"\n- \"We should use X instead of Y\"\n- \"The trade-off is worth it because...\"\n- \"Record this as an ADR\"\n\n**Implicit signals** (suggest recording an ADR — do not auto-create without user confirmation)\n- Comparing two frameworks or libraries and reaching a conclusion\n- Making a database schema design choice with stated rationale\n- Choosing between architectural patterns (monolith vs microservices, REST vs GraphQL)\n- Deciding on authentication\u002Fauthorization strategy\n- Selecting deployment infrastructure after evaluating alternatives\n\n## What Makes a Good ADR\n\n### Do\n- **Be specific** — \"Use Prisma ORM\" not \"use an ORM\"\n- **Record the why** — the rationale matters more than the what\n- **Include rejected alternatives** — future developers need to know what was considered\n- **State consequences honestly** — every decision has trade-offs\n- **Keep it short** — an ADR should be readable in 2 minutes\n- **Use present tense** — \"We use X\" not \"We will use X\"\n\n### Don't\n- Record trivial decisions — variable naming or formatting choices don't need ADRs\n- Write essays — if the context section exceeds 10 lines, it's too long\n- Omit alternatives — \"we just picked it\" is not a valid rationale\n- Backfill without marking it — if recording a past decision, note the original date\n- Let ADRs go stale — superseded decisions should reference their replacement\n\n## ADR Lifecycle\n\n```\nproposed → accepted → [deprecated | superseded by ADR-NNNN]\n```\n\n- **proposed**: decision is under discussion, not yet committed\n- **accepted**: decision is in effect and being followed\n- **deprecated**: decision is no longer relevant (e.g., feature removed)\n- **superseded**: a newer ADR replaces this one (always link the replacement)\n\n## Categories of Decisions Worth Recording\n\n| Category | Examples |\n|----------|---------|\n| **Technology choices** | Framework, language, database, cloud provider |\n| **Architecture patterns** | Monolith vs microservices, event-driven, CQRS |\n| **API design** | REST vs GraphQL, versioning strategy, auth mechanism |\n| **Data modeling** | Schema design, normalization decisions, caching strategy |\n| **Infrastructure** | Deployment model, CI\u002FCD pipeline, monitoring stack |\n| **Security** | Auth strategy, encryption approach, secret management |\n| **Testing** | Test framework, coverage targets, E2E vs integration balance |\n| **Process** | Branching strategy, review process, release cadence |\n\n## Integration with Other Skills\n\n- **Planner agent**: when the planner proposes architecture changes, suggest creating an ADR\n- **Code reviewer agent**: flag PRs that introduce architectural changes without a corresponding ADR\n",{"name":5,"metadata":49,"description":7},{"origin":50},"ECC","main","74715deacdc69119d739f38916f8ee4f0f979ebf","skills\u002Fstorage\u002Faffaan-m_ECC\u002Farchitecture-decision-records",0,"https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills","https:\u002F\u002Fgithub.com\u002Fmdnaimul22","AI Agents Workflows Automation | Specializing in Python, FastAPI, MCP Agents & Custom ERP.","2026-11-11 21:16:57",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add mdnaimul22\u002Fhuman-skills --skill architecture-decision-records",{"tool":65,"command":66},"bunx","bunx skills add mdnaimul22\u002Fhuman-skills --skill architecture-decision-records",{"tool":68,"command":69},"pnpm","pnpm dlx skills add mdnaimul22\u002Fhuman-skills --skill architecture-decision-records","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Faffaan-m_ECC\u002Farchitecture-decision-records\u002FSKILL.md",true,[],[74,82,108,130,149,164],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":81},"01M72JT3YP1SQHD0MANGDXQ4RT","higgsfield-websites","Build, edit, and deploy full-stack websites, apps and games via the Higgsfield CLI (`higgsfield website …`). Each is a React 19 + TanStack Start SSR app in one Cloudflare Worker (D1\u002FR2\u002FKV\u002FDO\u002FContainers). THREE product types, picked via `--type` on create: `website` (standalone, no Higgsfield integration — references\u002Fwebsite-flow.md), `app` (Sign in with Higgsfield + fnf SDK, Quanta — references\u002Fapp-flow.md), `game` (realtime multiplayer rooms — references\u002Fgame-flow.md). Routes to the right flow; each carries its own rules and deploy\u002Fpublish gates.\nUse when: \"build me a website\", \"make a landing page\", \"create a web app\", \"build a SaaS dashboard \u002F portfolio\", \"make me a game\", \"deploy this site\", \"publish\". Also owns GAME ART: \"make a spritesheet\", \"tileable texture\", \"animate a 3D character\", game music\u002FSFX — see the game-* references.\nNOT for: single image\u002Fvideo\u002Faudio generation (higgsfield-generate), product photos (higgsfield-product-photoshoot), marketplace cards (higgsfield-marketplace-cards).","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fhiggsfield-ai_skills\u002Fhiggsfield-websites\u002FSKILL.md",[],[],"2026-11-10 22:39:42",{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":100,"publishedAt":44},"01M70JPK8HAXXA85P7Q8NKZZYG","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-skills\u002FSKILL.md",[88,91,96,97],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":98,"categoryName":99,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[101,102,103,104,37,105,106,29,107],"writing","writing skills","editing","deployment","Existing","new","work",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":119,"publishedAt":44},"01M70JP4PHBH1CQVVDWZ94W159","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fwriting-plans\u002FSKILL.md",[114,115,116],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},{"categoryNo":117,"categoryName":118,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师",[101,120,121,122,29,123,124,37,125,126,127,128,129],"writing plans","plans","you","code","for","requirements","task","multi","spec","multi-step task",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":44},"01M70JNTYVGXFZT8PASZ844TH8","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\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fverification-before-completion\u002FSKILL.md",[],[137,138,139,140,141,142,37,143,144,145,29,146,107,147,148],"verification","verification before completion","complete","about","output","assertions","prs","evidence","claim","claims","commands","running",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":44},"01M70JNGVSQDESWN0Q5BPJ875V","using-superpowers","Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions","https:\u002F\u002Fgithub.com\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-superpowers\u002FSKILL.md",[155],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,158,159,160,37,29,161,162,163],"using superpowers","superpowers","conversation","how to","how","find","questions",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":44},"01M70JN57CE588NPYPYTWH1DWG","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\u002Fmdnaimul22\u002Fhuman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fstorage\u002Fobra_superpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[171,172,173,174,175,176,29,107,177,178,179,180,181,182,183,121,37,184,185],"using git worktrees","Using git","git","worktrees","git worktrees","implementation","git worktree","worktree","native","Tools","isolation","fallback","feature","via","workspace"]