Use a Team's Harness

Team harnesses are consumed as cards and project overlays. Start by initializing the project, adding the team's card, and previewing the generated downstream state:

drwn init
drwn apply @team/backend@^1.0.0
drwn add @team/backend@^1.0.0
drwn write --dry-run
drwn write

drwn apply resolves the card and updates the current project. drwn write materializes the resolved skills and MCP config into .claude, .codex, and .cursor for that project.

Keep the project current:

drwn card status --explain
drwn status --why
drwn card outdated
drwn card update
drwn update
drwn write --dry-run

Use drwn card pin @team/[email protected] when a project needs an exact card version. Use drwn card remove @team/backend when the project should stop consuming the team harness.

Cloned Projects

If the project already has .agents/drwn/card.lock, prefer the install flow:

drwn install --no-apply --json
drwn write --dry-run
drwn install --json

The install-harness-project skill wraps this sequence for agents. It keeps locked-card installation separate from new-project initialization and card-set mutation.

Extensions remain explicit project choices:

drwn extensions add parallel
drwn extensions add markitdown
drwn extensions add beads --include-skill

For the workflow skills that operate these commands, see Use Darwinian Harness Skills.