renata

_by  

🇧🇷 Versão em português

Record · Evidence · Name · Anchor · Test · Automate.

RENATA is a product method that ties persona → metric → ADR → code, shipped as a Claude Code plugin. It takes you from "I have an idea" to "code running in production" without losing the why behind each decision along the way.

Created by Eric Luque · AInsteins — https://www.ainsteins.com.br

Why RENATA exists

RENATA lives at an intersection nobody else occupies:

1. Product frameworks (Cagan, Torres, Lean) teach you to decide what to build — but stop at the code's border. The decision becomes a slide; the code is born orphaned from its why.
2. AI coding / vibe-coding tools generate code fast — but with no method: no persona, no metric, no recorded decision. Speed accruing interest.
3. RENATA is the bridge, with enforcement: the product method reaches inside the code — the ADR blocks the commit that violates it, the hook collects the gate, the hypothesis comes back to be falsified. The why survives the implementation.

Who it's for: a solo founder or a small PM+dev team building with AI, who wants product rigor without a product org.
What it is NOT: not project management (it doesn't replace your team's Scrum/kanban), not a code generator, not a product course — it's the method between your idea and your AI-written code.

Install

/plugin marketplace add AInsteinsBR/renata
/plugin install renata@ainsteins

Start a project

/renata:init "My Product"

Creates CLAUDE.md, docs/ and .claude/ in the project, and activates ADR-violation blocking on commit (if the project uses git). Then follow GETTING-STARTED.md.

What's in the plugin

• 29 commands — planning (/renata:discovery, /renata:prd, /renata:persona, /renata:user-journey, /renata:metrics, /renata:adr, /renata:landscape, /renata:feature-breakdown, /renata:feature-behavior, /renata:phase-roadmap, /renata:feature-spec), design (/renata:screens), validation (/renata:assumption-test, /renata:interview-kit, /renata:interview-debrief, /renata:hypothesis-check), development (/renata:plan-phase, /renata:execute, /renata:spike, /renata:phase-scope, /renata:triage, /renata:todo, /renata:refactor, /renata:retro, /renata:extract-pattern), post-production (/renata:bug-report, /renata:incident), navigation (/renata:status), and the scaffold (/renata:init).
• 6 agents — @architect, @code-reviewer, @qa-tester, @perf-auditor, @security-reviewer, @pattern-mapper.
• 3 auto-activating skills — respecting-adrs, keeping-docs-alive, detecting-scope-creep.
• Hooks — stage gate, in-session status, ADR-violation blocking on commit.

Note: the method content (commands, docs) is currently written in Portuguese; identifiers (commands, agents, files) are in English. Full English localization is on the roadmap. For the philosophy, see METHOD.md; for the step-by-step, GETTING-STARTED.md. For what's new in each version, see CHANGELOG.md.

Need help rolling it out?

RENATA is free and open (MIT). If you want to deploy the method at your company — setup, team training, custom code starters, or product/architecture consulting — AInsteins does that:

https://www.ainsteins.com.br

Why "RENATA"

Every method needs a name. This one carries hers.

RENATA is named after my wife, Renata. Behind every project I build there are hours that belonged to us — evenings, weekends, the small precious time a couple has. She gave that time up, again and again, so these ideas could exist. Not grudgingly: she's the one who pushes me to create, who believes the thing is worth building before anyone else does.

So the acronym is real — Record, Evidence, Name, Anchor, Test, Automate, the six verbs of the method — but the name is a thank-you. To the person who anchors everything else.

— Eric

License

MIT © Eric Luque / AInsteins. Use freely; keep the copyright notice.