arc-knows
v1.18.3
Published
Arc knows — A meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode and Gemini.
Maintainers
Readme
Arc knows
Build software with AI — reliably.
Claude Code is powerful. Arc knows makes it trustworthy.
What It Does
Arc knows fixes the main problem with AI coding: context rot. As Claude fills its context window, quality degrades and it starts making mistakes.
Arc knows solves this by:
- Breaking work into atomic tasks (each fits in a fresh context window)
- Using subagents for heavy lifting (keeps your session fast)
- Making atomic git commits (every task, reversible history)
- Verifying results (did it actually build what we said?)
You describe what you want. Arc knows handles the context engineering. Claude Code builds it.
Quick Start
Install
npx arc-knows@latestPrompts you to choose:
- Runtime — Claude Code, OpenCode, Gemini, or all
- Location — Global (all projects) or local (current project)
Recommended: Run Claude Code with --dangerously-skip-permissions to avoid constant approval prompts.
Verify
/arc:helpHow It Works
One simple loop: discuss → plan → execute → verify
┌─────────────────────────────────────────────────────────────┐
│ 1. INIT PROJECT │
│ /arc:new-project │
│ │
│ Answer questions → Extract requirements → Create roadmap │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 2. FOR EACH PHASE │
│ │
│ ┌──────────────────┐ ┌──────────────────┐ ┌─────────────┐ │
│ │ /arc:discuss- │ │ /arc:plan-phase │ │ /arc:execute-│ │
│ │ phase │ │ │ │ phase │ │
│ │ │ │ │ │ │ │
│ │ Shape how │ │ Research + │ │ Execute all │ │
│ │ to build it │ │ create plans │ │ plans in │ │
│ └──────────────────┘ └──────────────────┘ │ parallel │ │
│ │ └─────────────┘ │
│ │ ↓ │
│ │ ┌─────────────┐ │
│ │ │/arc:verify- │ │
│ │ │ work │ │
│ │ │ │ │
│ │ │ Test that │ │
│ │ │ it works │ │
│ │ └─────────────┘ │
│ ┌──────────────────┐ │ ↓ │
│ │ /arc:complete- │◄───────────────────┴─── repeat ────┘
│ │ milestone │
│ │ │
│ │ Archive & tag │
│ │ release │
│ └──────────────────┘
└─────────────────────────────────────────────────────────────┘Step 1: Initialize Project
/arc:new-projectWhat happens:
- Questions — Asks until it understands your idea
- Research — Spawns parallel agents to investigate the domain
- Requirements — Extracts what's v1, v2, and out of scope
- Roadmap — Creates phases mapped to requirements
Creates: PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md
Step 2: Discuss Phase (Optional but Recommended)
/arc:discuss-phase 1Why this matters: A roadmap phase is just a sentence. That's not enough to build what you imagine.
This step captures your preferences:
- Visual features → Layout, interactions, animations
- APIs/CLIs → Response format, flags, errors
- Content systems → Structure, tone, depth
The deeper you go here, the more it builds your vision instead of reasonable defaults.
Creates: {phase}-CONTEXT.md
Step 3: Plan Phase
/arc:plan-phase 1What happens:
- Research — Investigates how to implement (guided by your CONTEXT.md)
- Plan — Creates 2-3 atomic task plans
- Verify — Checks plans against requirements
Each plan is small enough to execute in a fresh context window. No quality degradation.
Creates: {phase}-RESEARCH.md, {phase}-{N}-PLAN.md
Step 4: Execute Phase
/arc:execute-phase 1What happens:
- Runs plans in waves — Parallel where possible
- Fresh context per plan — 200k tokens for implementation only
- Commits per task — Every task gets its own commit
- Verifies — Checks code delivers what was promised
Walk away. Come back to completed work with clean git history.
Creates: {phase}-{N}-SUMMARY.md
Step 5: Verify Work
/arc:verify-work 1Does it actually work? This is where you confirm.
- Extracts testable outcomes — What you should be able to do now
- Walks through testing — "Can you log in?" Yes/no, or describe what's wrong
- Diagnoses failures — Spawns debug agents to find root causes
- Creates fix plans — Ready for re-execution
If everything passes → next phase. If something's broken → re-execute with fix plans.
Creates: {phase}-UAT.md, fix plans if issues found
Step 6: Complete Milestone
When all phases are done:
/arc:complete-milestone
/arc:new-milestone # Start next versionEach milestone is a clean cycle: define → build → ship.
Simplified Commands
The Essentials
| Command | What it does |
|---------|--------------|
| /arc:new-project | Start new project (questions → roadmap) |
| /arc:discuss-phase <N> | Shape implementation decisions |
| /arc:plan-phase <N> | Research + create task plans |
| /arc:execute-phase <N> | Execute all plans, commit per task |
| /arc:verify-work <N> | Test that it actually works |
| /arc:complete-milestone | Archive milestone, tag release |
| /arc:new-milestone | Start next version |
Brownfield Projects
Already have code? Map it first:
/arc:map-codebase # Analyze existing codebase
/arc:new-project # Then initialize as usualQuick Mode (Small Tasks)
/arc:quickFor bug fixes, small features, config changes. Same quality, faster path.
Navigation
| Command | What it does |
|---------|--------------|
| /arc:progress | Where am I? What's next? |
| /arc:help | Show all commands |
Why It Works
Fresh Context Every Time
Each plan executes in a fresh 200k token context. No accumulated garbage, no "I'll be more concise now."
Atomic Git Commits
abc123f feat(08-02): create login endpoint
def456g feat(08-02): add password hashing
hij789k feat(08-02): implement email confirmationEach task independently revertible. Git bisect finds exact failing commit.
Multi-Agent Architecture
Your session stays fast (30-40% context). Heavy work happens in subagents:
- 4 parallel researchers investigate domain
- Planner creates and refines plans
- Executors build in parallel
- Debuggers diagnose failures
You orchestrate. Agents execute.
Configuration
Project settings in .planning/config.json. Configure during /arc:new-project or update with /arc:settings.
Model Profiles
| Profile | Planning | Execution | Verification |
|---------|----------|-----------|--------------|
| quality | Opus | Opus | Sonnet |
| balanced (default) | Opus | Sonnet | Sonnet |
| budget | Sonnet | Sonnet | Haiku |
Switch: /arc:set-profile budget
Workflow Toggles
| Setting | Default | What it does |
|---------|---------|--------------|
| workflow.research | true | Research before planning |
| workflow.plan_check | true | Verify plans before execution |
| workflow.verifier | true | Verify delivery after execution |
Auto Mode (Hands-Off)
Want zero interaction? Use the simplified commands:
/a:init # Initialize project
/a:plan # Discuss + plan all phases
/a:go 1 # Execute + verify phase 1
/a:go 2 # Execute + verify phase 2
...
/a:auto # Execute ALL remaining phases automatically
# or simply:
/a:continue # Continue where you left off (auto-detects next action)/a:auto runs the full pipeline: discuss → plan → execute → verify → next phase
Continues until all phases complete or error detected. Checkpoint-based resumption across sessions.
Security
Protect sensitive files by adding to Claude Code's deny list:
{
"permissions": {
"deny": [
"Read(.env)",
"Read(.env.*)",
"Read(**/secrets/*)",
"Read(**/*credential*)",
"Read(**/*.pem)",
"Read(**/*.key)"
]
}
}This prevents Claude from reading these files entirely.
Update & Uninstall
# Update
npx arc-knows@latest
# Uninstall
npx arc-knows --claude --global --uninstallClaude Code is powerful. Arc knows makes it reliable.
