From arcforge
Manages the lifecycle of optional learning candidates: queues observations, enables review via dashboard, and controls activation of artifacts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arcforge:arc-learningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`arc-learning` turns repeated project observations into reviewable learning candidates. Learning is **disabled by default**, **automatic once enabled**, and conservative at every behavior-change boundary.
arc-learning turns repeated project observations into reviewable learning candidates. Learning is disabled by default, automatic once enabled, and conservative at every behavior-change boundary.
Position: observations → candidate queue → dashboard review → inactive drafts → explicit activation → active artifacts
The primary interface for reviewing and acting on candidates is the dashboard (arcforge learn dashboard). Candidates are queued automatically by the observer daemon's LLM curator; the dashboard is where the human reviewer approves, dismisses, materializes, activates, promotes, or deactivates them.
The default scope is project-local. Promotion to global scope is an explicit dashboard action; silent auto-promotion to global remains unsupported — the dashboard's Promote action is the only path, and it requires explicit user authorization.
Primary surface — dashboard-driven:
| Task | Command |
|---|---|
| Check config | arcforge learn status [--json] |
| Enable project learning | arcforge learn enable --project |
| Disable project learning | arcforge learn disable --project |
| Open review dashboard | arcforge learn dashboard [--port N] |
Once the daemon is running and learning is enabled, the dashboard is where all candidate review and lifecycle actions happen (Approve, Dismiss, Materialize, Activate, Deactivate, Promote, Evolve). The dashboard reads from ~/.arcforge/learning/candidates/queue.jsonl (the canonical Layer 5 queue produced by the LLM curator). See docs/guide/learning-dashboard.md for the full operational guide.
Legacy arcforge learn analyze|review|inbox|approve|reject|materialize|activate|inspect|drafts subcommands remain in the CLI but do not read or write the candidate queue — use the dashboard instead.
Use --json on any command when another tool or test needs machine-readable output.
arcforge learn status [--json]. Learning is disabled by default for both project and global scopes.arcforge learn enable --project for project-local learning. After enablement, the observer daemon assembles evidence batches, calls the LLM curator, and automatically queues pending candidates in the candidate queue.arcforge learn dashboard to open the browser control plane at http://localhost:3334. The dashboard is the canonical review surface.[Approve] or [Dismiss] action. Approval is required before any artifact is written.[Materialize] action. Draft artifacts are written to ~/.arcforge/learning/drafts/<candidate-id>/<materialization-id>/instincts/<name>.md — these are inactive review files; they are not loaded into Claude context.[Activate] action only after reviewing the draft. Activation copies the draft to ~/.arcforge/instincts/<project>/<candidate-id>.md (project scope) or ~/.arcforge/instincts/global/<candidate-id>.md (global scope), with supersede_with_backup if an active artifact already exists at that path. Once activated, the instinct is injected at SessionStart through that activation gate only — the top 5 by confidence (sort/cap, not a threshold), with an inject_activated_instincts kill-switch (default ON). Non-activated candidates are never injected.The full set of statuses a candidate moves through:
| Status | Meaning |
|---|---|
pending_review | Queued by LLM curator, awaiting human review |
needs_more_evidence | Flagged for more evidence before approval |
approved | Human-approved, ready to materialize |
materialized | Inactive draft artifact(s) written under ~/.arcforge/learning/drafts/<cid>/<mid>/, ready to activate |
activated | Draft promoted to active instinct file under ~/.arcforge/instincts/<scope>/<cid>.md |
deactivated | Previously activated, now deactivated |
dismissed | Rejected; no artifacts written |
superseded | Replaced by an evolved candidate |
The supported surface is the arcforge learn ... lifecycle above. Do not bypass candidate approval, inactive draft materialization, or explicit activation gates with ad-hoc scripts — combining related instincts into a higher-level candidate is the dashboard's Evolve action.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub gregoryho/arcforge --plugin arcforge