Skip to main content

Planning Docs

Planning docs capture product, architecture, roadmap, and backlog decisions before they are promoted into stable public, developer, or engineering docs.

Core planning set​

  • docs/planning/research.md - ecosystem scan and adjacent-code notes
  • docs/planning/product-spec.md - MVP scope, user flows, and product rules
  • docs/planning/architecture.md - suggested system design, data model, and integrations
  • docs/planning/prd.md - product requirements draft for v1 and near-term expansion
  • docs/planning/agent-integration-surface.md - external agent-consumable VRDex skill, API, website navigation, and MCP direction
  • docs/planning/calendar-integration.md - Google Calendar export/sync direction for event workflows
  • docs/planning/seed-import-model.md - reviewed partner/list seed-import model and fake fixture shape
  • docs/planning/world-discovery.md - world pages, creator attribution, active-world discovery, and creator-commerce boundaries
  • docs/planning/marketplace-api-research.md - marketplace sync gate, provider posture, and disallowed storefront data
  • docs/planning/engineering-strategy.md - stack, testing, verification, and agentic factory plan
  • docs/planning/docs-strategy.md - Docusaurus and source-of-truth documentation plan
  • docs/planning/epics.md - phased epic breakdown for v0.5, v1, and v1.5
  • docs/planning/issue-seeding.md - how to split epics into GitHub issues and milestones
  • docs/planning/dependency-map.md - hard/soft dependency map across the seeded backlog
  • docs/planning/issue-drafts.md - drafted GitHub issue bodies captured from planning work

Working rule​

  • keep planning decisions here instead of leaving them only in chat
  • when backlog structure changes, update docs/planning/epics.md, docs/planning/issue-seeding.md, and docs/planning/dependency-map.md together where practical