[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6ME5911AEQQ6DCBDPMBMJNF":3,"skill-same:01M6ME5911AEQQ6DCBDPMBMJNF":69},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":50,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M6ME5911AEQQ6DCBDPMBMJNF","plan",null,"Plan future work, investigate before building, research a topic, or compare the alternatives for a choice. Takes optional free text. The skill reads the request, open drafts, accepted canon, branch, and code, then creates only the documents a later reader needs — none for a small fix. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'plan the onboarding journey', 'investigate X before we plan', 'compare the alternatives for Y', 'REST or a queue? two teams disagree', 'I need market research before we plan', 'we are regulated — trace the requirements'. With no arguments it resumes an open planning draft or offers what to plan next. 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\u002Farchcore\u002Fskills\u002Fplan\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"branch","new","recording","free","next","journey","later","roadmap","only","fix","redesign","review","work","choice","decision","text","open","code","create","documents","2026-11-10 10:12:30",false,"---\nname: plan\nargument-hint: \"[topic]\"\ndescription: \"Plan future work, investigate before building, research a topic, or compare the alternatives for a choice. Takes optional free text. The skill reads the request, open drafts, accepted canon, branch, and code, then creates only the documents a later reader needs — none for a small fix. Use for 'plan the X redesign', 'create a roadmap', 'plan a new feature', 'plan the onboarding journey', 'investigate X before we plan', 'compare the alternatives for Y', 'REST or a queue? two teams disagree', 'I need market research before we plan', 'we are regulated — trace the requirements'. With no arguments it resumes an open planning draft or offers what to plan next. 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 future work from the project context. Context resolution\n(`skills\u002F_shared\u002Fgate-contract.md`, section Context resolution) records the\nclaims, unknowns, hazards, and authority; the conductor\n(`skills\u002F_shared\u002Fdelta-routing.md`) selects the documents a later reader needs;\ninstruments produce them. Vision types are the primary output. 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 a new feature for CSV export\" → typically one `spec` and one `plan`\n- \"Upgrade the HTTP client across three services with a coordinated rollout\" → a `plan` alone\n- \"Plan the notifications platform\" → a `prd`, one `spec` per capability, one `plan`\n- \"Fix the typo in the onboarding copy\" → no document; implement directly\n- \"I need market research before we plan\" → acquisition instrument\n- \"We must trace these requirements for the auditor\" → only the requirement levels that obligation names\n- \"Investigate X before we plan\" → `research`; \"Compare the alternatives for Y\" → `rnd`\n- \"REST or a queue for SAP? Two teams disagree\", with the facts of both options recorded → `rfc`\n- `research \u003Ctopic>` as the first word → the type `research`\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## Entry\n\nApply in this order:\n\n| Signal | Action |\n|---|---|\n| No arguments, one draft with a state block this command resumes | Resume it at its earliest incomplete gate |\n| No arguments, several such drafts | Resume rule 10 in `skills\u002F_shared\u002Fgate-contract.md` |\n| No arguments, a clear request in the session or one unfinished plan | Offer a start menu of at most four items, each with the evidence that names it, the recommended item first |\n| No arguments and no reliable signal | Ask one question — what outcome to plan; a dirty branch alone is not a target |\n| The first word is a type slug | The explicit type request per `explicit-type-request-wins.adr`; a leading `research` requests the type `research` |\n| Any other request | Context resolution, then Selection per `skills\u002F_shared\u002Fdelta-routing.md` |\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` only when the evidence to choose\nis missing; any other investigation produces `research`. WHEN the deciding facts\nare already recorded and the open part is whose weights win — two owners\ndisagree, or the owner has not chosen — the decision instrument records an\n`rfc`, and no `rnd` is created. A standalone external material is filed through\n`\u002Farchcore:document`. A request proposing a specific target for team review\n(\"let's adopt Y\", \"draft an RFC for Y\") belongs to `\u002Farchcore:document`'s\ndecision instrument; a lone \"should we switch to Y\" with the evidence to choose\nmissing stays here as `rnd`.\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\nselection 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 selection\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 owner documents whose referenced paths changed after them — the staleness input to Selection.\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 the session root holds no `.archcore\u002F`, THEN follow `skills\u002F_shared\u002Ftarget-project.md`, section Projects without `.archcore\u002F`: name the roots the session recap listed, ask which project to use or whether to initialize the session root, and do not call `mcp__archcore__init_project` before the answer.\n\n**Global sources.** If a `list_documents` \u002F `search_documents` result has `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. Edit a global\ndocument only through its source project, per that file's write convention, and\nnever join a local and a global document with `add_relation`. Absent any global\nmatch, proceed as usual.\n\n### 2. Select\n\nBuild the context record per `skills\u002F_shared\u002Fgate-contract.md`, section Context\nresolution, then run Selection per `skills\u002F_shared\u002Fdelta-routing.md` and report\nits selection line. Never ask the user to choose an instrument.\n\n### 3. Budget\n\nInterview mechanics, question form, and the ceiling of 5 questions per\ninvocation: `skills\u002F_shared\u002Felicitation-contract.md`.\n\n### 4. Execute the selection\n\nInvoke each selected instrument, 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 `claims:` field this command adds), 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 selection 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 selection produced no `plan` document, skip to Result — the exit gate\nor the selection line names the follow-ups.\n\n### 6. Implement fork\n\nWHEN a blocking exit check stopped the selection, skip this step and go to Result.\nOtherwise, offer 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 selection line, and the inferred scope when no argument set it.\n- Produced documents grouped by category — vision, knowledge, experience — with each document's path and status. WHEN the request named more than one target project, list each document beside its project root per `skills\u002F_shared\u002Ftarget-project.md`.\n- Relations created, plus candidate `mcp__archcore__add_relation` targets among existing documents, or a statement that none match.\n- `retire` claims reported for closeout discharge, when any exist.\n- Next actions, naming only v2 commands: `\u002Farchcore:plan` to continue the selection, `\u002Farchcore:document \u003Csubject>` to record a decision or document code touched during implementation, `\u002Farchcore:review` to check the implementation against the recorded plan and reconcile its Declared Delta.\n- WHEN contract drafting remains open on a material user-owned choice, name the draft `spec`, the unanswered choice, and the behavior it changes. Do not offer implementation until that check passes. Name the three ways to continue — answer the choice, delegate it (\"you decide\"), or proceed anyway — and the resume command `\u002Farchcore:plan \u003Cspec title>`.\n- Name instruments and stages in plain words; do not print a gate address of the form `\u003Ctrack>.\u003Cstage>`.\n","# \u002Farchcore:plan\n\nPlan future work from the project context. Context resolution\n(`skills\u002F_shared\u002Fgate-contract.md`, section Context resolution) records the\nclaims, unknowns, hazards, and authority; the conductor\n(`skills\u002F_shared\u002Fdelta-routing.md`) selects the documents a later reader needs;\ninstruments produce them. Vision types are the primary output. 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 a new feature for CSV export\" → typically one `spec` and one `plan`\n- \"Upgrade the HTTP client across three services with a coordinated rollout\" → a `plan` alone\n- \"Plan the notifications platform\" → a `prd`, one `spec` per capability, one `plan`\n- \"Fix the typo in the onboarding copy\" → no document; implement directly\n- \"I need market research before we plan\" → acquisition instrument\n- \"We must trace these requirements for the auditor\" → only the requirement levels that obligation names\n- \"Investigate X before we plan\" → `research`; \"Compare the alternatives for Y\" → `rnd`\n- \"REST or a queue for SAP? Two teams disagree\", with the facts of both options recorded → `rfc`\n- `research \u003Ctopic>` as the first word → the type `research`\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## Entry\n\nApply in this order:\n\n| Signal | Action |\n|---|---|\n| No arguments, one draft with a state block this command resumes | Resume it at its earliest incomplete gate |\n| No arguments, several such drafts | Resume rule 10 in `skills\u002F_shared\u002Fgate-contract.md` |\n| No arguments, a clear request in the session or one unfinished plan | Offer a start menu of at most four items, each with the evidence that names it, the recommended item first |\n| No arguments and no reliable signal | Ask one question — what outcome to plan; a dirty branch alone is not a target |\n| The first word is a type slug | The explicit type request per `explicit-type-request-wins.adr`; a leading `research` requests the type `research` |\n| Any other request | Context resolution, then Selection per `skills\u002F_shared\u002Fdelta-routing.md` |\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` only when the evidence to choose\nis missing; any other investigation produces `research`. WHEN the deciding facts\nare already recorded and the open part is whose weights win — two owners\ndisagree, or the owner has not chosen — the decision instrument records an\n`rfc`, and no `rnd` is created. A standalone external material is filed through\n`\u002Farchcore:document`. A request proposing a specific target for team review\n(\"let's adopt Y\", \"draft an RFC for Y\") belongs to `\u002Farchcore:document`'s\ndecision instrument; a lone \"should we switch to Y\" with the evidence to choose\nmissing stays here as `rnd`.\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\nselection 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 selection\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 owner documents whose referenced paths changed after them — the staleness input to Selection.\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 the session root holds no `.archcore\u002F`, THEN follow `skills\u002F_shared\u002Ftarget-project.md`, section Projects without `.archcore\u002F`: name the roots the session recap listed, ask which project to use or whether to initialize the session root, and do not call `mcp__archcore__init_project` before the answer.\n\n**Global sources.** If a `list_documents` \u002F `search_documents` result has `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. Edit a global\ndocument only through its source project, per that file's write convention, and\nnever join a local and a global document with `add_relation`. Absent any global\nmatch, proceed as usual.\n\n### 2. Select\n\nBuild the context record per `skills\u002F_shared\u002Fgate-contract.md`, section Context\nresolution, then run Selection per `skills\u002F_shared\u002Fdelta-routing.md` and report\nits selection line. Never ask the user to choose an instrument.\n\n### 3. Budget\n\nInterview mechanics, question form, and the ceiling of 5 questions per\ninvocation: `skills\u002F_shared\u002Felicitation-contract.md`.\n\n### 4. Execute the selection\n\nInvoke each selected instrument, 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 `claims:` field this command adds), 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 selection 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 selection produced no `plan` document, skip to Result — the exit gate\nor the selection line names the follow-ups.\n\n### 6. Implement fork\n\nWHEN a blocking exit check stopped the selection, skip this step and go to Result.\nOtherwise, offer 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 selection line, and the inferred scope when no argument set it.\n- Produced documents grouped by category — vision, knowledge, experience — with each document's path and status. WHEN the request named more than one target project, list each document beside its project root per `skills\u002F_shared\u002Ftarget-project.md`.\n- Relations created, plus candidate `mcp__archcore__add_relation` targets among existing documents, or a statement that none match.\n- `retire` claims reported for closeout discharge, when any exist.\n- Next actions, naming only v2 commands: `\u002Farchcore:plan` to continue the selection, `\u002Farchcore:document \u003Csubject>` to record a decision or document code touched during implementation, `\u002Farchcore:review` to check the implementation against the recorded plan and reconcile its Declared Delta.\n- WHEN contract drafting remains open on a material user-owned choice, name the draft `spec`, the unanswered choice, and the behavior it changes. Do not offer implementation until that check passes. Name the three ways to continue — answer the choice, delegate it (\"you decide\"), or proceed anyway — and the resume command `\u002Farchcore:plan \u003Cspec title>`.\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":44},"[topic]","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Farchcore-ai\u002Farchcore\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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plan",{"tool":61,"command":62},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill plan",{"tool":64,"command":65},"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\u002Farchcore\u002Fskills\u002Fplan\u002FSKILL.md",true,[],[70,80,88,96,104,112],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":74,"licenseFileUrl":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":79},"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",[],[]]