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.

1 / 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
dowe agent init
dowe agent update
Command
Purpose
Behavior

No data

There are no records to display

2 / 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. The skills keep frontend modules in views, backend modules and migrations in server, and only project wiring at the root.

dowe
AGENTS.md
CLAUDE.md
.agents/
  manifest.json
  harnesses/tdd.md
  plans/
  skills/
    dowe-core/
    dowe-domain-modeling/
    dowe-views/
    dowe-server/
    dowe-theme/
Step
What the agent does

No data

There are no records to display

3 / REFERENCE-DRIVEN UI

Treat the image as a visual contract

When a user asks for an exact reconstruction, dowe-views inventories the complete shell and every visible page band before authoring source.

dowe
python3 .agents/skills/dowe-views/scripts/visual_qa.py self-test

4 / AGENT-READY FROM INIT

Start with a designed system

Choose CRUD or blank first. CRUD continues directly to optional English and Spanish i18n, while the Database provider stays in server configuration and both starters include the same project Agent Harness and five public authoring skills, including domain modeling blueprints for business systems.

Starter
Shape
Details

No data

There are no records to display

5 / 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.

Capability
Responsibility

No data

There are no records to display

6 / 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.

dowe
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