[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME619V83Z79J6ZTZFSP2Y1":3,"skill-same:01M6ME619V83Z79J6ZTZFSP2Y1":82},{"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":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6ME619V83Z79J6ZTZFSP2Y1","plan",null,"Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research \u003Ctopic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use \u002Farchcore:document. Not for checking docs against code — use \u002Farchcore:review.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchcore-ai\u002Fplugin\u002Fskills\u002Fplan\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[5,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"either","new","hand","re","recording","sources","scope","customer discovery","iso","sdd","route","review","roadmap","never","coverage","work","decision","code","create","customer","2026-11-10 10:12:30",false,"---\nname: plan\nargument-hint: \"[sdd|sources|iso|research] [topic]\"\ndescription: \"Plan a feature or initiative through a computed route: the conductor derives the canon delta and assembles the document package — from a zero-document null route for small fixes to an umbrella PRD with one spec per capability for large initiatives. Modes, named as the first word: sdd (full package), sources (MRD → BRD → URD) for market research, customer discovery, and business or user requirements, iso (BRS → StRS → SyRS → SRS) for ISO 29148 and regulated work, research for a technical investigation — never market research — that the research instrument closes either by scope coverage (a research document) or by a recommendation (an rnd). Explicit form: plan research \u003Ctopic>. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'I need market research before we plan', 'we're regulated — start the ISO requirements cascade', 'investigate X before we plan', 'compare the alternatives for Y' — a new investigation, not a finished report already in hand. Not for recording a decision or documenting existing code — use \u002Farchcore:document. Not for checking docs against code — use \u002Farchcore:review.\"\n---\n\n# \u002Farchcore:plan\n\nPlan a feature or initiative through a computed route. The conductor\n(`skills\u002F_shared\u002Fdelta-routing.md`) derives the canon delta Δ, the gap profile\nΠ, the zone maturity M, and the risk flags R, then assembles the document\npackage; instruments produce the documents. Vision types are the primary\noutput. Reads cover all three categories: vision supplies intent and\nresumption targets, knowledge supplies constraints, experience supplies\nprecedent.\n\n## When to use\n\n- \"Plan the auth redesign\" → computed route — typically `capability`: one spec plus one plan\n- \"Create a roadmap for the API migration\" → computed route\n- \"Plan a new feature for CSV export\" → computed route\n- \"Plan the notifications platform\" → computed route — typically `umbrella`: prd, one spec per capability, one plan\n- \"I need market research before we plan\" → acquisition instrument (`sources` mode)\n- \"We're regulated — start the ISO requirements cascade\" → iso links (`iso` mode)\n- \"Investigate X before we plan\" → research instrument, `research`; \"Compare the alternatives for Y\" → research instrument, `rnd` — a named pending decision or candidate set selects `rnd`, otherwise `research`\n- `plan research \u003Ctopic>` → research instrument; the instrument selects `research` (closed by scope coverage) or `rnd` (closed by a recommendation) by its closing test\n\n**Not plan:**\n\n- Recording a decision → `\u002Farchcore:document`\n- Documenting existing code → `\u002Farchcore:document`\n- Codifying a team standard → `\u002Farchcore:document`\n- Checking documents against code → `\u002Farchcore:review`\n\n## Route computation\n\nApply in this order:\n\n| Signal | Route |\n|---|---|\n| No arguments | Ground per step 1; WHEN a draft on the branch carries a state block, resume it; otherwise ask one question — what to plan — with a recommendation drawn from the branch changes |\n| The first word is a mode (`sdd`, `sources`, `iso`, `research`) | The mapped instrument per the mode map in `skills\u002F_shared\u002Fdelta-routing.md`, without route computation |\n| Any other request | Compute Δ, Π, M, and R per the Derivation section of `skills\u002F_shared\u002Fdelta-routing.md`; its route table decides the package |\n| A decision surfaces at a gate | Record the `adr` through the decision instrument (`skills\u002F_shared\u002Ftracks\u002Fdecision.md`), then return to the open gate |\n\nResearch boundary: discovery feeding an `mrd` → `brd` → `urd` requirements\nchain belongs to acquisition. A request naming a pending decision or a set of\ncandidates to choose between produces `rnd`; any other investigation produces\n`research`. The path name `research` selects the instrument, not the type; the\nsame test applies. Neither `rnd` nor `evidence` is an entry on this command: an\n`rnd` comes only from that test, the spike, or the compatibility fallback, and a\nstandalone material is filed through `\u002Farchcore:document research`. A request proposing a specific\ntarget for team acceptance (\"should we switch to Y\", \"let's adopt Y\") belongs\nto `\u002Farchcore:document`'s decision instrument.\n\n## Execution\n\n### 1. Ground\n\nComplete this step before asking the user any question. The research\nvocabulary probe (`skills\u002F_shared\u002Fresearch-compatibility.md`) runs only under\nits own condition 1 — a request or type naming `research` or `evidence`, a\nroute engaging the research instrument, or a grounding result of either type.\nAdd `research` and `evidence` to the planning-moment filter below only when\nthe probe returns `yes`; a topic search without a type filter finds documents\nof both types on every engine. If this skill has no shell tool, use the probe\nresult the host supplied; if none was supplied, report `needs-vocabulary-probe`\nwith the helper path and stop before the first MCP call that names either type.\n\nThe actor-subject probe (`skills\u002F_shared\u002Factor-subject-compatibility.md`) runs\nunder its own condition 1 — a request naming `scenario` or `journey`, a route\nengaging the illustrate instrument, or a grounding result of either type — and\nadds both types to the filter below only when it returns `yes`. The same\nno-shell rule applies: report `needs-vocabulary-probe` and stop before the first\nMCP call that names either type.\n\n1. Search `.archcore\u002F` with `mcp__archcore__search_documents` and `mcp__archcore__list_documents` across all three categories. Pass a planning-moment type filter — for example `types=[\"idea\", \"prd\", \"plan\", \"spec\", \"rnd\", \"rfc\", \"adr\", \"rule\", \"task-type\", \"cpat\"]` — and add `\"scenario\"`, `\"journey\"` when the actor-subject probe returned `yes` — instead of relying on the global type ranking. Do not exclude a category from reads.\n2. WHEN a found document carries `implements`, `depends_on`, or `related` relations, pull the linked documents one hop via `mcp__archcore__list_relations` and `mcp__archcore__get_document`.\n3. WHEN a found draft on the topic carries an `archcore:track` state block, resume it per the resume rules in `skills\u002F_shared\u002Fgate-contract.md` and `skills\u002F_shared\u002Fdelta-routing.md` instead of opening a new track.\n4. Read git state — current branch, recent commits, working tree — and the code areas the topic names. Record the concrete files and modules for Step 5, and note zone documents whose referenced paths changed after them — the staleness input to Derivation.\n5. IF `.archcore\u002F` exists but contains no documents, THEN proceed on outer-context grounding (git state and the codebase) and report that zero documents were found.\n6. IF `.archcore\u002F` does not exist, THEN announce initialization in one line and call `mcp__archcore__init_project` without asking a question.\n\n**Global sources.** If a `list_documents` \u002F `search_documents` result has\n`global: true` \u002F `read_only: true` \u002F `source_kind: \"global\"`, load\n`skills\u002F_shared\u002Fglobals.md`. Also load it when a `search_documents` response's\n`coverage` names a source other than `\"local\"` — even when `results` is empty:\nthe empty page is exactly where that file's retry ladder applies. Never modify\na global document and never target one with `add_relation`. Absent any global\nmatch, proceed as usual.\n\n### 2. Route\n\nCompute the route per the Derivation section of\n`skills\u002F_shared\u002Fdelta-routing.md` and report the route announcement. WHEN the\nfirst word is a mode, execute its mapped instrument without route computation.\nA route name or a document type name as the first word is topic text; the\nconductor computes the route. Never ask the user to choose a route or a size label.\n\n### 3. Budget\n\nInterview mechanics, question form, and ceilings:\n`skills\u002F_shared\u002Felicitation-contract.md`. Auto mode draws every question from\nthe shared per-invocation ceiling; a mode entry raises per-gate\nbudgets to the maxima the track file declares.\n\n### 4. Execute the package\n\nInvoke each instrument the route names, in conductor order, per the instrument\nregistry and sequencing rules in `skills\u002F_shared\u002Fdelta-routing.md`. Run each\ninstrument's gates per `skills\u002F_shared\u002Fgate-contract.md`: evaluate `skip_when`\nfirst at every gate, keep track state only in the `archcore:track` block\ninside the draft artifact (with the `route:` and `delta:` fields this command\nadds), persist each gate close in one `mcp__archcore__update_document` call,\nand follow the resume rules on re-entry. Gate bodies, per-gate questions, and\nrelation wiring live in the track files — do not restate them.\n\nBefore delegating research or evidence work, pass the current vocabulary probe\nresult and absolute plugin root to the assistant. If the assistant returns\n`needs-vocabulary-probe`, run the helper and resume the same task.\nBefore delegating any other document write or relation work, pass the absolute\nplugin root to the assistant. The assistant reads\n`skills\u002F_shared\u002Frelation-authoring.md` under that root.\n\n### 5. Map tasks to files\n\nWHEN the package produced a `plan` document:\n\n1. Annotate each task in the plan's Tasks section with the concrete files or modules that grounding surfaced for it, using `@path\u002Fto\u002Ffile` notation, in one `mcp__archcore__update_document` call.\n2. WHEN grounding surfaced no file or module for a task, state that no target was found for that task. Do not guess a path.\n3. Confirm the plan carries its `## Declared Delta` section per sequencing rule 9 of `skills\u002F_shared\u002Fdelta-routing.md`.\n\nWHEN the package produced no `plan` document (the `null`, `decision`, and\n`amendment` routes, the acquisition and research paths), skip to Result — the\nexit gate or the announcement names the follow-ups.\n\n### 6. Implement fork\n\nOffer exactly two exits and let the user choose:\n\n- **Implement now** — start on the mapped task list, first phase first, against the files mapped in Step 5.\n- **Stop here** — the draft documents and relations stay in `.archcore\u002F`; a later `\u002Farchcore:plan` invocation resumes any draft that still carries a state block.\n\n## Result\n\nReport:\n\n- The route announcement — route, size label, and the Δ, Π, M, R values that produced them.\n- Produced documents grouped by category — vision, knowledge, experience — with each document's path and status.\n- Relations created, plus candidate `mcp__archcore__add_relation` targets among existing documents, or a statement that none match.\n- `retires` entries reported for closeout discharge, when any exist.\n- Next actions, naming only v2 commands: `\u002Farchcore:plan` to continue a package, `\u002Farchcore:document decision` to record a decision or `\u002Farchcore:document code` to document code touched during implementation, `\u002Farchcore:review closeout` to check the implementation against the recorded plan and reconcile the declared Δ.\n- Name instruments and stages in plain words; do not print a gate address of the form `\u003Ctrack>.\u003Cstage>`.\n","# \u002Farchcore:plan\n\nPlan a feature or initiative through a computed route. The conductor\n(`skills\u002F_shared\u002Fdelta-routing.md`) derives the canon delta Δ, the gap profile\nΠ, the zone maturity M, and the risk flags R, then assembles the document\npackage; instruments produce the documents. Vision types are the primary\noutput. Reads cover all three categories: vision supplies intent and\nresumption targets, knowledge supplies constraints, experience supplies\nprecedent.\n\n## When to use\n\n- \"Plan the auth redesign\" → computed route — typically `capability`: one spec plus one plan\n- \"Create a roadmap for the API migration\" → computed route\n- \"Plan a new feature for CSV export\" → computed route\n- \"Plan the notifications platform\" → computed route — typically `umbrella`: prd, one spec per capability, one plan\n- \"I need market research before we plan\" → acquisition instrument (`sources` mode)\n- \"We're regulated — start the ISO requirements cascade\" → iso links (`iso` mode)\n- \"Investigate X before we plan\" → research instrument, `research`; \"Compare the alternatives for Y\" → research instrument, `rnd` — a named pending decision or candidate set selects `rnd`, otherwise `research`\n- `plan research \u003Ctopic>` → research instrument; the instrument selects `research` (closed by scope coverage) or `rnd` (closed by a recommendation) by its closing test\n\n**Not plan:**\n\n- Recording a decision → `\u002Farchcore:document`\n- Documenting existing code → `\u002Farchcore:document`\n- Codifying a team standard → `\u002Farchcore:document`\n- Checking documents against code → `\u002Farchcore:review`\n\n## Route computation\n\nApply in this order:\n\n| Signal | Route |\n|---|---|\n| No arguments | Ground per step 1; WHEN a draft on the branch carries a state block, resume it; otherwise ask one question — what to plan — with a recommendation drawn from the branch changes |\n| The first word is a mode (`sdd`, `sources`, `iso`, `research`) | The mapped instrument per the mode map in `skills\u002F_shared\u002Fdelta-routing.md`, without route computation |\n| Any other request | Compute Δ, Π, M, and R per the Derivation section of `skills\u002F_shared\u002Fdelta-routing.md`; its route table decides the package |\n| A decision surfaces at a gate | Record the `adr` through the decision instrument (`skills\u002F_shared\u002Ftracks\u002Fdecision.md`), then return to the open gate |\n\nResearch boundary: discovery feeding an `mrd` → `brd` → `urd` requirements\nchain belongs to acquisition. A request naming a pending decision or a set of\ncandidates to choose between produces `rnd`; any other investigation produces\n`research`. The path name `research` selects the instrument, not the type; the\nsame test applies. Neither `rnd` nor `evidence` is an entry on this command: an\n`rnd` comes only from that test, the spike, or the compatibility fallback, and a\nstandalone material is filed through `\u002Farchcore:document research`. A request proposing a specific\ntarget for team acceptance (\"should we switch to Y\", \"let's adopt Y\") belongs\nto `\u002Farchcore:document`'s decision instrument.\n\n## Execution\n\n### 1. Ground\n\nComplete this step before asking the user any question. The research\nvocabulary probe (`skills\u002F_shared\u002Fresearch-compatibility.md`) runs only under\nits own condition 1 — a request or type naming `research` or `evidence`, a\nroute engaging the research instrument, or a grounding result of either type.\nAdd `research` and `evidence` to the planning-moment filter below only when\nthe probe returns `yes`; a topic search without a type filter finds documents\nof both types on every engine. If this skill has no shell tool, use the probe\nresult the host supplied; if none was supplied, report `needs-vocabulary-probe`\nwith the helper path and stop before the first MCP call that names either type.\n\nThe actor-subject probe (`skills\u002F_shared\u002Factor-subject-compatibility.md`) runs\nunder its own condition 1 — a request naming `scenario` or `journey`, a route\nengaging the illustrate instrument, or a grounding result of either type — and\nadds both types to the filter below only when it returns `yes`. The same\nno-shell rule applies: report `needs-vocabulary-probe` and stop before the first\nMCP call that names either type.\n\n1. Search `.archcore\u002F` with `mcp__archcore__search_documents` and `mcp__archcore__list_documents` across all three categories. Pass a planning-moment type filter — for example `types=[\"idea\", \"prd\", \"plan\", \"spec\", \"rnd\", \"rfc\", \"adr\", \"rule\", \"task-type\", \"cpat\"]` — and add `\"scenario\"`, `\"journey\"` when the actor-subject probe returned `yes` — instead of relying on the global type ranking. Do not exclude a category from reads.\n2. WHEN a found document carries `implements`, `depends_on`, or `related` relations, pull the linked documents one hop via `mcp__archcore__list_relations` and `mcp__archcore__get_document`.\n3. WHEN a found draft on the topic carries an `archcore:track` state block, resume it per the resume rules in `skills\u002F_shared\u002Fgate-contract.md` and `skills\u002F_shared\u002Fdelta-routing.md` instead of opening a new track.\n4. Read git state — current branch, recent commits, working tree — and the code areas the topic names. Record the concrete files and modules for Step 5, and note zone documents whose referenced paths changed after them — the staleness input to Derivation.\n5. IF `.archcore\u002F` exists but contains no documents, THEN proceed on outer-context grounding (git state and the codebase) and report that zero documents were found.\n6. IF `.archcore\u002F` does not exist, THEN announce initialization in one line and call `mcp__archcore__init_project` without asking a question.\n\n**Global sources.** If a `list_documents` \u002F `search_documents` result has\n`global: true` \u002F `read_only: true` \u002F `source_kind: \"global\"`, load\n`skills\u002F_shared\u002Fglobals.md`. Also load it when a `search_documents` response's\n`coverage` names a source other than `\"local\"` — even when `results` is empty:\nthe empty page is exactly where that file's retry ladder applies. Never modify\na global document and never target one with `add_relation`. Absent any global\nmatch, proceed as usual.\n\n### 2. Route\n\nCompute the route per the Derivation section of\n`skills\u002F_shared\u002Fdelta-routing.md` and report the route announcement. WHEN the\nfirst word is a mode, execute its mapped instrument without route computation.\nA route name or a document type name as the first word is topic text; the\nconductor computes the route. Never ask the user to choose a route or a size label.\n\n### 3. Budget\n\nInterview mechanics, question form, and ceilings:\n`skills\u002F_shared\u002Felicitation-contract.md`. Auto mode draws every question from\nthe shared per-invocation ceiling; a mode entry raises per-gate\nbudgets to the maxima the track file declares.\n\n### 4. Execute the package\n\nInvoke each instrument the route names, in conductor order, per the instrument\nregistry and sequencing rules in `skills\u002F_shared\u002Fdelta-routing.md`. Run each\ninstrument's gates per `skills\u002F_shared\u002Fgate-contract.md`: evaluate `skip_when`\nfirst at every gate, keep track state only in the `archcore:track` block\ninside the draft artifact (with the `route:` and `delta:` fields this command\nadds), persist each gate close in one `mcp__archcore__update_document` call,\nand follow the resume rules on re-entry. Gate bodies, per-gate questions, and\nrelation wiring live in the track files — do not restate them.\n\nBefore delegating research or evidence work, pass the current vocabulary probe\nresult and absolute plugin root to the assistant. If the assistant returns\n`needs-vocabulary-probe`, run the helper and resume the same task.\nBefore delegating any other document write or relation work, pass the absolute\nplugin root to the assistant. The assistant reads\n`skills\u002F_shared\u002Frelation-authoring.md` under that root.\n\n### 5. Map tasks to files\n\nWHEN the package produced a `plan` document:\n\n1. Annotate each task in the plan's Tasks section with the concrete files or modules that grounding surfaced for it, using `@path\u002Fto\u002Ffile` notation, in one `mcp__archcore__update_document` call.\n2. WHEN grounding surfaced no file or module for a task, state that no target was found for that task. Do not guess a path.\n3. Confirm the plan carries its `## Declared Delta` section per sequencing rule 9 of `skills\u002F_shared\u002Fdelta-routing.md`.\n\nWHEN the package produced no `plan` document (the `null`, `decision`, and\n`amendment` routes, the acquisition and research paths), skip to Result — the\nexit gate or the announcement names the follow-ups.\n\n### 6. Implement fork\n\nOffer exactly two exits and let the user choose:\n\n- **Implement now** — start on the mapped task list, first phase first, against the files mapped in Step 5.\n- **Stop here** — the draft documents and relations stay in `.archcore\u002F`; a later `\u002Farchcore:plan` invocation resumes any draft that still carries a state block.\n\n## Result\n\nReport:\n\n- The route announcement — route, size label, and the Δ, Π, M, R values that produced them.\n- Produced documents grouped by category — vision, knowledge, experience — with each document's path and status.\n- Relations created, plus candidate `mcp__archcore__add_relation` targets among existing documents, or a statement that none match.\n- `retires` entries reported for closeout discharge, when any exist.\n- Next actions, naming only v2 commands: `\u002Farchcore:plan` to continue a package, `\u002Farchcore:document decision` to record a decision or `\u002Farchcore:document code` to document code touched during implementation, `\u002Farchcore:review closeout` to check the implementation against the recorded plan and reconcile the declared Δ.\n- Name instruments and stages in plain words; do not print a gate address of the form `\u003Ctrack>.\u003Cstage>`.\n",{"name":5,"description":7,"argument-hint":57},"[sdd|sources|iso|research] [topic]","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Farchcore-ai\u002Fplugin\u002Fskills\u002Fplan",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plan",{"tool":74,"command":75},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plan",{"tool":77,"command":78},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Farchcore-ai\u002Fplugin\u002Fskills\u002Fplan\u002FSKILL.md",true,[],[83,93,101,109,117,125],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":92},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":92},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":92},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":92},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":121,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":92},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":87,"licenseFileUrl":129,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":92},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]