Creating a project
Start a project in the web app, answer the five vision questions, and publish the story map IntentDocs drafts from them.
A project holds one product's spec: its vision, its story map and everything your agents build against it. You create it in the web app in a few minutes. You don't need a codebase yet.
Start the project
- Sign in at intentdocs.com and open Projects.
- Choose New project.
- Pick how you're starting:
- Starting fresh — no existing code. You answer the vision questions yourself.
- I have an existing codebase — your agent reads the repository and writes a report you can import. See Brownfield agent prompt.
- Give the project a name and, if you like, a description of the problem it solves.
- Optionally link GitHub. Starting fresh, you can tick Create a private GitHub repo for this project. With an existing codebase, you can pick the repository under Connect a repo (optional). Both need Connect GitHub first.
- Choose Create project.
The project opens on its Spec tab, at Vision.
Answer the vision
The vision is five questions. Plan, Validate and the rest of Spec stay locked until all five have an answer.
| Question | What it asks for |
|---|---|
| Who are your users? | The people who will use it: their role, context and what they care about. |
| What problem are you solving? | The specific pain. What's broken, slow or missing for them today. |
| What makes them switch? | The trigger or frustration that would make someone stop and try your product. |
| What's the first release? | The smallest useful version. Not the vision, the thing you'd ship in two weeks. |
| How will you know it's working? | The earliest signal that real people find it valuable. |
Each question offers Show me an example and What do you mean by this?. Press Continue to save an answer and move on. You can edit any answer later from the same list.
Your agent can read and write the vision too, with the MCP tools get_vision and set_vision. Older agents may call them get_constitution and set_constitution; they are the same tools. See Vision.
Generate the story map
When the fifth answer is in, IntentDocs shows Vision complete.
- Choose Generate the story map. IntentDocs drafts activities and stories from your answers.
- Choose Review story map →. Rename or remove anything in the draft.
- Choose Publish map. Nothing is saved until you do.
The map opens on Story map. Every story has acceptance criteria you can edit. See The Spec tab.
Note: if generation fails, your answers are kept. Choose Try again.
Other ways to start
- From the terminal.
npx intentdocs startwalks you from a problem statement to a new project, andnpx intentdocs scopeturns it into a story map. See CLI: Project setup. - From a PRD. Your agent can import an existing requirements document with the
import_prdMCP tool, or you can runnpx intentdocs import. See CLI: AI features.
Next
Connect your agent so it can read the spec.