Direct implementation
Describe the goal and let the agent decide routine details. Skip repeated clarification, specification writing, and a separate start confirmation. Checks and independent review stay in place.
An IM-native coding agent
Describe the work. Choose direct implementation or clarify first. Dev Agent carries your request through implementation, checks, and review to a merge request — all from your chat.
For configured IM conversations and authorized repositories.
websiteStatic example · simple clarification shown below. All three modes are explained in the workflow section.
Choose a mode above to try a different path. These controls only change this fictional example.
Filtering, clear behavior, and keyboard access.
Code changes and repository conventions.
The implementation against the task’s requirements.
Example merge request
Add a search filtertask branch → main
Code changes, check results, and review notes.
Not automatically merged or deployed.
1 / 4 · Request
Fictional conversation · not a live session
Agent Skills · Convention over configuration
Copy a prompt into your agent, or install reusable guidance with Skills CLI. Either is enough to get started.
curl -fsSL https://dev-agent.io/.well-known/agent-skills/index.json
Behind the command · well-known discovery
{
"skills": [{
"name": "dev-agent-user-commands",
"url": "/.well-known/agent-skills/dev-agent-user-commands/SKILL.md"
}]
}
Originally developed by Anthropic, Agent Skills defines the SKILL.md format: metadata plus task instructions. This is the format of the guide, not the website discovery protocol.
Cloudflare’s Agent Skills Discovery RFC proposes the well-known index, skill URLs, and digests. This site follows draft v0.2.0. It is a community proposal, not an IETF standard or a guarantee of client support.
The IETF’s RFC 8615 defines the general /.well-known/ URI mechanism. It does not define SKILL.md or this Agent Skills index.
The workflow
One /new entry, three ways to work. Every task keeps its repository, target branch, requirements, and reviewable delivery together.
Describe the goal and let the agent decide routine details. Skip repeated clarification, specification writing, and a separate start confirmation. Checks and independent review stay in place.
Resolve the essential gaps together. Read the specification and test plan, confirm that version, then decide when to start.
Explore requirements, constraints, and trade-offs in more depth. Then confirm the specification and separately approve implementation.
Start with /new. Select an available repository and the branch your changes should target, then describe the outcome you need.
Direct implementation starts from your request without a specification. Simple and deep clarification prepare a specification and test plan for you to confirm, followed by a separate go-ahead to build.
Dev Agent works in a separate task workspace, runs checks, and independently reviews code quality and requirement fit. Results, unavailable checks, and unresolved findings are reported as they are.
Get a merge request against your selected branch. Inspect the changes, ask for refinements, and merge through your usual review process.
Built around the conversation
Development rarely ends with the first draft. Continue in plain language, with the task and its context still in place.
Ask for another change in the same conversation. Before a merge, refine the existing request. After a confirmed merge, new work can become a new merge request without starting the discussion over.
Check progress with /status, request a stop with /stop, and continue with /continue or a plain-language follow-up. Your mode, context, and work stay with the task; direct implementation stays spec-free.
Ask questions, search public information, and read web pages in everyday chat. /new starts development; /end closes it. A thank-you or a question after delivery does not automatically trigger more code changes.
Ask for an avatar, icon, or simple diagram in everyday chat when image delivery is enabled. These are programmatically drawn visuals, not photorealistic image generation. Adding images to a repository requires a separate confirmation.
Clear boundaries
Choose how much to clarify. Repository access, image publication, and the final merge keep their own boundaries in every mode.
The user guide
Send /help in your Dev Agent conversation, or use /new to begin a task. Your chat needs access to a configured repository; this website is the public product and command guide.
/new/status/stop/continue/end/help