Project Blueprint 8 min read

Auto-Pilot mode

One click, full blueprint. Auto-Pilot runs the entire 6-stage generation pipeline end-to-end with zero manual intervention.

What is Auto-Pilot?

Auto-Pilot is the one-click button in your project sidebar that runs the complete generation pipeline — Research, Architecture, Features, Technical Design, Phases, and Prompts — automatically, in sequence, with no manual steps required.

It's the fastest way to go from a filled-out wizard to a complete, developer-ready blueprint. Total generation time is typically 2-5 minutes depending on the complexity of your product idea.

How to use Auto-Pilot

1

Complete the Idea step

Fill in your product description, target users, business model, and any other wizard context. The more you provide, the better the output.

2

Click 'Generate All' in the sidebar

The orange gradient button at the top of the project sidebar. This triggers the Auto-Pilot pipeline.

3

Watch the progress

The button transforms into a real-time progress indicator showing the current stage name (e.g., "Research", "Architecture") and completion percentage. A pipeline progress bar also appears at the top of the content area.

4

Review your completed blueprint

Once all 6 stages are done, navigate through each section to review the generated content. Every section (Research, Architecture, Features, etc.) now has full AI-generated output.

What happens during Auto-Pilot

Stage 1
Research runs first — generates market analysis, competitor mapping, and audience profiles.
Stage 2
Architecture uses research findings to design system components, database schema, and API structure.
Stage 3
Features creates prioritized feature specs (Now/Later/No) based on architecture capabilities and market needs.
Stage 4
Technical Design deep-dives into implementation details — auth flows, state management, error handling.
Stage 5
Phases breaks the features into sprint-based development phases with story points and milestones.
Stage 6
Prompts generates AI-optimized prompt packs for Cursor/Copilot/Claude, referencing your specific architecture and features.
💡

Each stage waits for the previous one to complete before starting. This ensures downstream stages have full context from upstream outputs. If any stage fails, the pipeline pauses and you can retry from the failed stage.

When NOT to use Auto-Pilot

Auto-Pilot is best for first-time generation. In these cases, use individual stage generation instead:

  • You've updated only one section of your wizard (e.g., changed the tech stack) — regenerate only Architecture and downstream
  • A specific stage produced unsatisfactory results — retry just that stage
  • You want to review and iterate on Research before generating Architecture
  • You're experimenting with different positioning strategies and want to compare Research outputs
⚠️

Running Auto-Pilot on a project that already has generated content will overwrite all existing outputs with new generations. Your previous content is NOT preserved unless you create a new Version first.

Pipeline progress bar

During Auto-Pilot execution, a thin progress bar appears at the top of the content area. It shows:

  • Current stage name — which of the 6 stages is currently being processed
  • Overall percentage — how far along the entire pipeline is (0-100%)
  • Animated fill — visual progress indicator with smooth transitions

The progress bar disappears automatically once all stages are complete or if the pipeline is cancelled.