Create Policy
In brief: Author a version-controlled policy markdown for a workflow-id so agents resolve project-specific behaviour without re-asking.
When to use
When a default policy is missing, when you need an alternate policy (smoke, staging, weekly upkeep), or when evolving team rules after trying a variant. See Policies.
Prompt
/testchimp create policy run-qa
/testchimp create policy connect-to-test-env
/testchimp create policy for upkeep
Scope
Workflow id required (catalog id such as run-qa, connect-to-test-env). No branch auto-scope.
Policy
N/A (this workflow authors policies). Output goes under plans/knowledge/policies/ with:
---
workflow-id: <catalog-id>
version: <semver>
---
Prefer <workflow-id>.policy.md for the project default; use custom filenames + --policy for variants. Then upsert-policy so the platform has it immediately.
What it does
Interviews for scoping, env, subflows (composites), quality bar, and quirks; writes markdown without rewriting skill playbook steps. Strictest checklist for connect-to-test-env. After write, bump version whenever guidance changes for traceability.