Session 1 — The Constitution
Goal: Confirm the project identity, scope boundaries, and design philosophy are still accurate and aligned. Estimated time: 30 min
Reading Order
| # | File | What It Covers |
|---|---|---|
| 1 | CONTRIBUTING.md | The single entry point. Repo structure, tech stack, commands, service map, forbidden actions. |
| 2 | PRODUCT_project-scope.md | Vision, three pillars, value pillars, design principles, target segments, V0.1 scope. |
| 3 | STRATEGY_platform-vision.md | Execution horizons (v0.1 → H3), GTM strategy, concierge onboarding, competitive differentiation. |
| 4 | STRATEGY_feature-subsets.md | The 6 modular product subsets, inter-context dependencies, wedge strategy. |
| 5 | STRATEGIC_BLIND_SPOTS.md | 14 tracked blind spots (SB-1 through SB-14). Status tracker. |
🔍 What to Validate
- [ ] Does the V0.1 scope in
project-scope.mdstill match what you are actually building right now? - [ ] Are the horizon markers (
[v0.1],[v0.2],[future],[vision]) still correctly assigned infeature-subsets.md? - [ ] Blind spots SB-2 and SB-9 are marked ✅ resolved — confirm you agree.
- [ ] The 10 open blind spot items — are any now resolved or escalated?
- [ ] The brand identity section in
project-scope.mdis in German while the rest is English. Intentional? - [ ]
CONTRIBUTING.mdservice map — do all endpoints and deploy triggers still match reality? - [ ]
CONTRIBUTING.mddomain guidance table — do the skill paths still match the.agents/skills/directory?