[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NQHX6W1X034F0N7KH6DCWD":3,"skill-same:01M6NQHX6W1X034F0N7KH6DCWD":119},{"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":73,"commitSha":74,"skillDirectory":75,"forksCount":14,"repositoryHtmlUrl":76,"repositoryHomepageUrl":77,"ownerHtmlUrl":78,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":79,"install":80,"resources":93},"01M6NQHX6W1X034F0N7KH6DCWD","role-management",null,"Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.","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\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"role management","management","role","roles","Existing","can","event","keep","tech","id","fresh","create","get","project","query","maintain","log","use","reviewer","sqlite","2026-11-10 10:12:30",false,"---\nname: role-management\ndescription: |\n  Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-role-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: processkit\n    layer: 1\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: [Role]\n      mcp_tools:\n        - create_role\n        - get_role\n        - update_role\n        - list_roles\n        - link_role_to_actor\n      templates: [role]\n---\n\n# Role Management\n\n## Intro\n\nA Role is a named set of responsibilities that an Actor can fill. Roles\ndescribe what — not who. \"Alice is a developer\" is a Binding between Actor\n`ACTOR-alice` and Role `ROLE-developer`; this skill manages the Role side of\nthat relationship.\n\n**Important:** Roles in processkit have no enforcement semantics. They are\ndescriptive, not restrictive. RBAC enforcement is out of scope\n(see DISC-002 \u002F DEC-017).\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### When to create a Role\n\nCreate a Role when:\n- A responsibility recurs across multiple work items or processes.\n- You need to refer to \"the person who X\" without naming a specific actor.\n- A process template references the role (\"the reviewer must …\").\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Role\nmetadata:\n  id: ROLE-reviewer\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: reviewer\n  description: \"Reviews code and documentation changes before merge.\"\n  responsibilities:\n    - \"Read PRs within 48 hours of request\"\n    - \"Approve or request changes with actionable feedback\"\n    - \"Block merges on security or correctness concerns\"\n  skills_required: [code-review, debugging]\n  default_scope: project      # project | sprint | permanent\n---\n\nOptional body: elaboration, examples, anti-patterns.\n```\n\n### Workflow\n\n1. Pick an ID: `ROLE-\u003Cname>` where name is kebab-case and unique.\n2. Write a one-sentence `description` — the role's purpose.\n3. List concrete `responsibilities` as imperative bullet points.\n4. Optionally list `skills_required` — links to skill IDs that describe the\n   capabilities this role depends on.\n5. Save to `context\u002Froles\u002F`.\n6. Log `role.created`.\n\n### Assigning actors to roles\n\n**Do not list actor IDs in the Role file.** Assignments go in Binding entities\nso they can be scoped, time-bounded, and changed without editing the Role.\n\n```yaml\nkind: Binding\nspec:\n  type: role-assignment\n  subject: ACTOR-alice\n  target: ROLE-reviewer\n  scope: SCOPE-project-x    # optional\n```\n\nSee `skills\u002Fbinding-management`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Confusing Role with Actor.** A Role is a named set of\n  responsibilities (\"tech-lead\", \"release-manager\"). An Actor is a\n  person or agent who can FILL a role. \"Alice is the tech lead\" is\n  a Binding from `ACTOR-alice` to `ROLE-tech-lead`, not an update\n  to either entity.\n- **Creating a Role for one specific person.** \"Alice's\n  responsibilities\" is not a Role; it's just Alice. Roles capture\n  responsibilities that can be transferred between people. If only\n  one person could ever fill it, it's a job title, not a Role.\n- **Treating Role membership as RBAC enforcement.** Roles are\n  descriptive, not restrictive. processkit does not check whether\n  an actor is \"allowed\" to do something based on their Role.\n  Authorization is out of scope — Roles document who SHOULD do\n  what, not who is permitted to.\n- **Renaming a Role instead of creating a new one.** Renaming\n  silently rewrites history — every old Binding now points at a\n  Role with a different meaning. If the responsibilities have\n  genuinely changed, create a new Role and end the old Bindings;\n  don't overwrite.\n- **Putting tasks in `responsibilities` instead of WorkItems.** The\n  `responsibilities` field describes ongoing duties (\"review PRs\",\n  \"approve releases\"), not specific to-dos. If you find yourself\n  writing \"implement feature X\" in responsibilities, that's a\n  WorkItem.\n- **Vague responsibility lists.** \"Ensures quality\" is not a\n  responsibility; \"Reviews every PR before merge to main\" is. Each\n  bullet should be concrete enough that you could ask a holder\n  \"did you do this last week\" and get a yes\u002Fno answer.\n- **Forgetting to log `role.created` \u002F `role.updated`.** The audit\n  trail tracks role evolution. Skipping the log makes \"when did we\n  add the security-reviewer role\" unanswerable.\n\n## Full reference\n\n### Fields\n\n| Field              | Type          | Notes                                                    |\n|--------------------|---------------|----------------------------------------------------------|\n| `name`             | string        | Kebab-case. Matches the suffix of `metadata.id`.         |\n| `description`      | string        | One sentence. Shown in role listings.                    |\n| `responsibilities` | list[string]  | Imperative bullet points. Concrete, not vague.           |\n| `skills_required`  | list[string]  | Skill IDs or names. Advisory, not enforced.              |\n| `default_scope`    | enum          | `project` \u002F `sprint` \u002F `permanent`. Default assumption for Bindings. |\n| `supersedes`       | string        | Role ID this one replaces (for role renames\u002Freorg).      |\n\n### Roles vs Categories vs Gates\n\nBeginners sometimes conflate three related concepts:\n\n- **Role** — who does a thing (reviewer, developer, release-manager).\n- **Category** — how a thing is classified (bug, feature, tech-debt).\n- **Gate** — a checkpoint that validates a thing (code-review-passed).\n\nA Role can be assigned via Binding; a Category is a label; a Gate is\nsomething a process has to pass. Don't model one as another.\n\n### No enforcement\n\nprocesskit does not check that an actor filling a role has the right\n`skills_required`, or that actions restricted to a role are only performed\nby bound actors. Roles are descriptive. If you need RBAC, that's a\ngovernance platform concern (DEC-017).\n\n### Well-known roles\n\nprocesskit does not ship a canonical list of roles — they vary too much per\nproject. But these are common enough to be mentioned here for naming\nconsistency: `developer`, `reviewer`, `tech-lead`, `release-manager`,\n`incident-commander`, `product-owner`, `designer`, `security-reviewer`.\nProjects are free to use these names or invent their own.\n","# Role Management\n\n## Intro\n\nA Role is a named set of responsibilities that an Actor can fill. Roles\ndescribe what — not who. \"Alice is a developer\" is a Binding between Actor\n`ACTOR-alice` and Role `ROLE-developer`; this skill manages the Role side of\nthat relationship.\n\n**Important:** Roles in processkit have no enforcement semantics. They are\ndescriptive, not restrictive. RBAC enforcement is out of scope\n(see DISC-002 \u002F DEC-017).\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### When to create a Role\n\nCreate a Role when:\n- A responsibility recurs across multiple work items or processes.\n- You need to refer to \"the person who X\" without naming a specific actor.\n- A process template references the role (\"the reviewer must …\").\n\n### Shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv2\nkind: Role\nmetadata:\n  id: ROLE-reviewer\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: reviewer\n  description: \"Reviews code and documentation changes before merge.\"\n  responsibilities:\n    - \"Read PRs within 48 hours of request\"\n    - \"Approve or request changes with actionable feedback\"\n    - \"Block merges on security or correctness concerns\"\n  skills_required: [code-review, debugging]\n  default_scope: project      # project | sprint | permanent\n---\n\nOptional body: elaboration, examples, anti-patterns.\n```\n\n### Workflow\n\n1. Pick an ID: `ROLE-\u003Cname>` where name is kebab-case and unique.\n2. Write a one-sentence `description` — the role's purpose.\n3. List concrete `responsibilities` as imperative bullet points.\n4. Optionally list `skills_required` — links to skill IDs that describe the\n   capabilities this role depends on.\n5. Save to `context\u002Froles\u002F`.\n6. Log `role.created`.\n\n### Assigning actors to roles\n\n**Do not list actor IDs in the Role file.** Assignments go in Binding entities\nso they can be scoped, time-bounded, and changed without editing the Role.\n\n```yaml\nkind: Binding\nspec:\n  type: role-assignment\n  subject: ACTOR-alice\n  target: ROLE-reviewer\n  scope: SCOPE-project-x    # optional\n```\n\nSee `skills\u002Fbinding-management`.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Confusing Role with Actor.** A Role is a named set of\n  responsibilities (\"tech-lead\", \"release-manager\"). An Actor is a\n  person or agent who can FILL a role. \"Alice is the tech lead\" is\n  a Binding from `ACTOR-alice` to `ROLE-tech-lead`, not an update\n  to either entity.\n- **Creating a Role for one specific person.** \"Alice's\n  responsibilities\" is not a Role; it's just Alice. Roles capture\n  responsibilities that can be transferred between people. If only\n  one person could ever fill it, it's a job title, not a Role.\n- **Treating Role membership as RBAC enforcement.** Roles are\n  descriptive, not restrictive. processkit does not check whether\n  an actor is \"allowed\" to do something based on their Role.\n  Authorization is out of scope — Roles document who SHOULD do\n  what, not who is permitted to.\n- **Renaming a Role instead of creating a new one.** Renaming\n  silently rewrites history — every old Binding now points at a\n  Role with a different meaning. If the responsibilities have\n  genuinely changed, create a new Role and end the old Bindings;\n  don't overwrite.\n- **Putting tasks in `responsibilities` instead of WorkItems.** The\n  `responsibilities` field describes ongoing duties (\"review PRs\",\n  \"approve releases\"), not specific to-dos. If you find yourself\n  writing \"implement feature X\" in responsibilities, that's a\n  WorkItem.\n- **Vague responsibility lists.** \"Ensures quality\" is not a\n  responsibility; \"Reviews every PR before merge to main\" is. Each\n  bullet should be concrete enough that you could ask a holder\n  \"did you do this last week\" and get a yes\u002Fno answer.\n- **Forgetting to log `role.created` \u002F `role.updated`.** The audit\n  trail tracks role evolution. Skipping the log makes \"when did we\n  add the security-reviewer role\" unanswerable.\n\n## Full reference\n\n### Fields\n\n| Field              | Type          | Notes                                                    |\n|--------------------|---------------|----------------------------------------------------------|\n| `name`             | string        | Kebab-case. Matches the suffix of `metadata.id`.         |\n| `description`      | string        | One sentence. Shown in role listings.                    |\n| `responsibilities` | list[string]  | Imperative bullet points. Concrete, not vague.           |\n| `skills_required`  | list[string]  | Skill IDs or names. Advisory, not enforced.              |\n| `default_scope`    | enum          | `project` \u002F `sprint` \u002F `permanent`. Default assumption for Bindings. |\n| `supersedes`       | string        | Role ID this one replaces (for role renames\u002Freorg).      |\n\n### Roles vs Categories vs Gates\n\nBeginners sometimes conflate three related concepts:\n\n- **Role** — who does a thing (reviewer, developer, release-manager).\n- **Category** — how a thing is classified (bug, feature, tech-debt).\n- **Gate** — a checkpoint that validates a thing (code-review-passed).\n\nA Role can be assigned via Binding; a Category is a label; a Gate is\nsomething a process has to pass. Don't model one as another.\n\n### No enforcement\n\nprocesskit does not check that an actor filling a role has the right\n`skills_required`, or that actions restricted to a role are only performed\nby bound actors. Roles are descriptive. If you need RBAC, that's a\ngovernance platform concern (DEC-017).\n\n### Well-known roles\n\nprocesskit does not ship a canonical list of roles — they vary too much per\nproject. But these are common enough to be mentioned here for naming\nconsistency: `developer`, `reviewer`, `tech-lead`, `release-manager`,\n`incident-commander`, `product-owner`, `designer`, `security-reviewer`.\nProjects are free to use these names or invent their own.\n",{"name":5,"metadata":44,"description":72},{"processkit":45},{"id":46,"uses":47,"layer":57,"created":58,"version":59,"category":60,"provides":61,"apiVersion":71},"SKILL-role-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.",1,1775433600000,"1.0.0","processkit",{"mcp_tools":62,"templates":68,"primitives":69},[63,64,65,66,67],"create_role","get_role","update_role","list_roles","link_role_to_actor",[21],[70],"Role","processkit.projectious.work\u002Fv2","Create and maintain Role entities — named sets of responsibilities that actors can fill. Use when defining a new role in the project (developer, reviewer, tech-lead, release-manager) or updating an existing role's responsibilities.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-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":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add projectious-work\u002Fprocesskit --skill role-management",{"tool":86,"command":87},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill role-management",{"tool":89,"command":90},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill role-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002FSKILL.md",true,[94,100,106,110,116],{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"assets\u002Frole.yaml","ASSET","资产文件",4361,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002Fassets\u002Frole.yaml",{"path":101,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":104,"sourceHtmlUrl":105},"mcp\u002Fmcp-config.json","REFERENCE","参考文档",213,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002Fmcp\u002Fmcp-config.json",{"path":107,"resourceType":102,"resourceTypeDesc":103,"sizeBytes":108,"sourceHtmlUrl":109},"mcp\u002FSERVER.md",1805,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002Fmcp\u002FSERVER.md",{"path":111,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":114,"sourceHtmlUrl":115},"mcp\u002Fserver.py","SCRIPT","脚本",13649,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002Fmcp\u002Fserver.py",{"path":117,"resourceType":112,"resourceTypeDesc":113,"sizeBytes":14,"sourceHtmlUrl":118},"scripts\u002F.gitkeep","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Frole-management\u002Fscripts\u002F.gitkeep",[120,127,134,140,165,185],{"skillNo":121,"name":122,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":126},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":126},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":126},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"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":151,"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",[146],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[20,152,153,154,30,155,156,157,31,158,159,160,142,161,162,163,164],"skill management","ontology","v1","as","work","transition","manage","update","alpha","list","package","skill package","manifests",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":172,"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",[171],{"categoryNo":147,"categoryName":148,"taxonomyType":149,"taxonomyTypeDesc":150},[173,174,20,175,176,177,178,179,180,181,182,183,156,31,158,160,184],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"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":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",[],[192,20,193,194,30,195,196,197,156,31,198,25,159,199,160,200,201,33,202,35],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","facts"]