[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XD5MKQ2VGPXR16DFNER25F":3,"skill-same:01M6XD5MKQ2VGPXR16DFNER25F":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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":14,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6XD5MKQ2VGPXR16DFNER25F","project-sync",null,"Fan out the current repo's CLAUDE.md, .claude\u002Fcommands, and .claude\u002Fskills into Codex, Gemini, and Copilot project-scope analogues (.codex\u002Fskills, .gemini\u002Fskills, .github\u002Fprompts, .github\u002Finstructions) plus refresh AGENTS.md, GEMINI.md, and .github\u002Fcopilot-instructions.md from the project's rule floor. Wraps `dotbabel project-sync`. Use when adopting cross-CLI workflows in a repo for the first time, or when adding a new command\u002Fskill that needs to be visible to Codex\u002FGemini\u002FCopilot. Triggers on: \"sync this repo\", \"project sync\", \"fan out commands\", \"wire up gemini for this project\", \"add this command to codex\", \"make this skill available in copilot\", \"regenerate AGENTS.md for this project\".","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\u002Fproject-sync\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"project","project sync","sync","commands","gemini","when","for","path","make","add","scope","dry","workflows","cli","time","up","command","repo","run","copilot","2026-11-10 10:12:30",false,"---\n# dotbabel:generated projection=sha256:fea93f5906249b591d545603d7c041a8c6e09767b98ddf879a9bc8e3d4b28385 source=skills\u002Fproject-sync\u002FSKILL.md — do not edit directly\nargument-hint: \"[--dry-run] [--all] [--repo \u003Cpath>]\"\ndescription: |\n  Fan out the current repo's CLAUDE.md, .claude\u002Fcommands, and .claude\u002Fskills into Codex, Gemini, and Copilot project-scope analogues (.codex\u002Fskills, .gemini\u002Fskills, .github\u002Fprompts, .github\u002Finstructions) plus refresh AGENTS.md, GEMINI.md, and .github\u002Fcopilot-instructions.md from the project's rule floor. Wraps `dotbabel project-sync`. Use when adopting cross-CLI workflows in a repo for the first time, or when adding a new command\u002Fskill that needs to be visible to Codex\u002FGemini\u002FCopilot. Triggers on: \"sync this repo\", \"project sync\", \"fan out commands\", \"wire up gemini for this project\", \"add this command to codex\", \"make this skill available in copilot\", \"regenerate AGENTS.md for this project\".\nname: project-sync\n---\n\n# project-sync — Repo-local cross-CLI fan-out\n\nThin wrapper around `dotbabel project-sync`. The binary owns all writes; this\nskill maps natural-language requests to the right invocation and surfaces\ndry-run output before mutating the repo.\n\n## When to invoke\n\n- The user wants to adopt cross-CLI workflows in a repo that already has\n  `.claude\u002Fcommands\u002F*` or `.claude\u002Fskills\u002F*`, but no `AGENTS.md`\u002F`GEMINI.md`\u002F\n  `.github\u002Fprompts\u002F`\u002F`.github\u002Finstructions\u002F` wiring.\n- A new command or skill was just added to `.claude\u002F`, and the user wants\n  Codex\u002FGemini\u002FCopilot to see it without leaving the editor.\n- The user asks for \"drift check\" or \"is this repo synced\" — run\n  `dotbabel check-project-sync` instead and surface the diff.\n- First-time setup: if `.dotbabel.json` is missing, suggest\n  `dotbabel project-init` first.\n\n## Workflow\n\n1. **Pre-flight.** Confirm cwd is a git repo and contains `CLAUDE.md` (with or\n   without rule-floor markers) plus at least one of `.claude\u002Fcommands\u002F` or\n   `.claude\u002Fskills\u002F`. If `.dotbabel.json` is absent, mention that defaults will\n   apply (no `cli_substitutions`, full fan-out to codex\u002Fgemini\u002Fcopilot,\n   gating on each CLI's `command -v` check).\n2. **Dry-run first.** Always run `dotbabel project-sync --dry-run` before\n   mutating. Summarize the planned actions to the user (count of instruction\n   files, count of new symlinks per CLI). Pause for confirmation **unless**\n   the user already said \"do it\" or \"go ahead\" in the same turn.\n3. **Apply.** Run `dotbabel project-sync` (no `--dry-run`). If the user passed\n   `--all`, propagate it.\n4. **Verify.** Run `dotbabel check-project-sync` and report `ok` \u002F\n   `missing` \u002F `stale` counts. Exit non-zero output should be surfaced.\n   The check applies the same `gate_on_cli_presence` gate as the sync, so a CLI\n   absent from `PATH` is reported as `skipped \u003Ccli>: not on PATH` rather than as\n   drift. Propagate `--all` here too when the user passed it in step 3, so both\n   commands cover the same CLIs.\n\n## Triggers and invocations\n\n| Trigger phrase                                        | Invocation                                                 |\n| ----------------------------------------------------- | ---------------------------------------------------------- |\n| \"sync this repo\", \"project sync\", \"fan out commands\"  | `dotbabel project-sync --dry-run` then apply               |\n| \"wire up gemini for this project\"                     | `dotbabel project-sync --all` (covers all)                 |\n| \"is this repo synced\", \"drift check the project sync\" | `dotbabel check-project-sync` (read-only)                  |\n| \"regenerate AGENTS.md for this project\"               | `dotbabel project-sync` (instructions are part of the run) |\n| \"set up project sync here\", \"first-time project sync\" | `dotbabel project-init` then project-sync                  |\n\n## Reference: Copilot mapping\n\nThe Copilot CLI fan-out targets `.github\u002Fprompts\u002F*.prompt.md` (commands) and\n`.github\u002Finstructions\u002F*.instructions.md` (skills) inside the target repo.\nSee [`references\u002Fcopilot-mapping.md`](references\u002Fcopilot-mapping.md) for the\nfull layout and rationale.\n\n## Boundaries\n\n- Always operate on the user's current working directory unless they pass an\n  explicit `--repo \u003Cpath>`. Never silently target a different repo.\n- Never run `--force`. The plan reserves it for collision overrides; defer\n  to the binary's existing collision warnings.\n- For consumer repos with no `.dotbabel.json`, the convention path applies\n  (entire `CLAUDE.md` becomes the rule floor when markers are absent).\n- `fan_out` accepts only `codex`, `gemini`, and `copilot`. A typo aborts the run\n  with `CONFIG_UNKNOWN_CLI`; fix the name rather than dropping the gate.\n- `fan_out_layout` is `per-cli` by default. Under `shared`, Codex and Gemini\n  both point at one `.cli\u002Fskills\u002F` tree, so describe changes by the canonical\n  path instead of naming each CLI directory twice. Switching an existing repo\n  leaves `.codex\u002Fskills.bak-\u003Ctimestamp>` behind — say so, so the user can\n  delete it. An unknown value aborts with `CONFIG_UNKNOWN_LAYOUT`.\n- `cli_excluded` maps a CLI to command basenames and skill ids it must not\n  receive. Suggest it when a command describes a Claude-only flow. The sync\n  removes an excluded link it wrote earlier and reports `removed: \u003Cpath>`;\n  mention that so the user expects the deletion in the diff. Under `shared`,\n  an exclusion for `codex` or `gemini` applies to both and the sync warns when\n  the lists differ. A malformed value aborts with `CONFIG_INVALID_EXCLUSION`.\n- This skill is for **project-scope** sync. For user-scope (`~\u002F.claude\u002F`,\n  `~\u002F.codex\u002F`, `~\u002F.gemini\u002F`) bootstrap, use `dotbabel bootstrap` instead.\n","# project-sync — Repo-local cross-CLI fan-out\n\nThin wrapper around `dotbabel project-sync`. The binary owns all writes; this\nskill maps natural-language requests to the right invocation and surfaces\ndry-run output before mutating the repo.\n\n## When to invoke\n\n- The user wants to adopt cross-CLI workflows in a repo that already has\n  `.claude\u002Fcommands\u002F*` or `.claude\u002Fskills\u002F*`, but no `AGENTS.md`\u002F`GEMINI.md`\u002F\n  `.github\u002Fprompts\u002F`\u002F`.github\u002Finstructions\u002F` wiring.\n- A new command or skill was just added to `.claude\u002F`, and the user wants\n  Codex\u002FGemini\u002FCopilot to see it without leaving the editor.\n- The user asks for \"drift check\" or \"is this repo synced\" — run\n  `dotbabel check-project-sync` instead and surface the diff.\n- First-time setup: if `.dotbabel.json` is missing, suggest\n  `dotbabel project-init` first.\n\n## Workflow\n\n1. **Pre-flight.** Confirm cwd is a git repo and contains `CLAUDE.md` (with or\n   without rule-floor markers) plus at least one of `.claude\u002Fcommands\u002F` or\n   `.claude\u002Fskills\u002F`. If `.dotbabel.json` is absent, mention that defaults will\n   apply (no `cli_substitutions`, full fan-out to codex\u002Fgemini\u002Fcopilot,\n   gating on each CLI's `command -v` check).\n2. **Dry-run first.** Always run `dotbabel project-sync --dry-run` before\n   mutating. Summarize the planned actions to the user (count of instruction\n   files, count of new symlinks per CLI). Pause for confirmation **unless**\n   the user already said \"do it\" or \"go ahead\" in the same turn.\n3. **Apply.** Run `dotbabel project-sync` (no `--dry-run`). If the user passed\n   `--all`, propagate it.\n4. **Verify.** Run `dotbabel check-project-sync` and report `ok` \u002F\n   `missing` \u002F `stale` counts. Exit non-zero output should be surfaced.\n   The check applies the same `gate_on_cli_presence` gate as the sync, so a CLI\n   absent from `PATH` is reported as `skipped \u003Ccli>: not on PATH` rather than as\n   drift. Propagate `--all` here too when the user passed it in step 3, so both\n   commands cover the same CLIs.\n\n## Triggers and invocations\n\n| Trigger phrase                                        | Invocation                                                 |\n| ----------------------------------------------------- | ---------------------------------------------------------- |\n| \"sync this repo\", \"project sync\", \"fan out commands\"  | `dotbabel project-sync --dry-run` then apply               |\n| \"wire up gemini for this project\"                     | `dotbabel project-sync --all` (covers all)                 |\n| \"is this repo synced\", \"drift check the project sync\" | `dotbabel check-project-sync` (read-only)                  |\n| \"regenerate AGENTS.md for this project\"               | `dotbabel project-sync` (instructions are part of the run) |\n| \"set up project sync here\", \"first-time project sync\" | `dotbabel project-init` then project-sync                  |\n\n## Reference: Copilot mapping\n\nThe Copilot CLI fan-out targets `.github\u002Fprompts\u002F*.prompt.md` (commands) and\n`.github\u002Finstructions\u002F*.instructions.md` (skills) inside the target repo.\nSee [`references\u002Fcopilot-mapping.md`](references\u002Fcopilot-mapping.md) for the\nfull layout and rationale.\n\n## Boundaries\n\n- Always operate on the user's current working directory unless they pass an\n  explicit `--repo \u003Cpath>`. Never silently target a different repo.\n- Never run `--force`. The plan reserves it for collision overrides; defer\n  to the binary's existing collision warnings.\n- For consumer repos with no `.dotbabel.json`, the convention path applies\n  (entire `CLAUDE.md` becomes the rule floor when markers are absent).\n- `fan_out` accepts only `codex`, `gemini`, and `copilot`. A typo aborts the run\n  with `CONFIG_UNKNOWN_CLI`; fix the name rather than dropping the gate.\n- `fan_out_layout` is `per-cli` by default. Under `shared`, Codex and Gemini\n  both point at one `.cli\u002Fskills\u002F` tree, so describe changes by the canonical\n  path instead of naming each CLI directory twice. Switching an existing repo\n  leaves `.codex\u002Fskills.bak-\u003Ctimestamp>` behind — say so, so the user can\n  delete it. An unknown value aborts with `CONFIG_UNKNOWN_LAYOUT`.\n- `cli_excluded` maps a CLI to command basenames and skill ids it must not\n  receive. Suggest it when a command describes a Claude-only flow. The sync\n  removes an excluded link it wrote earlier and reports `removed: \u003Cpath>`;\n  mention that so the user expects the deletion in the diff. Under `shared`,\n  an exclusion for `codex` or `gemini` applies to both and the sync warns when\n  the lists differ. A malformed value aborts with `CONFIG_INVALID_EXCLUSION`.\n- This skill is for **project-scope** sync. For user-scope (`~\u002F.claude\u002F`,\n  `~\u002F.codex\u002F`, `~\u002F.gemini\u002F`) bootstrap, use `dotbabel bootstrap` instead.\n",{"name":5,"description":44,"argument-hint":45},"Fan out the current repo's CLAUDE.md, .claude\u002Fcommands, and .claude\u002Fskills into Codex, Gemini, and Copilot project-scope analogues (.codex\u002Fskills, .gemini\u002Fskills, .github\u002Fprompts, .github\u002Finstructions) plus refresh AGENTS.md, GEMINI.md, and .github\u002Fcopilot-instructions.md from the project's rule floor. Wraps `dotbabel project-sync`. Use when adopting cross-CLI workflows in a repo for the first time, or when adding a new command\u002Fskill that needs to be visible to Codex\u002FGemini\u002FCopilot. Triggers on: \"sync this repo\", \"project sync\", \"fan out commands\", \"wire up gemini for this project\", \"add this command to codex\", \"make this skill available in copilot\", \"regenerate AGENTS.md for this project\".\n","[--dry-run] [--all] [--repo \u003Cpath>]","main","91c337164997b99943fbcc64e8e362577b67bc81","examples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fproject-sync","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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add kaiohenricunha\u002Fdotbabel --skill project-sync",{"tool":59,"command":60},"bunx","bunx skills add kaiohenricunha\u002Fdotbabel --skill project-sync",{"tool":62,"command":63},"pnpm","pnpm dlx skills add kaiohenricunha\u002Fdotbabel --skill project-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fproject-sync\u002FSKILL.md",true,[67],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fcopilot-mapping.md","REFERENCE","参考文档",2336,"https:\u002F\u002Fgithub.com\u002Fkaiohenricunha\u002Fdotbabel\u002Fblob\u002Fmain\u002Fexamples\u002Fminimal-consumer\u002F.claude\u002Fskills\u002Fproject-sync\u002Freferences\u002Fcopilot-mapping.md",[74,103,134,155,176,198],{"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":85,"publishedAt":39},"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",[80],{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[76,86,87,88,89,90,91,92,93,94,95,96,97,29,98,99,100,101,25,102],"testing","merge","code","start","access","session","ops","autonomy","releases","permission","full","runtime","devex","hook","true","action","scoped",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":117,"publishedAt":39},"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",[109,114],{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":115,"categoryName":116,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000037","律师与法务",[118,119,86,120,121,122,123,124,125,126,127,128,129,33,19,130,131,132,133,24],"audit","veracity audit","review","data pipeline","pipeline","Bash","math","coverage","only","engineer","formula","scoring","worker","end","at","invoke",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":39},"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",[],[141,142,143,86,120,37,144,118,123,145,146,147,126,148,149,150,151,152,153,154],"spec","validate","validate spec","acceptance","work","read","never","max","done","arch","line","2025","spec-driven","closure",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":164,"publishedAt":39},"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",[161],{"categoryNo":162,"categoryName":163,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000011","运维与部署",[165,166,167,120,168,169,37,118,170,123,146,171,172,148,173,30,152,174,132,175],"terragrunt","specialist","terragrunt specialist","orchestration","debugging","analysis","dependency","hooks","deep","remote","hierarchy",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":189,"publishedAt":39},"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",[182,185,186],{"categoryNo":183,"categoryName":184,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":162,"categoryName":163,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":187,"categoryName":188,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000015","视觉设计",[190,191,166,86,192,120,31,193,194,169,118,123,146,125,195,196,173,197,152,132],"terraform","terraform specialist","design","architecture","architecture review","test coverage","workspaces","problem",{"skillNo":199,"name":141,"nameZh":6,"description":200,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":201,"categories":202,"keywords":207,"publishedAt":39},"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",[203,204],{"categoryNo":187,"categoryName":188,"taxonomyType":112,"taxonomyTypeDesc":113},{"categoryNo":205,"categoryName":206,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000032","设计师",[141,192,208,193,209,210,211,212,213,214,215,216,217,218,219,25,220,221,222,223],"component","create","plan","projects","write","interactive","use","document","specification","triggers","opus","technical specification","trade-offs","technical plan","outputs","frontier"]