A pragmatic backlog mapped to the roadmap phases. Keep changes scoped; prefer iterative merges.
- Update README with vision, architecture, MDX/YAML, components, integrations
- Add ROADMAP.md and this TODO.md
- Add sample startup MDX:
startups/acme-claims.mdx
Acceptance:
- All docs present and coherent
- MDX sample committed (not necessarily rendered yet)
- Install
next-mdx-remote-client - Add
app/startups/[slug]/page.tsxto render a startup by slug - Implement loader:
- Read
startups/{slug}.mdx - Parse frontmatter (YAML)
- Render default export via next-mdx-remote-client
- Read
- Create components:
components/Hero.tsxcomponents/Problem.tsxcomponents/Solution.tsxcomponents/Features.tsxcomponents/Steps.tsx
- Default generation:
- If component props are missing, generate from YAML frontmatter
- If component file missing, fall back to a default renderer
Acceptance:
- Visiting
/startups/acme-claimsrenders the sample with defaults when needed
- Create Zod schema for frontmatter sections (LeanCanvas, VMV, OKRs, StoryBrand, Branding, Pricing, PRD, MVP, Experiments, Variants)
- Validate on load; produce readable error messages
- Add unit tests for schema parsing and default generation
Acceptance:
- Invalid YAML fails with a clear message; valid YAML renders
- Create Occupations + NAICS enumeration source
- Implement research workflow using Vercel AI SDK
- Implement scoring:
- remote_on_laptop
- model_capability
- data_availability
- integration_surface
- overall weighted score
- Persist scores to YAML
Acceptance:
- Can generate or update scores for a set of NAICS/occupations
- Lean Canvas generator
- VMV generator
- OKRs generator
- Hypotheses and Experiments generator
- Variants generator
- Name/Brand/Domain generator (builder domains/subdomains/mcp)
- StoryBrand generator
Acceptance:
- Running generators updates the frontmatter for a startup
- Generate theme/fonts/colors/logo prompt
- Create MDX UI templates (template/def/types/mdxui)
- Compose landing page sections from YAML
Acceptance:
- Landing page renders with generated branding and sections
- Map Pricing frontmatter to Stripe objects
- Pricing page renders plans from YAML
- Checkout integrates Stripe
Acceptance:
- Pricing displays correctly; checkout initiates
- PRD generator from research outputs
- MVP scoping and milestone planning
Acceptance:
- PRD and scope present in YAML and rendered sections
- Implement Devin API integration:
- Task creation per function/workflow/service
- Progress tracking
- Slide/deck generation for Business-as-Code
Acceptance:
- Running automation produces tasks and slides
- TypeScript strict mode
- Server components for data loading
- No secrets in repo; use env vars
- Tests for schema and critical transforms
- Content hot-reload for startups/*.mdx
- Multi-tenant builders for subdomains
- Analytics on startup funnel