[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XDD36M09ATEN3FVPN28AP9":3,"skill-same:01M6XDD36M09ATEN3FVPN28AP9":106},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":63,"commitSha":64,"skillDirectory":65,"forksCount":14,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":6,"ownerDescription":68,"updatedAt":69,"install":70,"resources":83},"01M6XDD36M09ATEN3FVPN28AP9","pulumi-specialist",null,"Deep-dive Pulumi stack review, component design, Automation API audit, and secrets management. Use for structured investigations of Pulumi stack drift, ComponentResource coupling, ESC configuration, and Automation API workflows. Triggers on: \"Pulumi audit\", \"stack review\", \"Automation API review\", \"ComponentResource design\", \"ESC audit\", \"Pulumi secrets\", \"Pulumi testing\".","kaiohenricunha\u002Fdotbabel","kaiohenricunha","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F69804490?v=4","01M6XCZD37W0KPCDGEA40Y610V","Kaio Cunha","01M6XCZD7SX714D114H3ZPNW09",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002FSKILL.md",[18,23,26,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000032","设计师",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"pulumi specialist","specialist","pulumi","stack","problem","project","deep","drift","read","api workflows","testing","Bash","secrets","api","secrets management","audit","component","workflows","review","design","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:a1598cbe5673b19cf18bd5184f7076033b31b8a2ccc98d7e8b256f7bd13106a0 source=skills\u002Fpulumi-specialist\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash\nargument-hint: \u003Cstack name, project path, or problem description>\ndescription: |\n  Deep-dive Pulumi stack review, component design, Automation API audit, and secrets management. Use for structured investigations of Pulumi stack drift, ComponentResource coupling, ESC configuration, and Automation API workflows. Triggers on: \"Pulumi audit\", \"stack review\", \"Automation API review\", \"ComponentResource design\", \"ESC audit\", \"Pulumi secrets\", \"Pulumi testing\".\nname: pulumi-specialist\n---\n\n# Pulumi Specialist\n\nStructured investigation for Pulumi infrastructure codebases. Five phases:\ngather context, diagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — stack name, project path, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the Pulumi project:\n   ```bash\n   cat Pulumi.yaml\n   pulumi stack ls\n   ```\n2. Inspect the active stack config:\n   ```bash\n   pulumi config --show-secrets\n   pulumi stack output\n   ```\n3. Glob for Pulumi source files:\n   ```bash\n   find . -name \"*.ts\" -o -name \"*.py\" -o -name \"*.go\" | grep -v node_modules | sort\n   ```\n4. Check for Automation API usage:\n   ```bash\n   grep -r \"LocalWorkspace\\|RemoteWorkspace\\|createStack\\|selectStack\" . \\\n     --include=\"*.ts\" --include=\"*.py\" --include=\"*.go\" -l\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Stack health:**\n\n```bash\npulumi preview --diff\npulumi stack --show-ids\n```\n\n**Resource graph:**\n\n```bash\npulumi stack graph --dependency-graph \u002Ftmp\u002Fgraph.dot\ndot -Tsvg \u002Ftmp\u002Fgraph.dot -o \u002Ftmp\u002Fgraph.svg   # if graphviz available\n```\n\n**Secret exposure check:**\n\n```bash\npulumi config --show-secrets | grep -i \"key\\|secret\\|password\\|token\"\npulumi stack output --show-secrets\n```\n\n**Test coverage:**\n\n```bash\nfind . -name \"*.test.ts\" -o -name \"*_test.go\" -o -name \"test_*.py\" | sort\n```\n\n---\n\n## Phase 3: Design \u002F Root-Cause Analysis\n\nMap symptoms to causes:\n\n| Symptom                          | Common Causes                                      | Check                                          |\n| -------------------------------- | -------------------------------------------------- | ---------------------------------------------- |\n| Unexpected resource replace      | Input property changed that triggers replacement   | `pulumi preview --diff` — look for `[replace]` |\n| Stack output leaks secret        | Output not marked `secret: true`                   | `pulumi stack output --show-secrets`           |\n| ComponentResource missing output | Output not registered in `registerOutputs`         | Check `this.registerOutputs({...})` call       |\n| Automation API stack timeout     | Long provisioning, no timeout configured           | Add `OnEvent` handler + timeout options        |\n| ESC env not loaded               | `esc env open` not called; ESC not linked to stack | `pulumi config env ls`                         |\n\nCite `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003Clogical name or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Cpreview output or code snippet>\nFix: \u003Cspecific change, with code diff>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\nOrder: CRITICAL → WARNING → INFO.\n\n---\n\n## Phase 5: Verification\n\nAfter fixes are applied:\n\n1. `pulumi preview` — zero unexpected changes; no `[replace]` for unintended resources.\n2. `pulumi stack output` — no secrets in plaintext output.\n3. Unit tests pass: `npm test` \u002F `go test .\u002F...` \u002F `pytest`.\n4. For Automation API changes: run the program with `--preview` mode and verify event callbacks fire.\n5. For ESC changes: `esc env open \u003Corg>\u002F\u003Cproject>\u002F\u003Cenv>` and confirm values resolve correctly.\n\n---\n\n## Reference Docs\n\n| File                     | When to use                                                |\n| ------------------------ | ---------------------------------------------------------- |\n| `stack-design.md`        | Stack topology, StackReference, multi-stack patterns       |\n| `component-resources.md` | ComponentResource design, inputs\u002Foutputs, lifecycle        |\n| `automation-api.md`      | Embedding `pulumi up`\u002F`destroy` in Node\u002FPython\u002FGo          |\n| `secrets.md`             | Config secrets, ESC, output sensitivity, encryption        |\n| `testing.md`             | Unit mocks, integration tests, Automation API test harness |\n","# Pulumi Specialist\n\nStructured investigation for Pulumi infrastructure codebases. Five phases:\ngather context, diagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — stack name, project path, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. Identify the Pulumi project:\n   ```bash\n   cat Pulumi.yaml\n   pulumi stack ls\n   ```\n2. Inspect the active stack config:\n   ```bash\n   pulumi config --show-secrets\n   pulumi stack output\n   ```\n3. Glob for Pulumi source files:\n   ```bash\n   find . -name \"*.ts\" -o -name \"*.py\" -o -name \"*.go\" | grep -v node_modules | sort\n   ```\n4. Check for Automation API usage:\n   ```bash\n   grep -r \"LocalWorkspace\\|RemoteWorkspace\\|createStack\\|selectStack\" . \\\n     --include=\"*.ts\" --include=\"*.py\" --include=\"*.go\" -l\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Stack health:**\n\n```bash\npulumi preview --diff\npulumi stack --show-ids\n```\n\n**Resource graph:**\n\n```bash\npulumi stack graph --dependency-graph \u002Ftmp\u002Fgraph.dot\ndot -Tsvg \u002Ftmp\u002Fgraph.dot -o \u002Ftmp\u002Fgraph.svg   # if graphviz available\n```\n\n**Secret exposure check:**\n\n```bash\npulumi config --show-secrets | grep -i \"key\\|secret\\|password\\|token\"\npulumi stack output --show-secrets\n```\n\n**Test coverage:**\n\n```bash\nfind . -name \"*.test.ts\" -o -name \"*_test.go\" -o -name \"test_*.py\" | sort\n```\n\n---\n\n## Phase 3: Design \u002F Root-Cause Analysis\n\nMap symptoms to causes:\n\n| Symptom                          | Common Causes                                      | Check                                          |\n| -------------------------------- | -------------------------------------------------- | ---------------------------------------------- |\n| Unexpected resource replace      | Input property changed that triggers replacement   | `pulumi preview --diff` — look for `[replace]` |\n| Stack output leaks secret        | Output not marked `secret: true`                   | `pulumi stack output --show-secrets`           |\n| ComponentResource missing output | Output not registered in `registerOutputs`         | Check `this.registerOutputs({...})` call       |\n| Automation API stack timeout     | Long provisioning, no timeout configured           | Add `OnEvent` handler + timeout options        |\n| ESC env not loaded               | `esc env open` not called; ESC not linked to stack | `pulumi config env ls`                         |\n\nCite `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003Clogical name or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Cpreview output or code snippet>\nFix: \u003Cspecific change, with code diff>\nTrade-off: \u003Calternative and its downside, if meaningful>\n```\n\nOrder: CRITICAL → WARNING → INFO.\n\n---\n\n## Phase 5: Verification\n\nAfter fixes are applied:\n\n1. `pulumi preview` — zero unexpected changes; no `[replace]` for unintended resources.\n2. `pulumi stack output` — no secrets in plaintext output.\n3. Unit tests pass: `npm test` \u002F `go test .\u002F...` \u002F `pytest`.\n4. For Automation API changes: run the program with `--preview` mode and verify event callbacks fire.\n5. For ESC changes: `esc env open \u003Corg>\u002F\u003Cproject>\u002F\u003Cenv>` and confirm values resolve correctly.\n\n---\n\n## Reference Docs\n\n| File                     | When to use                                                |\n| ------------------------ | ---------------------------------------------------------- |\n| `stack-design.md`        | Stack topology, StackReference, multi-stack patterns       |\n| `component-resources.md` | ComponentResource design, inputs\u002Foutputs, lifecycle        |\n| `automation-api.md`      | Embedding `pulumi up`\u002F`destroy` in Node\u002FPython\u002FGo          |\n| `secrets.md`             | Config secrets, ESC, output sensitivity, encryption        |\n| `testing.md`             | Unit mocks, integration tests, Automation API test harness |\n",{"name":5,"description":60,"allowed-tools":61,"argument-hint":62},"Deep-dive Pulumi stack review, component design, Automation API audit, and secrets management. Use for structured investigations of Pulumi stack drift, ComponentResource coupling, ESC configuration, and Automation API workflows. Triggers on: \"Pulumi audit\", \"stack review\", \"Automation API review\", \"ComponentResource design\", \"ESC audit\", \"Pulumi secrets\", \"Pulumi testing\".\n","Read Grep Glob Bash","\u003Cstack name, project path, or problem description>","main","91c337164997b99943fbcc64e8e362577b67bc81","plugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha","I'm a Platform\u002FInfra engineer who happens to work in cybersec and write Go code.","2026-10-26 14:12:51",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill pulumi-specialist",{"tool":76,"command":77},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill pulumi-specialist",{"tool":79,"command":80},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill pulumi-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002FSKILL.md",true,[84,90,94,98,102],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fautomation-api.md","REFERENCE","参考文档",2799,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002Freferences\u002Fautomation-api.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fcomponent-resources.md",2891,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002Freferences\u002Fcomponent-resources.md",{"path":95,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fsecrets.md",2650,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002Freferences\u002Fsecrets.md",{"path":99,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Fstack-design.md",2661,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002Freferences\u002Fstack-design.md",{"path":103,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Ftesting.md",3097,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fplugins\u002Fdotbabel\u002Ftemplates\u002Fclaude\u002Fskills\u002Fpulumi-specialist\u002Freferences\u002Ftesting.md",[107,133,161,182,202,218],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":55},"01M6XDQ7QMASPFZ355MYKCD06T","yolo","Start temporary autonomy for the current task or an explicit scope with a required --for expiry. Codex permits scoped pushes, merges, deploys, and releases after strict testing and validation; Full access is a separate runtime setting. Claude Code uses a session permission hook with a protected-action denylist.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fyolo\u002FSKILL.md",[113],{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},[109,45,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132],"merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":145,"publishedAt":55},"01M6XDQ1N21VE4KH98JWGZ7GN9","veracity-audit","Audit a data pipeline for Veracity and Value. Dispatches data-scientist, compliance-auditor, and data-engineer agents with project context injected at dispatch time. All source paths are supplied via flags — no defaults, no project assumptions. Subcommands: audit (full pipeline walk), score-check (scoring math only), gate-check (gate coverage only), source-trace \u003Clabel> (single source end-to-end). Invoke when: \"audit pipeline\", \"veracity check\", \"scoring math correct?\", \"check gates\", \"trace source\", \"verify quality gates\", \"formula correct?\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fveracity-audit\u002FSKILL.md",[139,142],{"categoryNo":140,"categoryName":141,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":143,"categoryName":144,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000037","律师与法务",[50,146,45,53,147,148,46,149,150,151,152,153,154,155,40,156,157,158,159,160],"veracity audit","data pipeline","pipeline","math","coverage","only","engineer","formula","scoring","time","worker","end","at","invoke","when",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"publishedAt":55},"01M6XDPVDKBR376C06CEK9BC5S","validate-spec","Audit an already-implemented spec against the codebase. Walks each constraint (ARCH-N, PERF-N, KD-N, etc.) and acceptance criterion, grounds findings in file:line evidence, runs the spec.json acceptance_commands, and writes a single audit doc to docs\u002Faudits\u002F. Use whenever the user asks to \"validate a spec\", \"audit a spec\", \"check if spec is implemented\", \"verify the spec is done\", \"is this spec really done\", or otherwise wants closure on spec-driven work. Read-only against the spec — produces an audit, never modifies the spec itself.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fvalidate-spec\u002FSKILL.md",[],[168,169,170,45,53,171,172,50,46,173,43,174,151,175,176,177,178,179,180,181],"spec","validate","validate spec","run","acceptance","work","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":191,"publishedAt":55},"01M6XDPMMECH82RAW553Y94HDS","terragrunt-specialist","Deep-dive Terragrunt hierarchy review, DRY pattern audits, and run-all orchestration analysis. Use for structured investigations of multi-environment Terragrunt layouts, dependency graphs, remote state config, and hook correctness. Triggers on: \"Terragrunt audit\", \"run-all review\", \"dependency block\", \"DRY pattern review\", \"env hierarchy audit\", \"mock_outputs\", \"terragrunt hooks\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterragrunt-specialist\u002FSKILL.md",[188],{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[192,36,193,53,194,195,171,50,196,46,43,197,198,175,41,199,179,200,158,201],"terragrunt","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","dry","remote","hierarchy",{"skillNo":203,"name":204,"nameZh":6,"description":205,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":206,"categories":207,"keywords":211,"publishedAt":55},"01M6XDPFJS2HGSE13RXF1HV8S7","terraform-specialist","Deep-dive Terraform architecture review, module design, state management, and migration. Use for structured investigations of Terraform workspaces, provider configuration, module coupling, import workflows, and test coverage. Triggers on: \"Terraform audit\", \"module review\", \"state management\", \"Terraform import\", \"workspace design\", \"provider config review\", \"Terraform testing\".","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fterraform-specialist\u002FSKILL.md",[208,209,210],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":189,"categoryName":190,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,36,45,54,53,52,214,215,195,50,46,43,150,216,217,41,39,179,158],"terraform","terraform specialist","architecture","architecture review","test coverage","workspaces",{"skillNo":219,"name":168,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":221,"categories":222,"keywords":225,"publishedAt":55},"01M6XDP7V6H8WYPSXVEKYE6HJ6","Create structured engineering specs through interactive pairing. Use when the user wants to create a spec, design doc, technical specification, architecture document, RFC, or engineering plan. Triggers on \"let's spec this out\", \"create a spec\", \"design doc\", \"write a technical plan\", \"plan the architecture\". Works for greenfield and brownfield projects. Outputs to docs\u002Fspecs\u002F.","https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fskills\u002Fspec\u002FSKILL.md",[223,224],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":32,"categoryName":33,"taxonomyType":29,"taxonomyTypeDesc":30},[168,54,51,214,226,227,228,229,230,231,232,233,234,235,236,131,237,238,239,240],"create","plan","projects","write","interactive","use","document","specification","triggers","opus","technical specification","trade-offs","technical plan","outputs","frontier"]