Project Intake
Reads your documents, notes or a few lines about an idea and writes the Project Brief: what the project is, section by section, with every gap marked as an open question. Then it asks the client what's still open with a survey they answer in any browser, and reads their answers back into the Brief.
Install
In Claude Code
/plugin marketplace add ronalddlopez/turbinez-pm/plugin install project-intake@turbinez-pmFrom the terminal
claude plugin marketplace add ronalddlopez/turbinez-pmclaude plugin install project-intake@turbinez-pmThe first command once; then any agent. Needs Claude Code and Node.js 22 or later.
Connect to Turbinez
/project-intake:connectOptional: the agent then works in a project in Turbinez, with your team. How connecting works
What it makes
The real thing, not a picture: what Project Intake made in our tests.
Project Brief
Written from the documents of Wrenfield, a made-up insurance broker (a SOW, kickoff notes, policies and data documents), then with the sponsor's answers to the first survey read in. 18 open questions still to settle.
Survey
The first survey for Wrenfield's sponsor: 10 questions, only about what the documents left open. Answer it and press Save answers to see what the client sends back.
Use it
Start intake
Point it at your documents, or describe the idea in a few lines. It writes the first Brief and a survey for the client.
/project-intake:start-intake docs/Read the answers
Put the answers file the client saved in your project folder. If the folder is connected to Turbinez, upload the file on the survey there instead. Then say so. It reads every answer into the Brief and asks a short second round only if something is still open.
/project-intake:read-answersChange the Brief
In plain words: "Add that the launch moved to June", "Write the out-of-scope section from my notes".
Its tools
A small local server: your project's files, or the connected project in Turbinez.
| Tool | What it does |
|---|---|
read_brief | The Brief by section, with its open questions |
write_brief | Some sections at a time; never over a section changed since it was read |
write_survey | A new survey and its page; a survey never changes once written |
list_surveysread_survey | The surveys and how many answered; one survey with every answers file |
read_board | Whether there's a board yet (read only) |
Connect to Turbinez
Optional. Connected, Project Intake works in a project in Turbinez instead of the folder's files, with the same tools, and your team sees every change.
/project-intake:connectSigns you in through the browser and links this folder to a project in Turbinez, a new one or one your team already has. From then on, the agents write there.
/project-intake:status- Says which project the folder is connected to and whether the connection works.
/project-intake:import- Brings the folder's own board, Brief and surveys into an empty project, when they didn't come in on connect.
/project-intake:export- Writes the project's copy into
turbinez/, so the agents can work from the files after you disconnect. /project-intake:disconnect- Ends the connection. The folder's files stay, and the agents work from them again.
A folder that already has a board, a Brief or surveys can bring them into a new, empty project when it connects, or leave them where they are.
Connecting needs a free Turbinez account. Turbinez is in early access, inviting teams a few at a time.
What it promises
Nothing invented
Every unknown is an open question, never a guess. The Brief says only what your documents and the client's answers say.
Your words kept
A paragraph you add to the Brief stays word for word. The tools refuse to write over a section that changed since the agent read it.
A short ask
At most two rounds of surveys: ten questions, then five. Only what the documents left open, never what they already say.