A command for bringing the RENATA product-development method into an existing codebase, often called a brownfield project. It reverse-engineers the code, documents its technical pattern and features, and builds a retrospective product plan with your confirmation at each stage.

Use it when an established repository wants to adopt RENATA. It is not intended for a new or empty project, or for extracting only the technical pattern.

It creates project documentation from what the software actually does instead of assuming the existing code matches old plans. Human confirmation prevents inferred details from becoming accepted facts.

adopt — Command for coding agents by AInsteinsBR: A command for bringing the RENATA product-development method into…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/ainsteinsbr/renata/adopt

Clone the repo

git clone --depth 1 https://github.com/AInsteinsBR/renata

Or install renata, the plugin that ships this one along with the rest of its 3 skills, 33 commands, 6 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ainsteinsbr/renata/adopt.svg)](https://agentmods.dev/commands/ainsteinsbr/renata/adopt)

Your own site

<a href="https://agentmods.dev/commands/ainsteinsbr/renata/adopt"><img src="https://agentmods.dev/badge/commands/ainsteinsbr/renata/adopt.svg" alt="Measured on agentmods" height="20"></a>

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,406 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00036	$0.02406
Opus 5	$0.00018	$0.01203
Sonnet 5	$0.00007	$0.00481
Haiku 4.5	$0.00004	$0.00241

Measured 3d ago against content hash c3e1a414262b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

adopt scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/adopt.md · 129 lines

How it starts

The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/renata:adopt — Adopt RENATA in an existing project (brownfield)

You are an architect + PM doing reverse engineering. You receive an existing codebase and adopt the RENATA method over it: technical pattern (via /renata:extract-pattern), technical context, feature inventory, retroactive PRD and selected as-built specs — stage by stage, confirming every item with the user.

Respond to the user and generate document content in the user's language (the language they are writing in).

The central rule is inherited from /renata:extract-pattern and governs every stage: the code is the truth, the human validates item by item. You report what the code does; the user decides what becomes documented.

When to use

A repo with real code that wants to adopt the method (brownfield). This is the single entry point — it orchestrates everything else.

DO NOT use for:

A new/empty project → /renata:init + Step 2 of GETTING-STARTED (/renata:prd).
Only the technical layer (ADRs + code-pattern doc) of a repo/starter → run /renata:extract-pattern directly.

The as-built provenance mark (do not violate)

Every artifact this command generates receives, right below the title:

> 🏗️ As-built — reverse-engineered from code by /renata:adopt on <YYYY-MM-DD>. Verify with /renata:status.

NEVER write the line > ✅ Verified by you on <date> — only the human does that, via /renata:status. Every artifact is born 🔄 (in progress) and awaits human verification.

Stage 0 — Pre-flight

Scaffold: check that CLAUDE.md, .claude/progress-map.yaml and docs/ exist. If not, execute the flow of ${CLAUDE_PLUGIN_ROOT}/commands/init.md first (it is safe on brownfield: it only copies the doc scaffold and asks before overwriting CLAUDE.md), then continue.
Git: run test -d .git. If there is no git, recommend git init NOW (the ADR-enforcement hook only activates with git) and offer to proceed anyway.
Code scopes: detect candidate code roots — frontend/, backend/, api/, src/, apps/*, packages/*, and dependency manifests (package.json, pyproject.toml, go.mod, Cargo.toml, Gemfile, pom.xml, composer.json). Show the list and confirm with the user which scopes to adopt.
Pre-existing artifacts: if docs/prd/, docs/decisions/ADR-*.md or docs/features/F*.md already have real content, switch to refine mode for those artifacts — never overwrite. Pre-existing ADRs are cleaned up via /renata:adr refine, not recreated.

Read the full file on GitHub · 129 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 129 lines · 36 tokens per session scan A c3e1a414262b

Subscribe to this mod's changes

adopt is a command published in the GitHub repository AInsteinsBR/renata (10 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 2,406 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning adr claude-code claude-plugin prd product-management

adopt

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/renata:adopt — Adopt RENATA in an existing project (brownfield)

When to use

The as-built provenance mark (do not violate)

Stage 0 — Pre-flight

What this file has done since we first saw it

Other commands, from other repositories

issue-review

issue-closeout

prd-review

prd-triage

prd-archive

issue-start