archon-dev
The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for 42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR 123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming
- Installs
- 247
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/coleam00/archon --skill archon-dev- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads archon-dev automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
archon-dev
Development workflow — research, plan, build, review, ship.
Current State
- Branch: !
git branch --show-current 2>/dev/null || echo "not in git repo" - Artifacts: !
ls .claude/archon/ 2>/dev/null || echo "none yet" - Active plans: !
ls .claude/archon/plans/*.plan.md 2>/dev/null | head -5 || echo "none"
Routing
Read $ARGUMENTS and determine which cookbook to load.
If the user explicitly names a cookbook (e.g., "plan", "implement"), use that. Otherwise, match intent from keywords:
| Intent | Keywords | Cookbook |
|---|---|---|
| Codebase questions, document what exists | "research", "how does", "what is", "where is", "trace", "find" | cookbooks/research.md |
| Strategic research, library eval, feasibility | "investigate", "should we", "can we", "compare", "evaluate", "feasibility", "best way to", "best approach" | cookbooks/investigate.md |
| Write product requirements | "prd", "requirements", "spec", "product requirement" | cookbooks/prd.md |
| Create implementation plan | "plan", "design", "architect", "write a plan" | cookbooks/plan.md |
| Execute an existing plan | "implement", "execute", "build", "code this", path to .plan.md | cookbooks/implement.md |
| Review code or PR | "review", "review PR", "code review", "review changes" | cookbooks/review.md |
| Debug or root cause analysis | "debug", "rca", "root cause", "why is", "broken", "failing" | cookbooks/debug.md |
| Commit changes | "commit", "save changes", "stage" | cookbooks/commit.md |
| Create pull request | "pr", "pull request", "create pr", "open pr" | cookbooks/pr.md |
| Report to GitHub | "issue", "report to gh", "log in github", "file a bug", "feature request", "create issue", "gh issue" | cookbooks/issue.md |
If ambiguous: Ask the user which cookbook to use.
After routing: Read the matched cookbook file and follow its instructions exactly.
Workflow Chains
Cookbooks feed into each other. After completing one, suggest the next:
research ──► investigate ──► prd ──► plan ──► implement ──► commit ──► pr
▲ │
debug ───────────┘ review ◄──────┘
│
▼
issue ──► plan (if feature) or debug (if bug)
Artifact Directory
All artifacts go to .claude/archon/. Create subdirectories as needed on first use.
.claude/archon/
├── prds/ # Product requirement documents
├── plans/ # Implementation plans
│ └── completed/ # Archived after implementation
├── reports/ # Implementation reports
├── issues/ # GitHub issue investigations
│ └── completed/
├── reviews/ # PR review reports
├── debug/ # Root cause analysis
└── research/ # Research findings
Project Detection
Do NOT hardcode project-specific commands. Detect dynamically:
- Package manager: Check for
bun.lockb→ bun,pnpm-lock.yaml→ pnpm,yarn.lock→ yarn, else npm - Validation command: Check
package.jsonscripts forvalidate,check, orverify - Test command: Check for
testscript inpackage.json - Conventions: Read CLAUDE.md for project-specific rules
Rules
- Evidence-based: Every claim about the codebase must reference
file:line - No speculation: If uncertain, investigate first
- Fail fast: Surface errors immediately, never swallow them
- Respect CLAUDE.md: Project conventions override cookbook defaults
- No AI attribution: Never add "Generated with Claude" or "Co-Authored-By: Claude" to commits or PRs
FAQ
What does the archon-dev skill do?
The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for 42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR 123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming
How do I install archon-dev?
Run npx skills add https://github.com/coleam00/archon --skill archon-dev in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/archon-dev/ (personal) or .claude/skills/archon-dev/ (project).
Which AI agents can use archon-dev?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is archon-dev safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains archon-dev?
It is published by coleam00 in coleam00/archon. It has 247 recorded installs.
More from coleam00/archon
playwright-cli
coleam00/archon
Automate browser interactions, test web pages and work with Playwright tests.
docker-extend
coleam00/archon
Open the skill to read its SKILL.md instructions.
test-release
coleam00/archon
Open the skill to read its SKILL.md instructions.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.