Skip to content
intentdocs/ docs
Docs menu
MCP Integration · 3.6

Spec my idea

The steps a chat assistant follows from an app idea to a story map the founder reviews, and where it stops for the person.

A chat assistant that connects to IntentDocs follows one flow, from an app idea to a story map the founder reviews. The server instructions and the Spec my idea prompt are this same text.

The steps

  1. Agree a project name. Stop for the person before creating the project.
  2. Call create_project with that name and a one-line idea. It creates the project in their personal workspace. If it's refused for the plan's project limit, show the founder the options it lists; archive a project only with their yes (archive_project with confirm: true).
  3. Ask the five vision questions one at a time and save each with set_vision (alias set_constitution). get_vision returns the next unanswered question with its heading and hint — ask that one in those words. One key is enough; the others stay. A different answer to a question that already has one needs confirm: true. Stop for the person after each vision question.
  4. Draft the story map with create_stories.
  5. Give the founder the review link create_stories returns.
  6. Stop after handing over the draft link.

Where the assistant stops

Stop for the person at three points: before creating the project, after each vision question, and after handing over the draft link.

When you name a story

Whenever you name a story, show its link (story_url) so the person can open that story.

The Spec my idea prompt

The server offers a prompt named spec-my-idea, titled Spec my idea. Loading it starts the flow:

Spec my idea. The person has an app idea. Start this flow and follow the steps in order.
 
1. Agree a project name. Stop for the person before creating the project.
2. Call create_project with that name and a one-line idea. It creates the project in their personal workspace. If it's refused for the plan's project limit, show the founder the options it lists; archive a project only with their yes (archive_project with confirm: true).
3. Ask the five vision questions one at a time and save each with set_vision (alias set_constitution). get_vision returns the next unanswered question with its heading and hint — ask that one in those words. One key is enough; the others stay. A different answer to a question that already has one needs confirm: true. Stop for the person after each vision question.
4. Draft the story map with create_stories.
5. Give the founder the review link create_stories returns.
6. Stop after handing over the draft link.
 
Stop for the person at three points: before creating the project, after each vision question, and after handing over the draft link.
 
Whenever you name a story, show its link (story_url) so the person can open that story.

After the draft

On the main MCP address, Building a story follows the build loop that start_story hands over.

On the ChatGPT address (/api/mcp/chatgpt), which has no build tools, Building happens in a coding agent, not in this chat. Connect one: https://docs.intentdocs.com/docs/getting-started/connecting-your-agent. Don't claim a story is built or tested.