[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WYFCVB7WHPF3NJRYN6JV0B":3,"skill-same:01M6WYFCVB7WHPF3NJRYN6JV0B":115},{"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":72,"commitSha":73,"skillDirectory":74,"forksCount":14,"repositoryHtmlUrl":75,"repositoryHomepageUrl":76,"ownerHtmlUrl":77,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":78,"install":79,"resources":92},"01M6WYFCVB7WHPF3NJRYN6JV0B","scope-management",null,"Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"management","scope management","scope","get","when","Existing","v1","event","keep","sprint","id","containers","project","query","grouping","milestone","manage","log","use","sqlite","2026-11-10 10:12:30",false,"---\nname: scope-management\ndescription: |\n  Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv1\n    id: SKILL-scope-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: processkit\n    layer: 2\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n      - skill: index-management\n        purpose: Query existing entities and keep the SQLite index fresh after writes.\n      - skill: id-management\n        purpose: Allocate unique entity identifiers via central ID generation.\n    provides:\n      primitives: [Scope]\n      mcp_tools:\n        - create_scope\n        - get_scope\n        - transition_scope\n        - list_scopes\n      templates: [scope]\n---\n\n# Scope Management\n\n## Intro\n\nA Scope is a named, bounded container that groups related entities — a sprint,\na milestone, a project, a release, a quarter. WorkItems, Processes, and\nBindings reference scopes to say \"I apply within this container.\"\n\n> **MCP server.** This skill ships a self-contained MCP server at\n> `mcp\u002Fserver.py` (PEP 723 script — requires `uv` and Python ≥ 3.10 on\n> PATH). Agent harnesses reach its tools by reading a single MCP config\n> file at startup, so the contents of `mcp\u002Fmcp-config.json` must be merged\n> into the harness's MCP config and placed at the harness-specific path\n> before this skill is usable. If processkit was installed by an installer,\n> that wiring is the installer's responsibility; if processkit was\n> installed manually, the project owner must do it by hand.\n\n## Overview\n\n### Kinds of scopes\n\n| kind        | Example                                     |\n|-------------|---------------------------------------------|\n| `sprint`    | 2-week iteration boundary                   |\n| `milestone` | Named delivery target                       |\n| `quarter`   | Calendar quarter for OKRs                    |\n| `project`   | Long-lived initiative                       |\n| `release`   | A specific release version                   |\n| `other`     | Custom boundary                             |\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: Scope\nmetadata:\n  id: SCOPE-sprint-42\n  created: 2026-04-01T00:00:00Z\nspec:\n  name: \"Sprint 42\"\n  kind: sprint\n  state: active\n  starts_at: 2026-04-01\n  ends_at: 2026-04-14\n  description: \"Two weeks focused on the lint command and docs-site bootstrap.\"\n  goals:\n    - \"Ship aibox lint v1\"\n    - \"Publish processkit docs-site\"\n---\n```\n\n### Workflow\n\n1. Pick an ID: `SCOPE-\u003Cshort-name>` (e.g., `SCOPE-sprint-42`, `SCOPE-q2-2026`).\n2. Set `kind` and `state` (`planned`\u002F`active`\u002F`completed`\u002F`cancelled`).\n3. Set `starts_at` \u002F `ends_at` for time-bounded scopes.\n4. Write goals as concrete, testable bullet points.\n5. Save to `context\u002Fscopes\u002F`, log `scope.created`.\n\n### Using scopes\n\nReference via `spec.scope: SCOPE-...` on WorkItems, or use a Binding\n(`type: work-scope`) when the scope relationship is temporal and an item\ncan move in or out of scope during its lifetime.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Treating a Scope like a folder.** Scope is a conceptual\n  container, not a directory. Don't move files based on scope\n  membership; reference the SCOPE-ID from entities and let the\n  index resolve membership.\n- **Creating overlapping Scopes that double-count work.** \"Sprint\n  42\" and \"Q2 OKRs\" can both contain the same workitem, but be\n  explicit about which is the primary scope vs which is a\n  secondary categorization. Otherwise reports double-count.\n- **Using `spec.scope` directly when membership is temporal.** If a\n  workitem moves into and out of a sprint over its lifetime, use a\n  Binding (`type: work-scope`) instead of pinning `spec.scope`.\n  The Binding carries `valid_from` \u002F `valid_until`; the field\n  doesn't.\n- **Forgetting to transition Scope state.** Scopes have a\n  lifecycle: `planned → active → completed → cancelled`. A Scope\n  that says `state: active` for six months past its end date\n  poisons every \"what's the current sprint\" query.\n- **Hallucinating SCOPE-IDs.** When asked to add work to \"the\n  current sprint\", call `list_scopes(state: active)` first. Don't\n  invent `SCOPE-sprint-42` if it doesn't exist — create it\n  explicitly via `create_scope`.\n- **Reusing a Scope across different timeframes.** \"Sprint 42\" in\n  Q2 2025 and \"Sprint 42\" in Q2 2026 are different Scopes — same\n  number, different time. Use distinct IDs\n  (`SCOPE-2025-Q2-sprint-42` and `SCOPE-2026-Q2-sprint-42`) so\n  history is unambiguous.\n- **Naming scopes ambiguously.** \"Q1\" without a year is meaningless\n  in three months. Always include the year and the kind in the\n  name; the ID can stay short.\n\n## Full reference\n\n### Fields\n\n| Field         | Type          | Notes                                             |\n|---------------|---------------|---------------------------------------------------|\n| `name`        | string        | Human-readable. Shown in listings.                 |\n| `kind`        | enum          | `sprint`\u002F`milestone`\u002F`quarter`\u002F`project`\u002F`release`\u002F`other` |\n| `state`       | enum          | `planned`\u002F`active`\u002F`completed`\u002F`cancelled`         |\n| `starts_at`   | date          | Optional. For time-bounded scopes.                 |\n| `ends_at`     | date          | Optional.                                          |\n| `goals`       | list[string]  | Concrete outcomes expected.                        |\n| `description` | string        | Longer context.                                    |\n| `parent`      | string        | Optional parent scope (quarter → sprint).          |\n\n### Nested scopes\n\nA sprint can be nested within a quarter via `spec.parent`. Queries resolve\ntransitively: \"all work in Q2 2026\" includes all sprints that sit inside it.\n\n### Closing a scope\n\nWhen a scope ends:\n1. Set `state: completed`.\n2. Log `scope.completed`.\n3. Do not delete the file — historical WorkItems reference it.\n4. Optionally write a retrospective DecisionRecord linked via\n   `spec.related_decisions`.\n","# Scope Management\n\n## Intro\n\nA Scope is a named, bounded container that groups related entities — a sprint,\na milestone, a project, a release, a quarter. WorkItems, Processes, and\nBindings reference scopes to say \"I apply within this container.\"\n\n> **MCP server.** This skill ships a self-contained MCP server at\n> `mcp\u002Fserver.py` (PEP 723 script — requires `uv` and Python ≥ 3.10 on\n> PATH). Agent harnesses reach its tools by reading a single MCP config\n> file at startup, so the contents of `mcp\u002Fmcp-config.json` must be merged\n> into the harness's MCP config and placed at the harness-specific path\n> before this skill is usable. If processkit was installed by an installer,\n> that wiring is the installer's responsibility; if processkit was\n> installed manually, the project owner must do it by hand.\n\n## Overview\n\n### Kinds of scopes\n\n| kind        | Example                                     |\n|-------------|---------------------------------------------|\n| `sprint`    | 2-week iteration boundary                   |\n| `milestone` | Named delivery target                       |\n| `quarter`   | Calendar quarter for OKRs                    |\n| `project`   | Long-lived initiative                       |\n| `release`   | A specific release version                   |\n| `other`     | Custom boundary                             |\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: Scope\nmetadata:\n  id: SCOPE-sprint-42\n  created: 2026-04-01T00:00:00Z\nspec:\n  name: \"Sprint 42\"\n  kind: sprint\n  state: active\n  starts_at: 2026-04-01\n  ends_at: 2026-04-14\n  description: \"Two weeks focused on the lint command and docs-site bootstrap.\"\n  goals:\n    - \"Ship aibox lint v1\"\n    - \"Publish processkit docs-site\"\n---\n```\n\n### Workflow\n\n1. Pick an ID: `SCOPE-\u003Cshort-name>` (e.g., `SCOPE-sprint-42`, `SCOPE-q2-2026`).\n2. Set `kind` and `state` (`planned`\u002F`active`\u002F`completed`\u002F`cancelled`).\n3. Set `starts_at` \u002F `ends_at` for time-bounded scopes.\n4. Write goals as concrete, testable bullet points.\n5. Save to `context\u002Fscopes\u002F`, log `scope.created`.\n\n### Using scopes\n\nReference via `spec.scope: SCOPE-...` on WorkItems, or use a Binding\n(`type: work-scope`) when the scope relationship is temporal and an item\ncan move in or out of scope during its lifetime.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Treating a Scope like a folder.** Scope is a conceptual\n  container, not a directory. Don't move files based on scope\n  membership; reference the SCOPE-ID from entities and let the\n  index resolve membership.\n- **Creating overlapping Scopes that double-count work.** \"Sprint\n  42\" and \"Q2 OKRs\" can both contain the same workitem, but be\n  explicit about which is the primary scope vs which is a\n  secondary categorization. Otherwise reports double-count.\n- **Using `spec.scope` directly when membership is temporal.** If a\n  workitem moves into and out of a sprint over its lifetime, use a\n  Binding (`type: work-scope`) instead of pinning `spec.scope`.\n  The Binding carries `valid_from` \u002F `valid_until`; the field\n  doesn't.\n- **Forgetting to transition Scope state.** Scopes have a\n  lifecycle: `planned → active → completed → cancelled`. A Scope\n  that says `state: active` for six months past its end date\n  poisons every \"what's the current sprint\" query.\n- **Hallucinating SCOPE-IDs.** When asked to add work to \"the\n  current sprint\", call `list_scopes(state: active)` first. Don't\n  invent `SCOPE-sprint-42` if it doesn't exist — create it\n  explicitly via `create_scope`.\n- **Reusing a Scope across different timeframes.** \"Sprint 42\" in\n  Q2 2025 and \"Sprint 42\" in Q2 2026 are different Scopes — same\n  number, different time. Use distinct IDs\n  (`SCOPE-2025-Q2-sprint-42` and `SCOPE-2026-Q2-sprint-42`) so\n  history is unambiguous.\n- **Naming scopes ambiguously.** \"Q1\" without a year is meaningless\n  in three months. Always include the year and the kind in the\n  name; the ID can stay short.\n\n## Full reference\n\n### Fields\n\n| Field         | Type          | Notes                                             |\n|---------------|---------------|---------------------------------------------------|\n| `name`        | string        | Human-readable. Shown in listings.                 |\n| `kind`        | enum          | `sprint`\u002F`milestone`\u002F`quarter`\u002F`project`\u002F`release`\u002F`other` |\n| `state`       | enum          | `planned`\u002F`active`\u002F`completed`\u002F`cancelled`         |\n| `starts_at`   | date          | Optional. For time-bounded scopes.                 |\n| `ends_at`     | date          | Optional.                                          |\n| `goals`       | list[string]  | Concrete outcomes expected.                        |\n| `description` | string        | Longer context.                                    |\n| `parent`      | string        | Optional parent scope (quarter → sprint).          |\n\n### Nested scopes\n\nA sprint can be nested within a quarter via `spec.parent`. Queries resolve\ntransitively: \"all work in Q2 2026\" includes all sprints that sit inside it.\n\n### Closing a scope\n\nWhen a scope ends:\n1. Set `state: completed`.\n2. Log `scope.completed`.\n3. Do not delete the file — historical WorkItems reference it.\n4. Optionally write a retrospective DecisionRecord linked via\n   `spec.related_decisions`.\n",{"name":5,"metadata":44,"description":71},{"processkit":45},{"id":46,"uses":47,"layer":57,"created":58,"version":59,"category":60,"provides":61,"apiVersion":70},"SKILL-scope-management",[48,51,54],{"skill":49,"purpose":50},"event-log","Log events to keep the audit trail accurate after every write.",{"skill":52,"purpose":53},"index-management","Query existing entities and keep the SQLite index fresh after writes.",{"skill":55,"purpose":56},"id-management","Allocate unique entity identifiers via central ID generation.",2,1775433600000,"1.0.0","processkit",{"mcp_tools":62,"templates":67,"primitives":68},[63,64,65,66],"create_scope","get_scope","transition_scope","list_scopes",[21],[69],"Scope","processkit.projectious.work\u002Fv1","Manage Scope entities — bounded containers grouping related work (sprint, milestone, project, quarter). Use when creating or updating a grouping boundary — sprint, milestone, quarter, project, release — that other entities will reference.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":80,"prompt":90,"zipAvailable":91},[81,84,87],{"tool":82,"command":83},"npx","npx skills add projectious-work\u002Fprocesskit --skill scope-management",{"tool":85,"command":86},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill scope-management",{"tool":88,"command":89},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill scope-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002FSKILL.md",true,[93,99,105,109],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fscope.yaml","ASSET","资产文件",364,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002Fassets\u002Fscope.yaml",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"mcp\u002Fmcp-config.json","REFERENCE","参考文档",204,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002Fmcp\u002Fmcp-config.json",{"path":106,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":107,"sourceHtmlUrl":108},"mcp\u002FSERVER.md",1082,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002Fmcp\u002FSERVER.md",{"path":110,"resourceType":111,"resourceTypeDesc":112,"sizeBytes":113,"sourceHtmlUrl":114},"mcp\u002Fserver.py","SCRIPT","脚本",8053,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Ftemplates\u002Fprocesskit\u002Fv0.13.0\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fscope-management\u002Fmcp\u002Fserver.py",[116,140,160,178,194,212],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":39},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[19,128,129,130,131,132,133,134,35,135,118,22,136,137,25,138,139],"skill management","create","update","package","alpha","work","list","ontology","as","manifests","skill package","transition",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":39},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[146],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},[19,148,149,150,151,152,132,133,153,154,35,155,156,157,22,158,159],"schema","schema management","MCP","workflows","validation","generated","rebuild","contracts","wed","deterministic","contract","mode",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":39},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[19,167,168,129,130,169,132,133,36,170,171,32,22,172,26,173,174,175,176,177],"proposition","proposition management","index","world","record","creation","interface","updates","facts","claims","WSJF",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"publishedAt":39},"01M6X5KMQ83QN9M6MPWZM7344F","ontology-management","Manage generated v1 ontology entities that do not require a dedicated domain server.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fontology-management\u002FSKILL.md",[],[19,135,185,129,132,186,187,153,188,36,35,189,190,22,191,27,26,192,25,193],"ontology management","lifecycle","archive","roadmap","do","domain","iteration","measurement","generic",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":200,"publishedAt":39},"01M6X5KCY2DN3SM21RERSFNEBT","okf-compatibility","Import, export, and validate conformant Open Knowledge Format bundles.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fokf-compatibility\u002FSKILL.md",[],[201,202,203,204,132,205,206,207,133,208,209,210,211],"okf","compatibility","okf compatibility","validate","open","knowledge","format","export","bundles","bundle","import",{"skillNo":213,"name":214,"nameZh":6,"description":215,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":216,"categories":217,"keywords":218,"publishedAt":39},"01M6X5JA8S5PNGJVFW4EQY8T83","capability-management","Manage versioned Capability entities and their governed lifecycle.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fcapability-management\u002FSKILL.md",[],[19,219,220,129,130,169,132,186,133,134,36,221,35,171,22,27,26,173,222,139],"capability","capability management","queries","changes"]