Tutorials
Short step-by-step tutorials for people who work with featureloom through Claude Code, Codex, Cursor or another MCP client.
Start with step 1: you set up your organization and try featureloom free for 30 days.
7 steps
Start here
Set up your organization and connect your console, then go step by step: a plan lands on the board, your agent realizes it, and you accept the work. Each step is one short tutorial.
- Step 1 of 7
Set up your organization or join one · one of two
Set up your organization
You can set up a featureloom organization on your own, for yourself or for your company, and try it free for 30 days.
Join an organization from an invitation
Your invitation link creates your account and takes you straight into your team’s organization.
- Step 2 of 7
Connect your console · one of three
Connect Claude Code with one command
One command from the app adds featureloom to Claude Code. From then on, your agent takes plans from your board.
Connect Codex with one command
One command from the app adds featureloom to Codex. From then on, your agent takes plans from your board.
Connect the Cursor editor with one button
A button in the app adds featureloom to the Cursor editor, and you confirm the connection by signing in through the browser. From then on, your agent takes plans from your board.
- Step 3 of 7
Your agent writes a plan from a console conversation
Tell your agent in the console what you need, and it creates the plan on your board.
- Step 4 of 7
A plan in the app from your meeting transcript
You paste a meeting transcript made with your own tool, and a cloud language model writes the plan.
- Step 5 of 7
Your agent realizes a plan from the board
A plan from the board goes to your agent with one command, and you follow its work on the board and in the plan document.
- Step 6 of 7
Acceptance: Do not accept and the agent’s rework
You do not have to accept your agent’s work: write a reason and give it the plan again, and it fixes the work and reports it again.
- Step 7 of 7
Invite people and grant rights
Invite your team from the People screen: everyone gets their own account, and their rights say what their consoles may do.
7 steps
Projects and plans on the board
From a new project to an ordered board: a plan you write yourself, a plan from text or a document, plans from a meeting, the order to take them in, the board’s settings and the plans set aside and archived.
- Step 1 of 7
Create a project and its board
A new project gets a board of its own, its own plan keys and its own settings.
- Step 2 of 7
Write a plan yourself and keep its document
A plan is one markdown document: you write it yourself, and featureloom keeps its versions as you save. Such plans are part of your subscription, within its content limit: from the balance you pay only for plans the model writes from meeting transcripts and documents.
- Step 3 of 7
A plan from pasted text or a PDF or Word document
Turn text, a PDF or a Word document into a plan built on your project’s template, with no agent and no writing from scratch.
- Step 4 of 7
From a meeting to epics and plans
You give your agent a meeting transcript saved as a file, and it creates epics, writes plans from your project’s template and links them by dependencies.
- Step 5 of 7
Epics and Order: what to take first
An epic groups plans, a dependency says what waits on what, and the Order screen shows which plan to start with.
- Step 6 of 7
Columns, types and the plan template
Three settings decide what your board’s columns mean, what you call the kinds of work and what a plan generated from material looks like.
- Step 7 of 7
Off the board: Set aside and Archive
A plan you don’t want to see on the board doesn’t have to go: you move a realized one to the archive and set aside one nobody has started yet.
8 steps
Agents and consoles
From a console connected with no secret to work done your team’s way: signing in through the browser, in Cursor CLI too, role prompts your agent gets with one command, your agent’s questions you answer in the plan, Cursor with a secret, your consoles in order, and an automation with a key for jobs no person runs.
- Step 1 of 8
Connect a console by signing in through the browser, with no secret
On a computer with a browser, you connect Claude Code with a command that holds no secret: you confirm the connection by signing in through the browser. On a server with no browser, use the ordinary connect command with a secret.
- Step 2 of 8
Connect Cursor CLI by signing in through the browser
You connect Cursor CLI with an entry with no secret in Cursor’s file, and confirm the connection by signing in through the browser. On a computer with no browser, use the entry with the secret.
- Step 3 of 8
Role prompts: your team’s process as console commands
A prompt is one of your team’s rules or procedures, in markdown. A console fetches it with one command, and with a plan key it gets the whole plan too.
- Step 4 of 8
The agent’s questions and your answers
When the plan doesn’t settle something, your agent asks a question in the plan, and you answer on the plan’s screen. The question and the answer stay in the plan document, so nothing has to be settled on the side.
- Step 5 of 8
Connect Cursor with a secret on a computer with no browser
Cursor CLI on a computer with no browser connects to featureloom with the entry with the secret. The secret works like the console’s password, so you keep it to yourself.
- Step 6 of 8
Your consoles: several at once, Reconnect and Disconnect
On the Your consoles card you see each of your consoles in the organization: its name, its state and its term. There you also give a console a new connect command or disconnect it.
- Step 7 of 8
An automation: an account for jobs on a server, with its own key
A job no person runs, on a server or in CI, the automatic tests and deployments after every code change, works as the organization’s automation: with rights of its own and a key valid until its term.
- Step 8 of 8
Slack: plan events on a channel
Your team sees on a Slack channel what happens to plans: a new plan, the start of realization, a question on a plan and finished work. An organization administrator connects the channel with one webhook address created in Slack.
2 steps
Subscription and billing
What you pay for in featureloom: the trial, paid seats and cancelling, and apart from them the balance that pays for featureloom’s model writing plans in the app.
- Step 1 of 2
Subscription: the 30-day trial, paid seats and cancellation
The Subscription and limits screen says which plan the organization has, how long the trial lasts and what you pay for. It is also where you buy the subscription or cancel it.
- Step 2 of 2
Balance and the Plan generator: what is billed separately
Your agents work on your own Claude or OpenAI subscription. The one thing billed separately is featureloom’s model that writes plans in the app: from the trial package first, then from the organization’s balance.
2 steps
Account and data
Your account across every organization, your password and signed-in devices, and for an administrator the export of the whole organization as one file.
- Step 1 of 2
Your account, password and signed-in devices
One account serves you in every organization. On the Your account screen you set the name others see, change your password and check which browsers the account is signed in on.
- Step 2 of 2
Export the organization as one ZIP file
An administrator downloads all of the organization’s data as one ZIP file, in markdown and JSON, also while the organization is read-only.