process-management
Manage Process entities — declarative sequences of steps with roles, gates, and a definition of done. Use when defining a reusable workflow — code review, release, incident response, onboarding — that the project wants to run consistently.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- process-management
- metadata
- { "processkit": { "id": "SKILL-process-management", "uses": [ { "skill": "event-log", "purpose": "Log events to keep the audit trail accurate after every write." }, { "skill": "role-management", "purpose": "Resolve Role IDs when entities need role-based assignment." }, { "skill": "gate-management", "purpose": "Evaluate gate conditions before allowing transitions." } ], "layer": 3, "created": 1775433600000, "version": "1.0.0", "category": "processkit", "provides": { "templates": [ "process" ], "primitives": [ "Process" ] }, "apiVersion": "processkit.projectious.work/v1" } }
- description
- Manage Process entities — declarative sequences of steps with roles, gates, and a definition of done. Use when defining a reusable workflow — code review, release, incident response, onboarding — that the project wants to run consistently.
02 资源文件 1
- 资产文件assets/process.yaml342 B
03 SKILL.md 正文
Process Management
Intro
A Process is a declarative definition of a workflow: a sequence of steps, the roles involved, the gates that must pass, and the definition of done. processkit does NOT execute processes — agents and humans do. processkit just defines them.
Overview
Shape
---
apiVersion: processkit.projectious.work/v1
kind: Process
metadata:
id: PROC-code-review
created: 2026-04-06T00:00:00Z
spec:
name: code-review
description: "Review a pull request before merge."
triggers: [pr.opened, pr.review-requested]
roles: [developer, reviewer]
steps:
- name: author-self-check
role: developer
uses_skill: code-review
description: "Author runs the self-review checklist."
- name: peer-review
role: reviewer
uses_skill: code-review
description: "A different actor reviews the diff and leaves comments."
gates: [GATE-no-blocking-comments]
- name: approval
role: reviewer
description: "Reviewer approves the PR."
gates: [GATE-code-review-passed]
- name: merge
role: developer
description: "Author merges after approval and CI pass."
gates: [GATE-ci-passed, GATE-code-review-passed]
definition_of_done: "PR merged with at least one approval, all CI gates passed."
---
Workflow
- Pick
PROC-<name>. - List
triggers— events that kick off the process. - List required
roles. - Define
stepsin order. Each step names the actor role, optional skill, description, and gates. - Write a clear
definition_of_done. - Save to
context/processes/.
Running a process
An agent running a process:
- Detects the trigger.
- Walks the steps in order.
- For each step, performs the action (often guided by
uses_skill). - Validates gates at each step — logs
gate.passed/gate.failed. - Logs
process.step.started/process.step.completed. - Exits when the last step completes or a blocking gate fails.
Gotchas
Agent-specific failure modes — provider-neutral pause-and-self-check items:
- Defining a Process without ownership. Every Process needs an owner Actor — the person or role responsible for keeping it current. Unowned Processes drift and become "the way we used to do things".
- Process with no termination criteria. A Process must answer "how do I know this is done". Open-ended processes that never terminate become noise; the agent has no signal to stop participating.
- Hand-waving "automated steps" that aren't actually wired. If a Process step says "CI runs automatically", verify the CI hook exists. A Process that lies about its automation is worse than one that admits everything is manual.
- Forgetting to version Process changes. When a Process definition changes, bump the version. Existing in-flight runs should reference the version they started under, not silently inherit the new rules mid-flight.
- Mixing Process steps with WorkItems. A Process step ("review the PR") is reusable across many runs; a WorkItem ("review BACK-1234") is one specific instance. Don't put workitem-specific data in the Process definition.
- Process documentation without examples. A Process that says "follow the release checklist" without linking to a worked example of a past release is incomplete. Examples are the difference between followable and theoretical.
- Authoring a Process for a one-off operation. If you only run it once, it's a runbook entry or a project log, not a Process. Processes earn their cost through repetition.
Full reference
Fields
| Field | Type | Notes |
|---|---|---|
name |
string | kebab-case identifier |
description |
string | One sentence |
triggers |
list[string] | Event types that start the process |
roles |
list[string] | Role names involved |
steps |
list[object] | Ordered list; see below |
definition_of_done |
string | The acceptance criterion for the whole process |
parallel |
bool | Default false; true = steps run in parallel |
retryable |
bool | Can the process be re-run if it fails? |
Step object
- name: <step-name>
role: <role-name> # who performs this step
description: <one-sentence>
uses_skill: <skill-name> # optional — skill that guides execution
inputs: [<entity-ref>] # optional — what this step needs
outputs: [<entity-ref>] # optional — what this step produces
gates: [<gate-id>] # optional — gates that must pass
on_failure: <action> # halt | retry | skip | escalate
Parallel vs sequential
Default is sequential. Set parallel: true to run steps concurrently when
they are independent. For conditional branching, write multiple processes
and trigger them conditionally rather than embedding complex logic.
Scoping a process
Use a Binding (type: process-scope) to apply a process to a specific
project or team:
kind: Binding
spec:
type: process-scope
subject: PROC-code-review
target: SCOPE-project-x
No workflow engine
processkit does not ship an engine that executes processes. The Process definition is a contract between the definition and whoever runs it. Agents are the default runners; automation can take over specific steps.
04 同仓库更多 Skills
standard-ui-design
暂无简介
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.
standard-agent-building
暂无简介
skill-management
Manage Skill package manifests as v1 ontology entities.
schema-management
Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.
proposition-management
Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.