| name | project-governance |
| description | Apply the platform-neutral Tier, approval, evidence, and irreversible-action boundaries defined by Agent Engineering Workflow. |
| author | Agent Engineering Workflow |
| version | 3.1.0 |
Project Governance
Use this Skill when a task needs Tier selection, approval routing, Candidate
Review, commit boundaries, or T3 incident follow-up.
Sources of Truth
config/workflow-policy.json — executable Tier and deadline data..workflow/manifest.json — current task, decision, and exact artifacts.docs/workflow/core-lifecycle.md — universal lifecycle and roles.docs/platforms/<runtime>.md — runtime mapping only.
Do not copy Tier thresholds or personal Profile permissions into this Skill.
Procedure
- Run
scripts/check_workflow.py classify --project-root <project>.
- Record the declared Tier and approval evidence in the Manifest.
- Run
scripts/check_workflow.py check --project-root <project>.
- Implement only the declared Task ID and Target Files.
- Generate a Candidate Package before commit.
- Obtain an independent Review Decision when Policy requires it.
- Let the Authorized committer perform the commit.
- Verify and retain the Commit Receipt.
- For T3, audit the incident record until required follow-up is complete.
Authority Boundary
- Coordinator and worker roles do not imply commit authority.
- Approval is scoped to one Candidate ID.
- Commit approval does not imply push, merge, deploy, or cross-project writes.
- Runtime Profile names and local paths belong in environment configuration.
For Hermes, use docs/platforms/hermes.md. The mapping describes capabilities,
not a particular user's Profiles.
