القائمة
Scaffold a new policy repo skeleton outside the current project.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Full dual-flywheel audit — Learning (capture from review) + Pruning (remove dead rules). Periodic charter hygiene.
One-time initial charter scaffold — detect stack, seed state, scaffold idioms, classify sensors, build the globs index.
Run the drift sensor on the current diff — fast pre-verify check that loaded charter rules still match what the code is doing.
Triage the code-debt ledger — review the debt sensor's findings and update corpus/state/code-debt.md.
Regenerate .keystone/INDEX.json — the primitive descriptor index every agent reads at session start.
Capture a learning candidate (surprise, incident, review finding) into .charter/learning/inbox/ for later synthesis.
| name | keystone-new-policy |
| description | Scaffold a new policy repo skeleton outside the current project. |
| tools | ["Read","Write","Edit","Glob","Bash"] |
| model | sonnet |
A policy is a separately-versioned charter fragment that consumer
projects pin in their keystone.json (e.g. an org-wide policy that
ships strict guides). This generator writes a fresh policy repo
skeleton — manifest, charter directory layout, README — that you then
populate and publish.
Unlike the other generators, keystone new policy writes to
./<name>/ in the current working directory, not into an existing
charter install.
From the directory where the policy repo should land:
keystone new policy <name>
Example:
keystone new policy acme-policies
# writes ./acme-policies/{keystone-policy.json, .charter/, README.md, ...}
keystone-policy.json — name, version, required port
declarations, strict locks..charter/ content — guides, sensors, etc.keystone policy add <owner>/<repo>@<version>.See the policy authoring guide for the full policy lifecycle.