Skip to main content
If the plan already lives in Linear, Trello, Jira, or a spreadsheet, you do not have to retype it. Your agent does the import. It can already reach those tools, and it can write into the project graph.

​
Linear, during onboarding

Linear has a proper puller. Say so during the onboarding interview and your board comes across in the same session: pulled, read for the level that actually carries your structure, and mapped into phases, enablers and cards. Where it is confident, it places things. Where it is not, it groups the doubtful ones and asks you once rather than forty times.

​
Everything else

Once your agent is connected, give it access to the tool your work lives in — Linear, Trello, Jira, GitHub Issues, Notion — the same way you would for any other task, using that tool’s own connector or API token. Then ask for the import in plain language:
Read my Linear issues for the current cycle, and create a card in alicein under the right enabler for each one. Use my labels to decide which enabler. Skip anything already closed.
Your agent reads the source, decides where each item belongs in your plan, and creates the cards. Open alicein.app/workspace to see them — click an enabler to open its cards.
Give it your credentials for the other tool, never the other way round. Alice.In does not ask for, hold, or store tokens for your other services — the connection is between your agent and that tool, on your machine.

​
Worth saying in the prompt

  • Where things should land. “Everything labelled infra goes under the deployment enabler.” Otherwise it will guess, and guesses are what you will spend the evening correcting.
  • What to skip. Closed issues, someone else’s backlog, the graveyard column.
  • How much to bring. The current cycle usually beats the entire history. You can always import more later.
  • Whether to bring the discussion. Long comment threads can come across as a card’s description, or be left behind.

​
Other sources

The same approach works for anything your agent can read:
  • A document or spreadsheet — “turn this roadmap doc into phases and enablers.”
  • A repository — issues, milestones, or a TODO.md.
  • A conversation — paste the notes from a planning call and ask for cards.

​
Check it before you trust it

An import is a first draft. Walk the map afterwards: drag enablers between phases, rename what reads badly, delete the noise.

​
Going the other way

There is no export button yet. Your record is a git repository; we will hand you everything in it — or delete all of it — whenever you ask.