DrZero Help

Use this skill when the user asks how to use @drzero, wants examples, or needs to see the available DrZero workflow modes after installing the plugin.

First Run

Initialize shared configuration in the current repo:

@drzero run drzero-config init for this repo

Verify setup:

@drzero drzero-config show
@drzero drzero-config validate
@drzero drzero-ping

Default init writes ./drzero.yml if missing and installs support scripts plus bundled agent templates under .codex/otc-awesome-llm. It does not activate specialist agents into .codex/agents, so @drzero remains the primary plugin mention. Advanced direct-agent activation uses dr0-* aliases.

Build Examples

Coordinated multi-agent implementation:

@drzero drzero-swarm "Build a simple React app with login, dashboard, and settings pages"

Default autonomous improvement loop:

@drzero drzero "Improve this repository using the default 3 iterations and 3 tasks per iteration"

Small direct task:

@drzero drzero-morty "Update the README with setup instructions"

Minimal CI-style fix:

@drzero drzero-pickle "Make the smallest change needed to pass CI"

Architecture decision before implementation:

@drzero drzero-council "Decide whether this should be implemented as a plugin skill or a support script"

Parallel implementation variants:

@drzero drzero-cronenberg "Try three caching approaches and compare the tradeoffs"

Cross-repo coordination:

@drzero drzero-portal-gun "Update authentication across all microservices"

Governed release-sensitive work:

@drzero drzero-citadel "Deploy payment processing changes with quality gates"

Peer-to-peer parallel cleanup:

@drzero drzero-unity "Fix all linting errors"

Workflow Modes

• drzero: default autonomous improvement.
• drzero-help: show setup guidance, workflow modes, and examples.
• drzero-ping: health check for config, scripts, and runtime.
• drzero-status: read current .codex/drzero-session.json status.
• drzero-config: initialize, show, validate, and edit shared YAML config.
• drzero-swarm: orchestrated multi-agent implementation.
• drzero-council: structured debate for architecture/design decisions.
• drzero-citadel: centralized governance with explicit quality gates.
• drzero-unity: peer-to-peer parallel work without one central owner.
• drzero-morty: simplified execution for small concrete tasks.
• drzero-cronenberg: parallel variants for comparison.
• drzero-portal-gun: cross-repo coordination.
• drzero-pickle: minimal viable changes under strict constraints.

Recommendation

Use drzero-swarm for substantial build work, drzero-morty for small scoped tasks, drzero-pickle for CI repair, and drzero-council when the design is unclear enough that implementation should wait.