[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD2F16ZSWCCNXJSHXKRYSK":3,"skill-same:01M6XD2F16ZSWCCNXJSHXKRYSK":103},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":14,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":6,"ownerDescription":65,"updatedAt":66,"install":67,"resources":80},"01M6XD2F16ZSWCCNXJSHXKRYSK","crossplane-specialist",null,"Deep-dive Crossplane platform review: XRD design, Composition correctness, provider config audit, managed resource health, and GitOps integration. Use for structured investigations of stuck Claims, composition pipeline bugs, and credential injection patterns. Triggers on: \"Crossplane audit\", \"XRD review\", \"Composition debug\", \"stuck Claim\", \"managed resource stuck\", \"provider config review\", \"Crossplane GitOps\".","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\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"crossplane specialist","specialist","crossplane","patterns","investigations","managed","claims","problem","deep","claim","design","config audit","read","Bash","Composition","injection","pipeline","audit","config","review","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:f0e7c91a4a4b115b4f0c02f86ff8d81d704405df0076984c0d4e82fd9ba5c228 source=skills\u002Fcrossplane-specialist\u002FSKILL.md — do not edit directly\nallowed-tools: Read Grep Glob Bash\nargument-hint: \u003CXRD name, Claim name, or problem description>\ndescription: |\n  Deep-dive Crossplane platform review: XRD design, Composition correctness, provider config audit, managed resource health, and GitOps integration. Use for structured investigations of stuck Claims, composition pipeline bugs, and credential injection patterns. Triggers on: \"Crossplane audit\", \"XRD review\", \"Composition debug\", \"stuck Claim\", \"managed resource stuck\", \"provider config review\", \"Crossplane GitOps\".\nname: crossplane-specialist\n---\n\n# Crossplane Specialist\n\nStructured investigation for Crossplane-based infrastructure platforms. Five phases:\ngather context, diagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — XRD name, Claim name, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. List installed providers and packages:\n   ```bash\n   kubectl get providers\n   kubectl get configurations\n   kubectl get functions\n   ```\n2. List XRDs and their ready status:\n   ```bash\n   kubectl get xrd\n   ```\n3. List Claims and Composites:\n   ```bash\n   kubectl get composite --all-namespaces\n   kubectl get claim --all-namespaces\n   ```\n4. Glob for Crossplane manifests in the working directory:\n   ```bash\n   find . -name \"*.yaml\" | xargs grep -l \"apiVersion: apiextensions.crossplane.io\" | sort\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Stuck Claim \u002F Composite trace:**\n\n```bash\nkubectl describe claim \u003Cname> -n \u003Cnamespace>\nkubectl describe composite \u003Cname>\nkubectl get managed --all-namespaces | grep -v \"True\"\nkubectl describe \u003Cmanaged-resource-kind> \u003Cname>\n```\n\n**Provider health:**\n\n```bash\nkubectl describe provider \u003Cname>\nkubectl get providerconfig\nkubectl describe providerconfig \u003Cname>\n```\n\n**Composition pipeline:**\n\n```bash\nkubectl get composition \u003Cname> -o yaml\nkubectl get function --all-namespaces\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| Claim stuck `Waiting`       | Composite not ready, no matching Composition          | `kubectl describe composite` → events          |\n| Managed resource `NotFound` | Wrong external-name annotation, ID mismatch           | Provider docs for external-name format         |\n| Provider `Unhealthy`        | Bad credentials, missing `ProviderConfig`             | `kubectl describe provider` events             |\n| Composition patch fails     | Wrong `fromFieldPath`, type mismatch                  | `kubectl get composite -o yaml` patched fields |\n| Function pipeline error     | Function pod crash, malformed `FunctionIO`            | `kubectl logs -n crossplane-system` function   |\n| Deletion stuck (finalizer)  | Managed resource `Delete` policy, cloud resource busy | Check deletion policy + cloud console          |\n\nCite `kind:name` or `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003Ckind:name or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Ckubectl output or config snippet>\nFix: \u003Cspecific change, with YAML diff if applicable>\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. `kubectl get composite \u003Cname>` — `READY: True`, `SYNCED: True`.\n2. `kubectl get managed` — all managed resources show `READY: True`.\n3. `kubectl describe claim \u003Cname>` — no error events.\n4. `kubectl apply --dry-run=server -f composition.yaml` — no schema errors.\n5. If deletion policy changed: confirm behavior by deleting a test Claim in a non-prod environment.\n\n---\n\n## Reference Docs\n\n| File                    | When to use                                               |\n| ----------------------- | --------------------------------------------------------- |\n| `xrd-design.md`         | XRD schema design, versioning, validation rules           |\n| `compositions.md`       | Composition patch-and-transform, pipeline mode, Functions |\n| `provider-configs.md`   | Credential injection, `ProviderConfig` patterns           |\n| `managed-resources.md`  | External-name, deletion policy, resource lifecycle        |\n| `gitops-integration.md` | Argo CD \u002F Flux health checks, package management          |\n","# Crossplane Specialist\n\nStructured investigation for Crossplane-based infrastructure platforms. Five phases:\ngather context, diagnose, design, recommend, verify.\n\n## Arguments\n\n- `$0` — XRD name, Claim name, or problem description. Required.\n\n---\n\n## Phase 1: Context Gathering\n\n1. List installed providers and packages:\n   ```bash\n   kubectl get providers\n   kubectl get configurations\n   kubectl get functions\n   ```\n2. List XRDs and their ready status:\n   ```bash\n   kubectl get xrd\n   ```\n3. List Claims and Composites:\n   ```bash\n   kubectl get composite --all-namespaces\n   kubectl get claim --all-namespaces\n   ```\n4. Glob for Crossplane manifests in the working directory:\n   ```bash\n   find . -name \"*.yaml\" | xargs grep -l \"apiVersion: apiextensions.crossplane.io\" | sort\n   ```\n\n---\n\n## Phase 2: Diagnosis\n\n**Stuck Claim \u002F Composite trace:**\n\n```bash\nkubectl describe claim \u003Cname> -n \u003Cnamespace>\nkubectl describe composite \u003Cname>\nkubectl get managed --all-namespaces | grep -v \"True\"\nkubectl describe \u003Cmanaged-resource-kind> \u003Cname>\n```\n\n**Provider health:**\n\n```bash\nkubectl describe provider \u003Cname>\nkubectl get providerconfig\nkubectl describe providerconfig \u003Cname>\n```\n\n**Composition pipeline:**\n\n```bash\nkubectl get composition \u003Cname> -o yaml\nkubectl get function --all-namespaces\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| Claim stuck `Waiting`       | Composite not ready, no matching Composition          | `kubectl describe composite` → events          |\n| Managed resource `NotFound` | Wrong external-name annotation, ID mismatch           | Provider docs for external-name format         |\n| Provider `Unhealthy`        | Bad credentials, missing `ProviderConfig`             | `kubectl describe provider` events             |\n| Composition patch fails     | Wrong `fromFieldPath`, type mismatch                  | `kubectl get composite -o yaml` patched fields |\n| Function pipeline error     | Function pod crash, malformed `FunctionIO`            | `kubectl logs -n crossplane-system` function   |\n| Deletion stuck (finalizer)  | Managed resource `Delete` policy, cloud resource busy | Check deletion policy + cloud console          |\n\nCite `kind:name` or `file:line` for every finding.\n\n---\n\n## Phase 4: Recommendations\n\nOutput findings in priority order:\n\n```\n[CRITICAL] \u003Ctitle>\nResource: \u003Ckind:name or file:line>\nIssue: \u003Cone sentence>\nEvidence: \u003Ckubectl output or config snippet>\nFix: \u003Cspecific change, with YAML diff if applicable>\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. `kubectl get composite \u003Cname>` — `READY: True`, `SYNCED: True`.\n2. `kubectl get managed` — all managed resources show `READY: True`.\n3. `kubectl describe claim \u003Cname>` — no error events.\n4. `kubectl apply --dry-run=server -f composition.yaml` — no schema errors.\n5. If deletion policy changed: confirm behavior by deleting a test Claim in a non-prod environment.\n\n---\n\n## Reference Docs\n\n| File                    | When to use                                               |\n| ----------------------- | --------------------------------------------------------- |\n| `xrd-design.md`         | XRD schema design, versioning, validation rules           |\n| `compositions.md`       | Composition patch-and-transform, pipeline mode, Functions |\n| `provider-configs.md`   | Credential injection, `ProviderConfig` patterns           |\n| `managed-resources.md`  | External-name, deletion policy, resource lifecycle        |\n| `gitops-integration.md` | Argo CD \u002F Flux health checks, package management          |\n",{"name":5,"description":57,"allowed-tools":58,"argument-hint":59},"Deep-dive Crossplane platform review: XRD design, Composition correctness, provider config audit, managed resource health, and GitOps integration. Use for structured investigations of stuck Claims, composition pipeline bugs, and credential injection patterns. Triggers on: \"Crossplane audit\", \"XRD review\", \"Composition debug\", \"stuck Claim\", \"managed resource stuck\", \"provider config review\", \"Crossplane GitOps\".\n","Read Grep Glob Bash","\u003CXRD name, Claim name, or problem description>","main","91c337164997b99943fbcc64e8e362577b67bc81","examples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-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":68,"prompt":78,"zipAvailable":79},[69,72,75],{"tool":70,"command":71},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill crossplane-specialist",{"tool":73,"command":74},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill crossplane-specialist",{"tool":76,"command":77},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill crossplane-specialist","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002FSKILL.md",true,[81,87,91,95,99],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fcompositions.md","REFERENCE","参考文档",2788,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002Freferences\u002Fcompositions.md",{"path":88,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":89,"sourceHtmlUrl":90},"references\u002Fgitops-integration.md",2907,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002Freferences\u002Fgitops-integration.md",{"path":92,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":93,"sourceHtmlUrl":94},"references\u002Fmanaged-resources.md",2706,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002Freferences\u002Fmanaged-resources.md",{"path":96,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fprovider-configs.md",2645,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002Freferences\u002Fprovider-configs.md",{"path":100,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fxrd-design.md",2709,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fcrossplane-specialist\u002Freferences\u002Fxrd-design.md",[104,131,159,180,200,219],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":52},"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",[110],{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[106,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","scope","devex","hook","true","action","for","scoped",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":143,"publishedAt":52},"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",[137,140],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":141,"categoryName":142,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000037","律师与法务",[49,144,112,51,145,48,45,146,147,148,149,150,151,152,153,154,155,156,157,158],"veracity audit","data pipeline","math","coverage","only","engineer","formula","scoring","time","project","worker","end","at","invoke","when",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":52},"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",[],[166,167,168,112,51,169,170,49,45,171,44,172,148,173,174,175,176,177,178,179],"spec","validate","validate spec","run","acceptance","work","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":181,"name":182,"nameZh":6,"description":183,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":184,"categories":185,"keywords":189,"publishedAt":52},"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",[186],{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[190,33,191,51,192,193,169,49,194,45,44,195,196,173,40,197,177,198,156,199],"terragrunt","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","dry","remote","hierarchy",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":211,"publishedAt":52},"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",[206,209,210],{"categoryNo":207,"categoryName":208,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":187,"categoryName":188,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[212,213,33,112,42,51,214,215,216,193,49,45,44,147,217,218,40,39,177,156],"terraform","terraform specialist","workflows","architecture","architecture review","test coverage","workspaces",{"skillNo":220,"name":166,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":226,"publishedAt":52},"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",[224,225],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},[166,42,227,215,228,229,230,231,232,233,234,235,236,237,238,129,239,240,241,242],"component","create","plan","projects","write","interactive","use","document","specification","triggers","opus","technical specification","trade-offs","technical plan","outputs","frontier"]