archcore-ai/archcore

**The agent stops guessing and starts following the system.**
A coding agent can write the code. It does not know your project: what the feature must do, where the code belongs, which decisions and rules already apply. So it guesses, and you explain the same things again in the next session.
Archcore keeps specs, architecture, decisions, rules, and plans in Git, and makes the right project context available to AI coding agents as they work. It helps your coding agent make changes that fit your repo's architecture, rules, and past decisions.
- /archcore:plan before you build. The agent implements from a spec, examples, and tasks, sized to the change.
- /archcore:document as you go. One sentence from you becomes a finished, linked document.
- /archcore:review before merge. Archcore compares the branch with the documents and names the side that is wrong.
Install
On macOS, Linux, or WSL:
On Windows (PowerShell 5.1+):
Then, in your project:
The installer adds the CLI and plugins for Claude Code, Codex CLI, and GitHub Copilot CLI when it finds them. archcore init connects the agents you choose to this project. It also supports Gemini CLI, OpenCode, Roo Code, and Cline. Cursor needs one extra setup step.
Already have a CLAUDE.md, AGENTS.md, or rule files? Say /archcore:init import in your agent to turn them into project documents.
The documents stay in your repo, in .archcore/. Details: privacy.
Plan: the agent builds from documents, not from a chat message
/archcore:plan reads the repo and the existing documents first. Then it asks you only what it cannot find there. Your answers become documents in .archcore/: a spec with requirements, and a plan with tasks mapped to files. A user-facing change also gets examples in Given/When/Then form. Larger work can add a PRD, research, or a formal requirements chain.
Archcore weighs the change, computes the route, and reports its size from S to XL. You never choose a template or a size.
| The change | What plan prepares |
| ----------------------------- | -------------------------------------------------------------- |
| A small fix | No documents |
| A settled choice | A decision record |
| A change to existing behavior | A check of the covering spec: update the spec, or fix the code |
| One new capability | A spec and a plan |
| Several capabilities | A PRD, one spec per capability, and a plan |
Risk raises the size. A security requirement adds a formal requirements chain. A data migration adds a migration runbook.
The agent then implements from the spec, the examples, and the tasks. The open questions are settled before the code, not after it.
Document: you say it once, Archcore writes the document
/archcore:document records what is true now: a decision, a team standard, how a module works, or a how-to. You do not choose a format. Archcore selects the document type, reads the code and the existing documents, and checks that the document does not exist yet. It asks you only what it cannot find. It links the new document to the related ones. A decision can also produce the rule and the guide that follow from it.