Menu
Scaffold a new lifecycle action (atomic unit of work) at the canonical path.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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-action |
| description | Scaffold a new lifecycle action (atomic unit of work) at the canonical path. |
| tools | ["Read","Write","Edit","Glob","Bash"] |
| model | sonnet |
An action is one atomic unit of lifecycle work, invoked by name
(by a playbook, another action, the menu file, or the user). Default
actions ship with every install: spec, orient, verify, review,
learn, audit, bootstrap, mode, synthesize, check-drift.
Custom actions for project-specific lifecycle phases live alongside.
Actions live at .charter/actions/<name>.md (flat, no topic
directory — actions are global by name across the cascade).
keystone new action <name>
Example:
keystone new action release-notes
# writes .charter/actions/release-notes.md
## Entry condition — what must be true before this action
runs.## Activities — a numbered list of verb + artifact steps.## Exit condition — what must be true when the action
completes.deps:
frontmatter so the indexer can build the graph.keystone index to refresh the descriptor surface.Full port contract:
docs/ports/action.md.