archon-dev

Route development tasks to CLAUDE cookbooks and organize artifacts under .claude/archon.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-dev-zillafan80-maxzilla
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archon-dev
Source: https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI/tree/main/payload/claw-code/.claw/skills/archon-archon-dev
Command: npx skills add https://github.com/zillafan80-Maxzilla/claw-code-ubuntu-desktopUI --skill archon-dev-zillafan80-maxzilla

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Archon development tasks require a consistent, artifact-driven workflow that routes user intent to targeted CLAUDE cookbooks and centralizes artifacts for traceability.

Core Features & Use Cases

  • Routing to cookbooks: research, investigate, prd, plan, implement, commit, pr, issue
  • Phase management: supports dependency-aware progression and artifact generation
  • Artifact organization: stores reports, plans, issues under .claude/archon and .claude/archon/reports/.claude/archon/plans

Quick Start

Ask Archon to run a cookbook by name, for example '/archon-dev plan' to begin planning.

Frequently Asked Questions about archon-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end development workflows from research to pull requests?

End-to-end development workflow automation routes user intent to targeted cookbooks for research, planning, implementation, and pull requests. It centralizes artifacts in structured directories to ensure traceability and reproducibility across the entire development lifecycle.

What is the best way to manage software engineering artifacts like PRDs and plans?

Software engineering artifact management stores reports, plans, and issues under dedicated directories like .claude/archon. This enforces consistent naming and validation gates to maintain dependency-aware progression and traceability throughout the project.

How do I structure a development process with evidence-based analysis and phase management?

Evidence-based analysis and phase management route user intent through dedicated cookbooks including investigate, prd, and plan. This enforces a disciplined process through validation gates and structured interaction with project conventions.

How do I start a planning phase for a new code feature using cookbook routing?

Planning phase automation begins by invoking the specific cookbook by name, such as '/archon-dev plan'. This routes intent to generate structured plans and artifacts, supporting dependency-aware progression for the implementation phase.

Can I generate and track GitHub issues and pull requests through an automated workflow?

Automated workflow routing supports dedicated issue and pr cookbooks to generate and track GitHub artifacts. It aggregates these artifacts under centralized directories to enforce traceability and reproducible development cycles.

When do I need a dependency-aware progression system for code review and implementation?

Dependency-aware progression is needed when moving from planning to implementation and code review. It manages phase dependencies and enforces validation gates, ensuring artifacts are generated and tracked consistently before committing changes.