[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6HR74CYRKKYHRBP836FFQMS":3,"skill-same:01M6HR74CYRKKYHRBP836FFQMS":65},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M6HR74CYRKKYHRBP836FFQMS","init-output",null,"Create the architect output directories and work\u002Fpipeline-progress.json for a new project.","wfukatsu\u002Fnexus-architect","wfukatsu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F11712747?v=4","01M6HR128TEJY1WD0C36TDQD7S","Wataru Fukatsu","01M6HR12D55WNY36YSW845YXZ1",13,"MIT","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Finit-output\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33],"init","output","init output","create","pipeline","architect","new project","json","haiku","work","project","name","progress","directories","for","2026-11-10 10:12:30",false,"---\ndescription: |\n  Create the architect output directories and work\u002Fpipeline-progress.json for a new project.\nargument-hint: '[project_name]'\nmodel: haiku\n---\n\n# Output Initialization\n\nShared files: a path written `@rules\u002F…`, `@skills\u002F…`, `@templates\u002F…` or `@docs\u002F…` is relative to the\nplugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.\n\n**Usage:** `\u002Farchitect:init-output [project_name]`\n\nUse --reset to reinitialize.\n\n## Expected Outcome\n\nCreate the directory structure and progress management files required for pipeline execution.\n\n## Existing State Is Never Discarded\n\nThis skill is **additive**. A project may already carry state when it runs — most often\nbecause the `product` pipeline ran first and this is the product→architect handoff\n(@docs\u002Fdesign.md §1.1–1.5), but equally on any re-run of the architect path. Read each file\nbefore writing it and merge into what is there. Only `--reset` replaces anything, and only\nafter a backup.\n\nWhat is at stake: `work\u002Fcontext.md` is **the** Open Questions store for the whole project — both\npipelines' questions, in one file (@rules\u002Fopen-questions.md §6) — which\n`\u002Farchitect:define-requirements` reads in its Step 2 to re-ask the `deferred` \u002F `unasked` entries\nit needs and answer them in place; `work\u002Fpipeline-progress.json` is shared\nby both pipelines and already holds the product phases and the `output_language` the user\nchose during the product run.\n\n## Execution Steps\n\n1. Create the following directories:\n   - `reports\u002Fbefore\u002F{project}\u002F`\n   - `reports\u002F00_summary\u002F`\n   - `reports\u002F01_analysis\u002F`\n   - `reports\u002F02_evaluation\u002F`\n   - `reports\u002F03_design\u002F`\n   - `reports\u002Freview\u002Findividual\u002F`\n   - `generated\u002F`\n   - `work\u002F`\n\n2. Create **or merge** `work\u002Fpipeline-progress.json`:\n\n   - **Absent** — create it, registering every phase from\n     `@skills\u002Fcommon\u002Fskill-dependencies.yaml` as `\"pending\"`, each with the fields defined in\n     @skills\u002Fcommon\u002Fprogress-registry.md — including `\"plugin\": \"architect\"`, which is what\n     makes an entry attributable once both pipelines share the file.\n   - **Present** — keep the file and add only the phase entries it does not already have, as\n     `\"pending\"`. Never reset an entry that exists, never remove a phase this manifest does\n     not define (the product pipeline registers its own phases in the same file), and leave\n     `gates`, `errors`, `warnings` and any other top-level key untouched.\n   - `options` — keep every value already set, in particular `output_language`, which the\n     product run may have asked the user for. Fill in only what is missing: `output_language`\n     defaults to `\"en\"`, `confirm_versions` to `true` (whether codegen skills confirm resolved\n     dependency versions with the user — see @rules\u002Fdependency-versions.md), `eli5` to\n     `\"technical\"` (which reports open with the plain-language section of\n     @rules\u002Feli5-summary.md).\n   - **Colliding phase names.** Four names are defined by *both* manifests — `map-domains`,\n     `design-api`, `create-domain-story`, `report` — and the registry keys phases by bare\n     name, so an existing entry under one of them may describe the **product** phase rather\n     than this one. Leave it exactly as it is. If it carries `\"plugin\": \"product\"` the\n     question is settled and there is nothing to report; if it carries no `plugin` at all\n     and is already `completed`, append one line to `warnings[]` naming it and stating that\n     its status may belong to the product pipeline, so the architect phase is unverified.\n     The status dashboard renders `warnings[]`, so the ambiguity is visible instead of\n     reading as done. **Never add `\"plugin\": \"architect\"` to an entry you did not create** —\n     that would claim the neighbour's work as this pipeline's.\n\n3. Create `work\u002Fcontext.md` **only if it is absent**, seeded with an empty `## Open Questions`\n   section whose table has the @rules\u002Fopen-questions.md §6 header, verbatim:\n\n   ```markdown\n   ## Open Questions\n\n   | ID | Question | Status | Answer | Options offered | Owner | Impact | Asked at |\n   |----|----------|--------|--------|-----------------|-------|--------|----------|\n   ```\n\n   If it exists, leave its content in\n   place: phases append to it, and it is **the** Open Questions store for the whole project —\n   both pipelines' questions live in this one file, so on the handoff path it already holds the\n   entries `\u002Farchitect:define-requirements` is about to read, re-ask and answer in place.\n   `reports\u002F00_requirements\u002Fopen-questions.md` is a view rendered from it, never a second store.\n\n## Options\n\n- `--reset`: Back up the existing `work\u002Fpipeline-progress.json` (copy to `*.bak`), then\n  re-register **this manifest's** phases as `\"pending\"` — phases belonging to the product\n  pipeline are still preserved. `--reset` does not touch `work\u002Fcontext.md` or\n  `work\u002Ftraceability.json`; both are shared with the product pipeline.\n\n## Completion Criteria\n\nThe directory structure and `work\u002Fpipeline-progress.json` exist, every architect phase has an\nentry, and no pre-existing phase entry, option value, or `work\u002Fcontext.md` content was lost.\n","# Output Initialization\n\nShared files: a path written `@rules\u002F…`, `@skills\u002F…`, `@templates\u002F…` or `@docs\u002F…` is relative to the\nplugin root, `${CLAUDE_PLUGIN_ROOT}` — not to the project being worked on. Read it from there.\n\n**Usage:** `\u002Farchitect:init-output [project_name]`\n\nUse --reset to reinitialize.\n\n## Expected Outcome\n\nCreate the directory structure and progress management files required for pipeline execution.\n\n## Existing State Is Never Discarded\n\nThis skill is **additive**. A project may already carry state when it runs — most often\nbecause the `product` pipeline ran first and this is the product→architect handoff\n(@docs\u002Fdesign.md §1.1–1.5), but equally on any re-run of the architect path. Read each file\nbefore writing it and merge into what is there. Only `--reset` replaces anything, and only\nafter a backup.\n\nWhat is at stake: `work\u002Fcontext.md` is **the** Open Questions store for the whole project — both\npipelines' questions, in one file (@rules\u002Fopen-questions.md §6) — which\n`\u002Farchitect:define-requirements` reads in its Step 2 to re-ask the `deferred` \u002F `unasked` entries\nit needs and answer them in place; `work\u002Fpipeline-progress.json` is shared\nby both pipelines and already holds the product phases and the `output_language` the user\nchose during the product run.\n\n## Execution Steps\n\n1. Create the following directories:\n   - `reports\u002Fbefore\u002F{project}\u002F`\n   - `reports\u002F00_summary\u002F`\n   - `reports\u002F01_analysis\u002F`\n   - `reports\u002F02_evaluation\u002F`\n   - `reports\u002F03_design\u002F`\n   - `reports\u002Freview\u002Findividual\u002F`\n   - `generated\u002F`\n   - `work\u002F`\n\n2. Create **or merge** `work\u002Fpipeline-progress.json`:\n\n   - **Absent** — create it, registering every phase from\n     `@skills\u002Fcommon\u002Fskill-dependencies.yaml` as `\"pending\"`, each with the fields defined in\n     @skills\u002Fcommon\u002Fprogress-registry.md — including `\"plugin\": \"architect\"`, which is what\n     makes an entry attributable once both pipelines share the file.\n   - **Present** — keep the file and add only the phase entries it does not already have, as\n     `\"pending\"`. Never reset an entry that exists, never remove a phase this manifest does\n     not define (the product pipeline registers its own phases in the same file), and leave\n     `gates`, `errors`, `warnings` and any other top-level key untouched.\n   - `options` — keep every value already set, in particular `output_language`, which the\n     product run may have asked the user for. Fill in only what is missing: `output_language`\n     defaults to `\"en\"`, `confirm_versions` to `true` (whether codegen skills confirm resolved\n     dependency versions with the user — see @rules\u002Fdependency-versions.md), `eli5` to\n     `\"technical\"` (which reports open with the plain-language section of\n     @rules\u002Feli5-summary.md).\n   - **Colliding phase names.** Four names are defined by *both* manifests — `map-domains`,\n     `design-api`, `create-domain-story`, `report` — and the registry keys phases by bare\n     name, so an existing entry under one of them may describe the **product** phase rather\n     than this one. Leave it exactly as it is. If it carries `\"plugin\": \"product\"` the\n     question is settled and there is nothing to report; if it carries no `plugin` at all\n     and is already `completed`, append one line to `warnings[]` naming it and stating that\n     its status may belong to the product pipeline, so the architect phase is unverified.\n     The status dashboard renders `warnings[]`, so the ambiguity is visible instead of\n     reading as done. **Never add `\"plugin\": \"architect\"` to an entry you did not create** —\n     that would claim the neighbour's work as this pipeline's.\n\n3. Create `work\u002Fcontext.md` **only if it is absent**, seeded with an empty `## Open Questions`\n   section whose table has the @rules\u002Fopen-questions.md §6 header, verbatim:\n\n   ```markdown\n   ## Open Questions\n\n   | ID | Question | Status | Answer | Options offered | Owner | Impact | Asked at |\n   |----|----------|--------|--------|-----------------|-------|--------|----------|\n   ```\n\n   If it exists, leave its content in\n   place: phases append to it, and it is **the** Open Questions store for the whole project —\n   both pipelines' questions live in this one file, so on the handoff path it already holds the\n   entries `\u002Farchitect:define-requirements` is about to read, re-ask and answer in place.\n   `reports\u002F00_requirements\u002Fopen-questions.md` is a view rendered from it, never a second store.\n\n## Options\n\n- `--reset`: Back up the existing `work\u002Fpipeline-progress.json` (copy to `*.bak`), then\n  re-register **this manifest's** phases as `\"pending\"` — phases belonging to the product\n  pipeline are still preserved. `--reset` does not touch `work\u002Fcontext.md` or\n  `work\u002Ftraceability.json`; both are shared with the product pipeline.\n\n## Completion Criteria\n\nThe directory structure and `work\u002Fpipeline-progress.json` exist, every architect phase has an\nentry, and no pre-existing phase entry, option value, or `work\u002Fcontext.md` content was lost.\n",{"model":27,"description":39,"argument-hint":40},"Create the architect output directories and work\u002Fpipeline-progress.json for a new project.\n","[project_name]","main","fed4c7ebb79ed82ce5c961f944a1ab0ab21bae26","skills\u002Finit-output",1,"https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect","https:\u002F\u002Fnexus-architect-docs-070772.gitlab.io\u002F","https:\u002F\u002Fgithub.com\u002Fwfukatsu","https:\u002F\u002Fwww.scalar-labs.com\u002F","Wataru Fukatsu | Co-Founder and CEO, Scalar, Inc.","2026-11-12 08:27:58",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add wfukatsu\u002Fnexus-architect --skill init-output",{"tool":57,"command":58},"bunx","bunx skills add wfukatsu\u002Fnexus-architect --skill init-output",{"tool":60,"command":61},"pnpm","pnpm dlx skills add wfukatsu\u002Fnexus-architect --skill init-output","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Finit-output\u002FSKILL.md",true,[],[66,103,135,162,185,203],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":82,"publishedAt":34},"01M6HRH10GPAVTZ8W90WD9HJK1","verify-sql-migration","Prove a SQL migration on data: golden checks against an authorized source database and\ndifferential tests against ScalarDB. Never touches production.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fverify-sql-migration\u002FSKILL.md",[72,77],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102],"sql","verify","migration","verify sql migration","core","database","data","Production","auto","never","en","properties","fetcher","tests","id","golden","sonnet","true","mode","source",{"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":118,"publishedAt":34},"01M6HRGWK643YKN0QVRQSNSDCR","verify-implementation","Check code against the design (API contract, transactions, security, requirements, the example\nchain) and report every divergence; optionally runs the eight-stage quality gate.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fverify-implementation\u002FSKILL.md",[109,112,115],{"categoryNo":110,"categoryName":111,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":113,"categoryName":114,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000030","开发工程师",{"categoryNo":116,"categoryName":117,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务",[84,119,120,121,122,123,124,125,126,91,127,93,128,129,130,131,132,133,134,100],"implementation","verify implementation","design","quality gate","code","api","repo","check","example","api contract","backlog","stage","requirements","contract","chain","scope",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":147,"publishedAt":34},"01M6HRGS929NK1B5WG1ZANSXQ1","update-knowledge","Fetch or update an OKF knowledge bundle: ScalarDB\u002FScalarDL, or the vendored Kubernetes\u002FTerraform\nbundle.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fupdate-knowledge\u002FSKILL.md",[141,144],{"categoryNo":142,"categoryName":143,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":145,"categoryName":146,"taxonomyType":75,"taxonomyTypeDesc":76},"01JBSEEDCAT000000000000021","资料检索与研究",[148,149,150,151,152,153,154,155,156,157,27,158,159,30,160,161],"update","knowledge","update knowledge","kubernetes","status","plugin","terraform","Tools","Bash","okf","fetch","bundle","root","latest",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":172,"publishedAt":34},"01M6HRGNMYSK70R8Y9BY41E74D","start","Interactive entry point for system architecture work: refactor a legacy application into services,\nor design a new system from requirements; picks the path from the project's state. To move a\ndatabase to ScalarDB, use migrate-database.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fstart\u002FSKILL.md",[168,169],{"categoryNo":110,"categoryName":111,"taxonomyType":75,"taxonomyTypeDesc":76},{"categoryNo":170,"categoryName":171,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000032","设计师",[164,121,173,174,88,175,176,177,178,28,179,180,181,182,29,131,183,184,33],"architecture","state","services","refactor","migrate","system","interactive","use","Legacy","application","move","path",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":34},"01M6HRGHZXK0NXF6W62MMNS46H","select-scalardb-edition","Choose the ScalarDB edition (Community, Enterprise Standard or Premium, plus Enterprise Options),\ndeployment mode and cluster topology through a short interview.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fselect-scalardb-edition\u002FSKILL.md",[],[192,193,194,195,196,197,198,199,200,201,202,99,101],"select","select scalardb edition","deployment","topology","Enterprise","choose","short","interview","community","options","cluster",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":34},"01M6HRGESF0BH6KCT70BP70B2J","scaffold","Generate a runnable ScalarDB starter project for any of the six interface combinations: build,\nconfig, schema, service class, docker-compose and README.","https:\u002F\u002Fgithub.com\u002Fwfukatsu\u002Fnexus-architect\u002Fblob\u002Fmain\u002Fskills\u002Fscaffold\u002FSKILL.md",[209],{"categoryNo":73,"categoryName":74,"taxonomyType":75,"taxonomyTypeDesc":76},[205,211,212,213,214,215,216,217,218,29,219,220,221,222,99,33],"docker","config","generate","README","schema","compose","build","docker-compose","combinations","service","starter","interface"]