Features
The essentials are on the home page. Here is the rest, in detail: how agents learn, what Product and Strategy do, and how Alfrig fits your ecosystem.
Agents
Hire agents, pick their department and role, and design how each one looks. Change anything later; it shows up in the office right away.
Skin, hair, beard, glasses, headphones, badge and clothes. Or roll the dice.
Engineering or Product; developer, PM, PO or designer.
Chat with the agent in charge of a task, at any stage. What you agree on feeds the work.
Learning
When a task is done, the agent goes to the reflection room and saves what it learned about the project. The next task already knows.
Short notes that feed the context of the next tasks. Review, write and delete whatever you want.
The project’s guide for agents is written when missing and updated by PR when a new lesson shows up.
Skills per department and step apply house rules, with an automatic check of the result.
Installed dependencies are cached between tasks.
Project lessons
src/ module with an English name; export the name and alias from src/index.js, test in test/ and document in the README.node:test and node:assert/strict; run node --test test/file.test.js for a single file.npm test on Node 22 for every PR: new code must pass on that version.TypeError with a lowercase message; out-of-range values throw RangeError.Real lessons, written by the agents on a test project.
Departments
From task to merge
SteveDeveloper
TonyDeveloperProject selection, investigation and spec, build, test check, PR, review, CI and merge. Conflicts, QA fix requests and retries stay inside the flow.
From idea to delivery
DianaPM
BrucePO
NatashaDesignerA broad request becomes an initiative: the PM analyzes and prioritizes, the PO documents and splits it into tasks, the designer draws the screens on a design board, using your product’s design system.
OKRs that guide the agents
Alfrig runs a consultant-style conversation and builds objectives, key results and KPIs per year and quarter. Every initiative points to the result it moves.
Product
A broad request becomes an initiative. The PM analyzes and prioritizes, the PO documents, the designer designs, and tasks flow to Engineering as their dependencies are ready.
PM01AnalysisProblem, user value, who is affected, hypotheses and challenges: fragile assumptions and simpler alternatives. If needed, it sends an agent to read the code before concluding.PM02PrioritizationNow, next or later, with the rationale recorded and the key result the initiative moves.PO03DocumentationSpec and tasks for Engineering, with acceptance criteria and dependencies between them.Designer04DesignEach flow’s screens on a design board, for desktop and, for the main ones, mobile, using your product’s design system. Every screen is checked in a browser and gets handoff notes for Engineering.Engineering05Delivery in wavesTasks go in as their dependencies are ready. In Jira, ClickUp and Linear, they become subtasks of the original task.What comes with it
When confidence is low, the PM asks only what matters, with ready-made answers to click.
The designer surveys tokens, patterns and components from the code, so the screens look like the real product.
Brand rules (tone, what never to do, references) apply to every screen.
Learned preferences and decisions feed the next analyses: the PM knows the company better over time.
Duplicate a screen, point at an element and ask for the change. The variation shows up next to it, and you choose which one stays.
Prioritization, documentation and design run on their own or wait for a person to approve.
Strategy
Alfrig runs a consultant-style conversation and builds objectives, key results and KPIs. The PM prioritizes by that plan, and every initiative points to the result it moves.
No spreadsheet or pricey consultancy: the conversation becomes objectives, KRs and KPIs.
Key results are spread across the four quarters, with a focus and milestones.
Alfrig asks whoever runs the organization to update the numbers, in the app and by email.
Groups with several products get a strategy per unit, each with its own owner.
Hi, I’m Alfrig. Let’s build the 2027 plan. First: what is your company and who does it sell to?
A finance app for small businesses. We sell to owners who don’t have an in-house accountant.
And what must be different a year from now? Give me a number you track today.
Answer in your own wordsDraftin progress
Company
Finance app for small businesses with no in-house accountant.
Objectives and key results
O1 · Make onboarding self-service
Artifacts
Every document an agent delivers in a chat becomes an artifact: specs, PRDs, checklists, UI copy and HTML prototypes. Each one has versions, lives in a searchable gallery and is shared the way you choose.
Ask an agent for a spec, a checklist or a screen prototype: it comes out as an artifact.
Asked for a tweak? The agent delivers the whole artifact again with the same title, and it gets a new version.
Find by title or content, and filter between yours, the organization’s and the public ones.
Screen prototypes open in the browser and switch theme in one click, ready to show a client.
Screen prototype
Getting-started checklist
v3 · Natasha, designer
Share · Visibility
Built for your ecosystem
Import repositories straight from your GitHub, GitLab, Bitbucket or Azure DevOps account. An agent reads each project, writes its card and works out who depends on whom. That map is how agents pick where to change code and in which order to merge.
cadastro-api
Customer registration module that validates and normalizes payloads according to CONTRATO.md.
Node · node --test
formatos-br
Brazilian formats library (currency, CPF, CNPJ, ZIP, phone, dates), no dependencies. Formatting reference for the customer contract.
Node · node --test
The designer surveys the tokens, libraries, patterns and components of your frontend from the code, and opens each sample in a browser to check it renders. Every screen on the design board uses that system and your brand rules.
The Mac, Windows and Linux app opens Alfrig in its own window, with its own session, and updates itself. Product changes arrive right away, no reinstall.
FAQ
Yes. Beyond Engineering there is a Product department, with a PM, a PO and a designer as agents: a broad request becomes an initiative that is analyzed, prioritized, documented and designed before it reaches Engineering. And there is Strategy: Alfrig builds OKRs and KPIs through a chat, and the PM prioritizes by them.
When a task is done, the agent saves short lessons about the project that feed the context of the next tasks; you review, write and delete whatever you want. The project’s AGENTS.md is written when missing and updated by PR. Skills per department and step apply your company’s standards.
Yes. The designer surveys your frontend’s tokens, libraries, patterns and components from the code and checks each sample in a browser. The screens on the design board come out with that system and your brand rules, checked in a browser.
Each artifact can be private (only whoever chatted with the agent), organization-wide (anyone with a login) or public (anyone with the link, no account). Artifacts have versions and live in a searchable gallery.
When you import repositories, an agent reads each project, writes its card (what it does, stack and how to test it) and works out the dependencies between them, each with the snippet that proves it. That map is how agents pick where to change code and in which order to merge.
Yes, for Mac (Apple Silicon and Intel), Windows and Linux (AppImage). It opens Alfrig in its own window and updates itself in the background.
No card. 2 agents and 20 tasks a month.
