arbiterForge/codeArbiter / plugins/ca-pi/skills/ca-init
ca-init
UnverifiedOpt this repo into codeArbiter — scaffold the root-level .codearbiter/ state store.
/ca-init — first-run scaffold
Stand up the root-level .codearbiter/ project-state store that opts a repo into arbiter
management. This is the v2 replacement for vendoring/init-vendor: no symlinks, no shims, no dual
root. It writes the activation flag and the empty state files, then hands off to the populator.
.codearbiter/CONTEXT.md frontmatter arbiter: enabled is the single activation flag — it gates
the SessionStart persona injection. The scaffolded
CONTEXT.md is a stub (no initialization sentinel), so after scaffolding the project still needs
populating before normal operation.
Explicit population strategies
--greenfield selects the exact <plugin-root>/skills/ca-decompose/SKILL.md workflow.
--brownfield selects the exact <plugin-root>/skills/ca-create-context/SKILL.md workflow.
That workflow populates an uninitialized stub. For an initialized brownfield
project, keep the existing marker and route source-observed acquisition and
target/delta work to /ca-decompose instead of replaying initial population.
An initialized refresh of existing context facts uses /ca-status drift
and the context-check owner after an explicit scoped or full selection.
Brownfield preparation
Confirm the intended repository, existing state, selected outcome and actual
host permissions before activation. Scaffolding enables governance and may
install Git hooks; it does not prove context correctness or host enforcement.
For existing source, use bounded inspection and the safe installed context
writer in <plugin-root>/routines/context-creation/SKILL.md. Scoped agents are
optional. Ordinary native Windows work does not require a special scout sandbox,
profile attestation or per-document artifact approval.
If a real host permission or the installed safe writer is unavailable, report
the exact operation and retain current state. Continue independent authorized
inspection; do not fabricate a profile, receipt, context document or initialized
marker. Successful scaffold or --check output is inventory, not evidence that
population or a live host probe completed.
The two flags are mutually exclusive and neither may combine with --check. --stage N may
accompany one only while .codearbiter/CONTEXT.md is absent: after checking the repository and host permissions,
scaffold at that stage, then enter the
selected workflow. When an uninitialized stub already exists, skip the refusing scaffolder and enter
the selected workflow directly. An initialized marker selects the initialized
acquisition or refresh owner above; a source-shape mismatch retains the selected
legacy workflow's BLOCK. Without an explicit strategy, continue with the unchanged auto-detection
procedure below under the same repository and host permissions.
Procedure
Before opening an active host session in an unfamiliar repository, a trusted
external process may inspect an explicit directory with
python "<plugin-root>/hooks/init-codearbiter.py" --check --passive --root PATH.
This bounded read checks only that directory's .codearbiter/CONTEXT.md activation
marker and prints a JSON inventory for Git hooks/exclusions, background Git fetch,
update refresh, and inference transport. Every effect is performed: false, with
capability unverified and authorization not_established. The root is caller
supplied and unverified; no Git command, repository script, network request,
global setting edit, or model source read occurs. Sensitive/excluded source paths
must be inventoried separately before any model read. If an active host session
has already started, this inspection cannot undo its earlier startup effects.
Activation is a separate step under the applicable host, network, repository-write, and inference permissions. The normal scaffold and active SessionStart behavior below remain in force for repositories that already opted in.
-
Run the scaffolder against the repo's git toplevel (resolved by the script):
python "<plugin-root>/hooks/init-codearbiter.py"It is idempotent and refuses if
.codearbiter/CONTEXT.mdalready exists — it never overwrites state. Pass--stage Nto set the initial maturity value (default1). Use--checkto report state without creating anything. -
The default creates
.codearbiter/withCONTEXT.md(arbiter: enabled,stage: N,context-format: html, stub body),open-questions.md,overrides.log(audit header),last-checkpoint(0) and.gitattributesexact-byte rules. It does not createopen-tasks.mdordone-tasks.md. The HTML knowledge population step creates the native portable work project identity in the same transaction as the initialized marker. Until then, native work creation refuses; do not create a placeholder task or board.--format markdownretains the legacy Markdown documents and both task boards. An existing HTML project with a legacy board stays legacy until explicit adoption. See<plugin-root>/includes/knowledge.md. -
Then route to the populator — the stub is not yet usable:
- Source code already exists in the repo → route to
/ca-create-context(brownfield: bounded inspection and optional agents read the codebase and synthesize the full context, writing the initialization sentinel). - Greenfield (no meaningful source) → route to
/ca-decompose(resumable interview).
The populator is mandatory, not optional: it authors
tech-stack.md,coding-standards.md, andsecurity-controls.md, or their HTML knowledge documents (and writes the initialization sentinel). The pipeline reads that context —writing-plansandtddneedtech-stack.md, the security gates needsecurity-controls.md— so/ca-featurerun on a freshly-scaffolded stub will STOP at pre-flight until the populator has run. Unknown facts may stay unknown; population does not need every question answered.session-startsurfaces this asNOT INITIALIZEDevery session. - Source code already exists in the repo → route to
-
Report what was created and which populator you are routing to.
When NOT to use
.codearbiter/already scaffolded → the scaffolder refuses; run/ca-create-contextor/ca-decomposeto populate, or/ca-statusto see state.- You only want to re-check detection state → run the scaffolder with
--check.
Hard gate
MUST NOT hand-author .codearbiter/CONTEXT.md frontmatter — the scaffolder is the sanctioned path so
the activation flag and state-file shapes match what the hook parses. MUST NOT mark a
stub initialized; only the populator writes the initialization sentinel.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| algorithmic-artanthropics/skillsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-gainDietrichGebert/ponytailShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact". | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-reviewDietrichGebert/ponytailQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |