[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6WWMCVMTX20MJ1VM9M9HDBH":3,"skill-same:01M6WWMCVMTX20MJ1VM9M9HDBH":99},{"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":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":72,"commitSha":73,"skillDirectory":74,"forksCount":14,"repositoryHtmlUrl":75,"repositoryHomepageUrl":76,"ownerHtmlUrl":77,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":78,"install":79,"resources":92},"01M6WWMCVMTX20MJ1VM9M9HDBH","process-management",null,"Legacy\u002Fmigration guidance for v1 Process entities — declarative workflow\ndefinitions with roles, gates, and a definition of done. In v2, use\nprocess-instance WorkItems plus Artifact-backed definitions instead of\ncreating new Process records.","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\u002Fskills\u002Fprocesskit\u002Fprocess-management\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"process management","management","process","records","when","declarative","definition","for","v1","with","event","keep","definition of done","gates","done","Legacy","log","use","ids","workflow","2026-11-10 10:12:30",false,"---\nname: process-management\ndescription: |\n  Legacy\u002Fmigration guidance for v1 Process entities — declarative workflow\n  definitions with roles, gates, and a definition of done. In v2, use\n  process-instance WorkItems plus Artifact-backed definitions instead of\n  creating new Process records.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-process-management\n    version: \"1.0.0\"\n    created: 2026-04-06T00:00:00Z\n    category: processkit\n    layer: 3\n    uses:\n      - skill: event-log\n        purpose: Log events to keep the audit trail accurate after every write.\n      - skill: role-management\n        purpose: Resolve Role IDs when entities need role-based assignment.\n      - skill: gate-management\n        purpose: Evaluate gate conditions before allowing transitions.\n    provides:\n      primitives: [Process]\n      templates: [process]\n---\n\n# Process Management\n\n## Intro\n\nIn v1, a Process was a declarative workflow definition: a sequence of\nsteps, roles, gates, and a definition of done. In v2, Process is not a\nfirst-class primitive authoring surface. Model a concrete run as a\nWorkItem with `spec.type: process-instance`, keep the reusable definition\nas an Artifact, and attach gates, scope, time, and budget policy through\nBindings.\n\n## Overview\n\n### Legacy v1 shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: \u003Clegacy Process>\nmetadata:\n  id: PROC-code-review\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: code-review\n  description: \"Review a pull request before merge.\"\n  triggers: [pr.opened, pr.review-requested]\n  roles: [developer, reviewer]\n  steps:\n    - name: author-self-check\n      role: developer\n      uses_skill: code-review\n      description: \"Author runs the self-review checklist.\"\n    - name: peer-review\n      role: reviewer\n      uses_skill: code-review\n      description: \"A different actor reviews the diff and leaves comments.\"\n      gates: [GATE-no-blocking-comments]\n    - name: approval\n      role: reviewer\n      description: \"Reviewer approves the PR.\"\n      gates: [GATE-code-review-passed]\n    - name: merge\n      role: developer\n      description: \"Author merges after approval and CI pass.\"\n      gates: [GATE-ci-passed, GATE-code-review-passed]\n  definition_of_done: \"PR merged with at least one approval, all CI gates passed.\"\n---\n```\n\n### v2 workflow\n\n1. Create or reuse an Artifact that describes the reusable workflow.\n2. Create a WorkItem with `spec.type: process-instance` for each run.\n3. Reference the definition Artifact from the WorkItem.\n4. Attach gates with `Binding(type=workitem-gate)` or\n   `Binding(type=scope-gate)`.\n5. Attach recurrence or active windows with `Binding(type=time-window)`.\n6. Attach cost policy with `Binding(type=budget-application)`.\n\n### Running a v2 process instance\n\nAn agent running a process-instance WorkItem:\n1. Reads the definition Artifact referenced by the WorkItem.\n2. Performs the next action, often guided by a skill.\n3. Evaluates attached Gates and logs `gate.passed` \u002F `gate.failed`.\n4. Transitions the WorkItem through the owning MCP server.\n5. Exits when the WorkItem reaches a terminal state or a blocking gate fails.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Defining a Process without ownership.** Every Process needs an\n  owner Actor — the person or role responsible for keeping it\n  current. Unowned Processes drift and become \"the way we used to\n  do things\".\n- **Process with no termination criteria.** A Process must answer\n  \"how do I know this is done\". Open-ended processes that never\n  terminate become noise; the agent has no signal to stop\n  participating.\n- **Hand-waving \"automated steps\" that aren't actually wired.** If\n  a Process step says \"CI runs automatically\", verify the CI hook\n  exists. A Process that lies about its automation is worse than\n  one that admits everything is manual.\n- **Forgetting to version Process changes.** When a Process\n  definition changes, bump the version. Existing in-flight runs\n  should reference the version they started under, not silently\n  inherit the new rules mid-flight.\n- **Mixing Process steps with WorkItems.** A Process step\n  (\"review the PR\") is reusable across many runs; a WorkItem\n  (\"review BACK-1234\") is one specific instance. Don't put\n  workitem-specific data in the Process definition.\n- **Process documentation without examples.** A Process that says\n  \"follow the release checklist\" without linking to a worked\n  example of a past release is incomplete. Examples are the\n  difference between followable and theoretical.\n- **Authoring a Process for a one-off operation.** If you only run\n  it once, it's a runbook entry or a project log, not a Process.\n  Processes earn their cost through repetition.\n\n## Full reference\n\n### Fields\n\n| Field                | Type          | Notes                                              |\n|----------------------|---------------|----------------------------------------------------|\n| `name`               | string        | kebab-case identifier                              |\n| `description`        | string        | One sentence                                       |\n| `triggers`           | list[string]  | Event types that start the process                 |\n| `roles`              | list[string]  | Role names involved                                |\n| `steps`              | list[object]  | Ordered list; see below                            |\n| `definition_of_done` | string        | The acceptance criterion for the whole process     |\n| `parallel`           | bool          | Default false; true = steps run in parallel        |\n| `retryable`          | bool          | Can the process be re-run if it fails?             |\n\n### Step object\n\n```yaml\n- name: \u003Cstep-name>\n  role: \u003Crole-name>         # who performs this step\n  description: \u003Cone-sentence>\n  uses_skill: \u003Cskill-name>  # optional — skill that guides execution\n  inputs: [\u003Centity-ref>]    # optional — what this step needs\n  outputs: [\u003Centity-ref>]   # optional — what this step produces\n  gates: [\u003Cgate-id>]        # optional — gates that must pass\n  on_failure: \u003Caction>      # halt | retry | skip | escalate\n```\n\n### Parallel vs sequential\n\nDefault is sequential. Set `parallel: true` to run steps concurrently when\nthey are independent. For conditional branching, write multiple processes\nand trigger them conditionally rather than embedding complex logic.\n\n### Applying workflow policy in v2\n\nUse v2 Binding types against the concrete governed entity:\n\n```yaml\nkind: Binding\nspec:\n  type: workitem-gate\n  subject: BACK-release-run\n  target: GATE-security-scan\n  scope: SCOPE-project-x\n```\n\n### No workflow engine\n\nprocesskit does not ship an engine that executes workflows. The\nprocess-instance WorkItem and its definition Artifact form a contract\nbetween the definition and whoever runs it. Agents are the default runners;\nautomation can take over specific steps.\n","# Process Management\n\n## Intro\n\nIn v1, a Process was a declarative workflow definition: a sequence of\nsteps, roles, gates, and a definition of done. In v2, Process is not a\nfirst-class primitive authoring surface. Model a concrete run as a\nWorkItem with `spec.type: process-instance`, keep the reusable definition\nas an Artifact, and attach gates, scope, time, and budget policy through\nBindings.\n\n## Overview\n\n### Legacy v1 shape\n\n```yaml\n---\napiVersion: processkit.projectious.work\u002Fv1\nkind: \u003Clegacy Process>\nmetadata:\n  id: PROC-code-review\n  created: 2026-04-06T00:00:00Z\nspec:\n  name: code-review\n  description: \"Review a pull request before merge.\"\n  triggers: [pr.opened, pr.review-requested]\n  roles: [developer, reviewer]\n  steps:\n    - name: author-self-check\n      role: developer\n      uses_skill: code-review\n      description: \"Author runs the self-review checklist.\"\n    - name: peer-review\n      role: reviewer\n      uses_skill: code-review\n      description: \"A different actor reviews the diff and leaves comments.\"\n      gates: [GATE-no-blocking-comments]\n    - name: approval\n      role: reviewer\n      description: \"Reviewer approves the PR.\"\n      gates: [GATE-code-review-passed]\n    - name: merge\n      role: developer\n      description: \"Author merges after approval and CI pass.\"\n      gates: [GATE-ci-passed, GATE-code-review-passed]\n  definition_of_done: \"PR merged with at least one approval, all CI gates passed.\"\n---\n```\n\n### v2 workflow\n\n1. Create or reuse an Artifact that describes the reusable workflow.\n2. Create a WorkItem with `spec.type: process-instance` for each run.\n3. Reference the definition Artifact from the WorkItem.\n4. Attach gates with `Binding(type=workitem-gate)` or\n   `Binding(type=scope-gate)`.\n5. Attach recurrence or active windows with `Binding(type=time-window)`.\n6. Attach cost policy with `Binding(type=budget-application)`.\n\n### Running a v2 process instance\n\nAn agent running a process-instance WorkItem:\n1. Reads the definition Artifact referenced by the WorkItem.\n2. Performs the next action, often guided by a skill.\n3. Evaluates attached Gates and logs `gate.passed` \u002F `gate.failed`.\n4. Transitions the WorkItem through the owning MCP server.\n5. Exits when the WorkItem reaches a terminal state or a blocking gate fails.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Defining a Process without ownership.** Every Process needs an\n  owner Actor — the person or role responsible for keeping it\n  current. Unowned Processes drift and become \"the way we used to\n  do things\".\n- **Process with no termination criteria.** A Process must answer\n  \"how do I know this is done\". Open-ended processes that never\n  terminate become noise; the agent has no signal to stop\n  participating.\n- **Hand-waving \"automated steps\" that aren't actually wired.** If\n  a Process step says \"CI runs automatically\", verify the CI hook\n  exists. A Process that lies about its automation is worse than\n  one that admits everything is manual.\n- **Forgetting to version Process changes.** When a Process\n  definition changes, bump the version. Existing in-flight runs\n  should reference the version they started under, not silently\n  inherit the new rules mid-flight.\n- **Mixing Process steps with WorkItems.** A Process step\n  (\"review the PR\") is reusable across many runs; a WorkItem\n  (\"review BACK-1234\") is one specific instance. Don't put\n  workitem-specific data in the Process definition.\n- **Process documentation without examples.** A Process that says\n  \"follow the release checklist\" without linking to a worked\n  example of a past release is incomplete. Examples are the\n  difference between followable and theoretical.\n- **Authoring a Process for a one-off operation.** If you only run\n  it once, it's a runbook entry or a project log, not a Process.\n  Processes earn their cost through repetition.\n\n## Full reference\n\n### Fields\n\n| Field                | Type          | Notes                                              |\n|----------------------|---------------|----------------------------------------------------|\n| `name`               | string        | kebab-case identifier                              |\n| `description`        | string        | One sentence                                       |\n| `triggers`           | list[string]  | Event types that start the process                 |\n| `roles`              | list[string]  | Role names involved                                |\n| `steps`              | list[object]  | Ordered list; see below                            |\n| `definition_of_done` | string        | The acceptance criterion for the whole process     |\n| `parallel`           | bool          | Default false; true = steps run in parallel        |\n| `retryable`          | bool          | Can the process be re-run if it fails?             |\n\n### Step object\n\n```yaml\n- name: \u003Cstep-name>\n  role: \u003Crole-name>         # who performs this step\n  description: \u003Cone-sentence>\n  uses_skill: \u003Cskill-name>  # optional — skill that guides execution\n  inputs: [\u003Centity-ref>]    # optional — what this step needs\n  outputs: [\u003Centity-ref>]   # optional — what this step produces\n  gates: [\u003Cgate-id>]        # optional — gates that must pass\n  on_failure: \u003Caction>      # halt | retry | skip | escalate\n```\n\n### Parallel vs sequential\n\nDefault is sequential. Set `parallel: true` to run steps concurrently when\nthey are independent. For conditional branching, write multiple processes\nand trigger them conditionally rather than embedding complex logic.\n\n### Applying workflow policy in v2\n\nUse v2 Binding types against the concrete governed entity:\n\n```yaml\nkind: Binding\nspec:\n  type: workitem-gate\n  subject: BACK-release-run\n  target: GATE-security-scan\n  scope: SCOPE-project-x\n```\n\n### No workflow engine\n\nprocesskit does not ship an engine that executes workflows. The\nprocess-instance WorkItem and its definition Artifact form a contract\nbetween the definition and whoever runs it. Agents are the default runners;\nautomation can take over specific steps.\n",{"name":5,"metadata":49,"description":71},{"processkit":50},{"id":51,"uses":52,"layer":62,"created":63,"version":64,"category":65,"provides":66,"apiVersion":70},"SKILL-process-management",[53,56,59],{"skill":54,"purpose":55},"event-log","Log events to keep the audit trail accurate after every write.",{"skill":57,"purpose":58},"role-management","Resolve Role IDs when entities need role-based assignment.",{"skill":60,"purpose":61},"gate-management","Evaluate gate conditions before allowing transitions.",3,1775433600000,"1.0.0","processkit",{"templates":67,"primitives":68},[26],[69],"Process","processkit.projectious.work\u002Fv2","Legacy\u002Fmigration guidance for v1 Process entities — declarative workflow\ndefinitions with roles, gates, and a definition of done. In v2, use\nprocess-instance WorkItems plus Artifact-backed definitions instead of\ncreating new Process records.\n","main","4876a92620ee792aac2ac9a1a806322d8a572367","archive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fprocess-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 process-management",{"tool":85,"command":86},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill process-management",{"tool":88,"command":89},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill process-management","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fprocess-management\u002FSKILL.md",true,[93],{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"assets\u002Fprocess.yaml","ASSET","资产文件",332,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Farchive\u002Fprocesskit-install-20261101\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fprocess-management\u002Fassets\u002Fprocess.yaml",[100,107,114,120,142,162],{"skillNo":101,"name":102,"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":103,"categories":104,"keywords":105,"publishedAt":106},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":106},"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":115,"name":116,"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":117,"categories":118,"keywords":119,"publishedAt":106},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":127,"publishedAt":44},"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",[126],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[25,128,129,32,130,131,132,133,134,135,136,137,122,138,139,140,141],"skill management","ontology","create","as","work","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":149,"publishedAt":44},"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",[148],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[150,151,25,152,153,154,155,156,157,158,159,160,132,134,135,137,161],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":44},"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",[],[169,25,170,171,130,172,173,174,132,134,175,34,136,176,137,177,178,179,180,40],"proposition management","proposition","interface","claims","record","world","creation","WSJF","index","updates","query","facts"]