One Plan Area per Project — With File Attachments the AI Can Read Too
On bigger projects I know the problem all too well: the actual plan lives in some notes document, the important files sit in a folder on my hard drive, and when I then sit down to work on the project with the AI, I have to dig both out again and paste them in one by one. That bit of housekeeping is exactly what I wanted to get rid of. So in boostN, every Big Project now has its own plan area — right at the top of the project, where it belongs.
The plan now lives at the project, not next to it
The basic idea is simple: instead of keeping the plan somewhere separate, I write it straight onto the project. It’s a proper writing space with formatting — headings, lists, emphasis — not something choppy, but text you can actually think in.
And I’m not locked into a single plan. I can create several plans per project, each with its own done status. That lets me, say, keep the rough direction apart from the concrete next step without opening a second tool for it. Once a plan is worked through, I check it off and it moves out of the way.
What I like is that it’s the same plan building block that also sits inside the Vision Board. Which means: no matter where in the app I’m planning, it feels the same. One concept, learned once, identical everywhere.
Drag files in — and pull them back out
The part I use most day to day is the file attachments right at the plan area. I can pick a file with the ”+ File” button or simply drag and drop it into the window, several at once if I like. Downloading is a single click.
And it barely matters what kind of file it is: a Markdown note, an exported HTML, a PDF with the client’s brief — the area takes anything up to 20 MB per file. So the reference material finally sits where the plan is, instead of scattered across three folders and two chats.
What I use it for
The client’s brief as a PDF, a Markdown file with the collected requirements, and a couple of screenshots — all on the same project. When I come back two weeks later, the whole context is right there.
The interesting part: the AI reads along
Up to here it’s a tidy but unspectacular thing — a plan plus a few attachments. The real difference comes from the AI agent being able to read the plan and write to it as well.
In practice that means: I no longer have to laboriously explain the plan to the AI every time or paste it in. It can read a project’s plan directly, take its bearings from it, and, on request, keep writing it. It pulls the attached files through secure, time-limited links — so it has the project context right at hand, without me becoming the bridge between plan and chat.
That changes how I work more than it sounds at first. Instead of “read through this again, then let’s talk,” it becomes “you know the plan, let’s pick up at the next point.” Context is no longer something I have to supply, but something that’s simply present at the project.
Private stays private
One thing mattered to me about the file attachments from the start: this is private storage. Only the owner can reach their files, no one else. And when something gets downloaded, it’s always delivered as a file and never just executed in the browser — especially with HTML files that’s an important distinction, one you normally shouldn’t have to think about as a user, because it ought to just be handled cleanly.
Conclusion
In the end the plan area is about one single, rather unglamorous thing: context in one place. The plan, the reference files, and the AI agent that knows both — all on the same project, instead of scattered across notes, folders and chat histories. For me it’s one of those building blocks you don’t want to do without after a few days, because the constant digging-around simply falls away.
Entdecke mehr
Working with AI: one word, two actions — and an hour of debugging
One word, two meanings: I blocked a Git commit, the AI heard deploy. Why a shared vocabulary decides everything when you work with AI.
GlossarSpeech-to-Text (STT)
Speech-to-Text refers to the automatic conversion of spoken language into text by an AI model. In an AI workflow, STT replaces the keyboard as the input channel — what matters is model size and domain vocabulary.
LexikonAutomating AI Workflows
No-/low-code automation with Make, Zapier and n8n: building blocks, use cases for agencies and SMBs, pricing models and the costliest pitfalls.