Dowe

DEVELOPMENT / EXTERNAL AGENTS

Dowe Agent

Dowe prepares a project for Codex, Claude Code, OpenCode, or another coding agent without choosing, hosting, or charging for the model.

Open Server docs

ONE PROJECT SETUP

Install the complete agent

Initialization writes provider-neutral instructions, the TDD harness, plans, and the public Dowe authoring skills included in the installed Dowe version.

dowe agent init
dowe agent update

INIT

Preserve project work

init creates missing agent files and preserves existing files byte for byte. It does not write generated .dowe artifacts.

UPDATE

Refresh managed knowledge

update rebuilds Dowe-managed instructions and skills, removes obsolete managed resources, and preserves project-owned skills.

VERSIONED AUTHORING KNOWLEDGE

Skills are installed automatically

Dowe installs authoring skills locally so an external agent can use the syntax and target boundaries that match the current compiler version.

AGENTS.md
CLAUDE.md
.agents/
  manifest.json
  harnesses/tdd.md
  plans/
  skills/
    dowe-core/
    dowe-views/
    dowe-server/
    dowe-theme/

DISCOVERY

Read frontmatter first

The agent discovers skill metadata before loading a focused SKILL.md.

DETAIL

Use focused references

dowe-views separates route and state guidance from a complete catalog covering every built-in component and its context-only child entries.

OWNERSHIP

Keep authority separate

Dowe-managed dowe-* skills are separate from private compiler-development skills and project-owned guidance.

AUTOMATIC WORKFLOW

The agent owns the workflow

AGENTS.md gives every external agent one short authoring contract. CLAUDE.md points Claude-compatible tools to the same rules instead of creating a second workflow.

Harness and CodeGraph

Behavior changes use the Agent Harness. CodeGraph remains available for ownership, modularity, dependencies, and duplication checks.

MCP integration

Providers can start the local read-only MCP bridge with dowe agent mcp instead of exposing credentials or opening a network port.

SPEC-DRIVEN DEVELOPMENT

Harnesses enforce process, not a test language

The TDD harness requires a spec, contracts, a test plan, validation, and documentation before a behavior change closes. Native literal tests can live in any project folder and run through dowe test.

Spec -> Contract -> Tests -> Implementation -> Validation -> Documentation

The coding agent writes and runs the concrete project tests appropriate to the selected spec. For literal contracts it can use test and assert declarations anywhere in the project, then records validation evidence under .dowe only when the harness requires it.

Read native test docs