recursive-mode.dev valid
recursive-mode
Powerful recursive workflow for agentic engineering (and fine-tuning)
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:00:01.654Z. Cached copy · Source on recursive-mode.dev
# recursive-mode
> Powerful recursive workflow for agentic engineering (and fine-tuning)
## Docs
- [Introduction to recursive-mode](https://recursive-mode.dev/introduction.md): What recursive-mode is, who it's for, and the problems it solves.
- [Quick Start](https://recursive-mode.dev/quickstart.md): Get a repository running with recursive-mode in under 5 minutes.
- [Installation](https://recursive-mode.dev/installation.md): All installation options for Recursive Mode: skills CLI, Python, PowerShell, and Bash.
- [Workflow overview](https://recursive-mode.dev/concepts/workflow-overview.md): The big picture of how recursive-mode works — runs, phases, artifacts, and feedback loops.
- [Phases](https://recursive-mode.dev/concepts/phases.md): Detailed reference for every phase in a Recursive Mode run — purpose, artifact file, and audit requirements.
- [Artifacts](https://recursive-mode.dev/concepts/artifacts.md): What artifact files are, how the draft-to-lock lifecycle works, and how to read them.
- [Memory](https://recursive-mode.dev/concepts/memory.md): The durable memory plane — what it stores, how it's organized, and when to read and update it.
- [Worktree](https://recursive-mode.dev/subskills/recursive-worktree.md): Isolate every recursive-mode run in a dedicated git worktree before implementation begins.
- [TDD](https://recursive-mode.dev/subskills/recursive-tdd.md): Enforce strict RED-GREEN-REFACTOR discipline in every recursive-mode implementation phase.
- [Debugging](https://recursive-mode.dev/subskills/recursive-debugging.md): Insert Phase 1.5 to find root cause before planning any fix.
- [Review Bundle](https://recursive-mode.dev/subskills/recursive-review-bundle.md): Package a canonical context bundle before delegating a Phase 3.5 review or audit.
- [Subagent](https://recursive-mode.dev/subskills/recursive-subagent.md): Decide whether and how to delegate phases to subagents, and enforce the handoff contract when you do.
- [Scripts](https://recursive-mode.dev/scripts/overview.md): Reference overview of all scripts included with recursive-mode — cross-platform utilities for bootstrapping, status checks, linting, locking, and more.
- [Install Script](https://recursive-mode.dev/scripts/install.md): Reference for install-recursive-mode — the bootstrapper that creates the /.recursive/ control-plane scaffold in your repository.
- [Status & Lint](https://recursive-mode.dev/scripts/status-and-lint.md): Reference for recursive-status and lint-recursive-run — tools for checking run status, lock-chain validity, and artifact structure.
- [Lock & Verify](https://recursive-mode.dev/scripts/lock-and-verify.md): Reference for recursive-lock and verify-locks — tools for locking phase artifacts and verifying lock integrity.
- [Starting a Run](https://recursive-mode.dev/guides/starting-a-run.md): How to start and resume Recursive Mode runs.
- [Auditing Phases](https://recursive-mode.dev/guides/auditing-phases.md): How the audit loop works and what you need
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| commandcode.ai | Command Code | documentation AI and machine learning AI agents and MCP +1 | US | 58 | ✓ | ||
| claudecodeguide.dev | Claude Code Guide | documentation AI and machine learning Developer tools +1 | US | 45 | ✓ | ✓ | |
| deepworkplan.com | Deep Work Plan | interface AI agents and MCP Developer tools +1 | — | 46 | ✓ | ✓ | |
| stagewise.io | stagewise Docs | documentation AI and machine learning AI agents and MCP +2 | — | 45 | ✓ | ✓ | |
| warp.dev | Warp | documentation Developer tools AI agents and MCP | US | 66 | ✓ | ✓ | |
| emdash.com | Emdash | documentation AI agents and MCP Developer tools | US | 52 | ✓ | ||
| rwx.com | RWX | documentation Developer tools DevOps and observability | — | 55 | ✓ | ||
| decisional.com | Decisional Documentation | documentation | US | 46 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=recursive-mode.dev · GET /v1/domain/recursive-mode.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage recursive-mode.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for recursive-mode.dev:
1. POST https://agentwebmap.com/v1/sites/recursive-mode.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://recursive-mode.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/recursive-mode.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/recursive-mode.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.