SkillsAdd

coleam00/archon

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 oth…

First seen Apr 11, 2026

Installation

$ npx skills add coleam00/archon --skill archon-dev
View on skills.sh ↗ GitHub repository ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Archon Manager Similar name
daffy0208/ai-dev-standards

Master Archon MCP for strategic project management, task tracking, and knowledge base operation…

122 installs

Also in this package

Other skills from coleam00/archon · top by installs.

npx skills add coleam00/archon
archon 307 playwright-cli 263 triage 255 docker-extend 254 rulecheck 253 test-release 252 release 251 validate-ui 246 agent-browser 246 save-task-list 245

Browse all from coleam00/archon

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 23.4K
License LICENSE
Default branch dev
Open issues 299
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,875 B
  • docs SUMMARY.md 1,546 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 247 installs

SKILL.md

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](cookbooks/research.md)
Strategic research, library eval, feasibility "investigate", "should we", "can we", "compare", "evaluate", "feasibility", "best way to", "best approach" [cookbooks/investigate.md](cookbooks/investigate.md)
Write product requirements "prd", "requirements", "spec", "product requirement" [cookbooks/prd.md](cookbooks/prd.md)
Create implementation plan "plan", "design", "architect", "write a plan" [cookbooks/plan.md](cookbooks/plan.md)
Execute an existing plan "implement", "execute", "build", "code this", path to .plan.md [cookbooks/implement.md](cookbooks/implement.md)
Review code or PR "review", "review PR", "code review", "review changes" [cookbooks/review.md](cookbooks/review.md)
Debug or root cause analysis "debug", "rca", "root cause", "why is", "broken", "failing" [cookbooks/debug.md](cookbooks/debug.md)
Commit changes "commit", "save changes", "stage" [cookbooks/commit.md](cookbooks/commit.md)
Create pull request "pr", "pull request", "create pr", "open pr" [cookbooks/pr.md](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](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.json scripts for validate, check, or verify
  • Test command: Check for test script in package.json
  • Conventions: Read CLAUDE.md for project-specific rules

Rules

  1. Evidence-based: Every claim about the codebase must reference file:line
  2. No speculation: If uncertain, investigate first
  3. Fail fast: Surface errors immediately, never swallow them
  4. Respect CLAUDE.md: Project conventions override cookbook defaults
  5. No AI attribution: Never add "Generated with Claude" or "Co-Authored-By: Claude" to commits or PRs