Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By Done-0
Enforce structured workflows for complex Claude Code tasks, requiring explicit planning, runbook-driven execution, validation, observability, review, maintenance, and knowledge capture before closure. Manage local AI knowledge base for engineering insights with vector search and embeddings.
npx claudepluginhub done-0/openarche --plugin openarcheView or update OpenArche configuration
Rebuild the knowledge index after changing embedding settings
Save a durable engineering insight into OpenArche knowledge
Search OpenArche knowledge
Sweep drift, low-value patterns, and maintenance follow-up
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Copilot — a framework of specialized agents, skills, commands, and hooks that give Claude persistent memory, expert methodology, and task tracking. Agents cover architecture (ta), engineering (me), QA (qa), design (sd/design), DevOps (do), documentation (doc), and knowledge onboarding (kc).
Cross-session Save/Load, and Ultrawork inspired by oh-my-opencode with Ralph Loops
A local-first SDLC workflow harness — structured, durable state for coding agents, with convergence gates, agent teams, and full audit trail.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Real-time statusline HUD for Claude Code - context health, tool activity, agent tracking, and todo progress
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Multi-AI collaboration plugin - orchestrates Codex, Gemini, and Claude as a team
OpenArche is a harness-first Claude Code plugin for non-trivial engineering work. It keeps complex tasks from closing before planning, validation, review, and closeout are explicit.
Task grading: decides whether a task stays light or enters harness controlEmbedding-based routing: uses the configured embedding backend to separate plain questions from execution work without language-specific keyword listsPersistent sessions: materializes .openarche/sessions/<task-id>/state.json only when execution work actually startsStage gates: keeps validation, review, and maintenance open until they are actually closedContext injection: adds current task state, gate reasons, and relevant local knowledgeKnowledge recall: retrieves repository-local knowledge first, then global knowledge, through embeddings and link expansionBackground closeout: captures reusable knowledge after the task stops/plugin marketplace add Done-0/openarche
/plugin install openarche
/reload-plugin
/openarche:setup
If you use local embeddings, the first successful run may need network access to download the model files. If you prefer API-backed embeddings, switch to remote in /openarche:config.
.openarche/sessions/<task-id>/state.json is materialized only for explicit execution work or, by default, after actual write activity starts.| Command | Description |
|---|---|
/openarche:setup | Prepare OpenArche for automatic task interception, harness sessions, and optional knowledge import |
/openarche:config | View or update grouped capability configuration |
/openarche:plan | Produce an execution plan with objective, acceptance criteria, and explicit task coverage |
/openarche:run | Turn a plan into an execution checklist |
/openarche:validate | Define browser and task validation expectations |
/openarche:observe | Define investigation queries and targets |
/openarche:review | Drive self-review, local agent review, cloud agent review, and repair loops |
/openarche:maintain | Run maintenance and drift-reduction workflows |
/openarche:knowledge-search | Search reusable engineering knowledge |
/openarche:knowledge-save | Persist reusable engineering knowledge explicitly |
/openarche:knowledge-reindex | Rebuild the knowledge vector index after embedding model changes |
Config file:
<home>/.claude/openarche/config.json
knowledge.embedding.provider: local or remoteorchestration: auto-injection, deferred materialization, and explicit command policyknowledge.embedding.localModel: used only when the provider is localknowledge.embedding.remoteModel, knowledge.embedding.remoteApiKey, knowledge.embedding.remoteBaseUrl: used only when the provider is remoteknowledge.retrieval: recall threshold, recall fanout, and injection budgetknowledge.extraction: extraction model and capture concurrencyexecution: isolation strategy and base ref
OpenArche records the isolation plan by default. It does not automatically create git worktrees or switch branches in your repository.validation.browser: required browser evidenceobservability: logs, metrics, and traces requirementsreview: self-review, local agent review, cloud agent review, repair loopsmaintenance: quality and drift cleanupIf the embedding provider changes, run:
/openarche:knowledge-reindex
Global OpenArche state lives under:
<home>/.claude/openarche/
├── config.json
├── state.json
├── capture-log.json
├── decision-log.jsonl
├── prototype-cache.json
├── index.json
└── knowledge/
Repository-scoped runtime state lives under:
<repo>/.openarche/
├── sessions/
│ └── <task-id>/
│ ├── state.json
│ └── evidence/ # created only after evidence is actually recorded
└── knowledge/
├── index.json
└── <entry-id>.md