Update V1.1
Sep 4, 2026v1.1
Better questions for different projects
Not every software project needs the same discovery process.
Codelab now adapts its Interview based on what you're building and the perspective you need.
General Interview
Use General mode for broad project discovery.
It's useful when you want Codelab to help structure an idea without requiring specialized domain knowledge.
Specialist Interview
Switch to Specialist mode when your project benefits from a particular professional perspective.
Specialist discovery can consider roles such as:
- Web Developer
- SEO Specialist
- Product Designer
- Marketer
- Business Strategist
- Business Owner
- Content Creator
- HR Specialist
- Writer / Storyteller
- Finance / Accounting Specialist
The resulting project still uses the same Blueprint structure.
Specialist mode simply helps discover more relevant context before the Blueprint is created.
Domain-aware discovery
Projects can also provide domain context such as:
- SaaS
- E-commerce
- Education
- Finance
- HR & Recruitment
- Healthcare
- Real Estate
- Media
- Legal
- Hospitality
- Logistics
- Manufacturing
- Nonprofit
This helps questions stay relevant to the project instead of following a generic questionnaire.
Scan URL
Have an existing website, reference site, or competitor?
Scan a URL and use the discovered information as additional project context.
This can reduce repetitive Interview questions and make it easier to work from an existing product.
Project Decisions
Important choices can now remain part of the project's ongoing context.
Examples:
- database choice
- authentication method
- deployment target
- payment provider
- architectural constraints
Future project work can reference these decisions instead of repeatedly rediscovering them.
Better handling of uncertainty
Not every decision needs to be known immediately.
Codelab can distinguish between information that is:
- Confirmed
- Assumed
- Unknown
Unknown decisions can remain unresolved instead of being silently invented.
Why it matters
Project discovery becomes less about completing a form and more about building a reliable understanding of the software you actually want to create.