5.4 KiB
TekDek Master Plan — Quick Checklist
This Week (Phase 0 Decisions): 🔴 CRITICAL PATH
Full Plan: See /knowledge/TekDek-Master-Project-Plan.md
YOUR DECISIONS THIS WEEK (Glytcht)
🔴 DECISION 1: Brick's Technical Specialty
Why: Templates his first articles, determines his voice in depth
Options: Backend? DevOps? Full-stack? Architecture? Database design?
Action: Pick one, I'll finalize his profile
Deadline: TODAY if possible
🔴 DECISION 2: Initial Persona Roster (Personas 2–10)
Why: Determines content calendar, arc participants, expertise mix
Options: 5–10 people (real people you know, or we recruit during Phase 1?)
Action: Sketch out 5–9 personas (name, expertise, rough voice idea)
Deadline: End of Week 1
🔴 DECISION 3: First Narrative Arc
Why: Drives all content scheduling and engagement
Options:
- PHP vs Node debate (Brick + Frontend persona clash)
- Learning journey (new persona builds in public)
- Collaboration (multiple personas build something together)
- Other?
Action: Pick arc, I'll plan beats and content calendar
Deadline: End of Week 2
🔴 DECISION 4: Revenue Model
Why: Dev team needs this to build payment processing
Options:
- Membership tiers (Free / $5/mo / $15/mo)
- Courses ($29–$99 each)
- Persona revenue share (70/30? 80/20?)
- Sponsorships?
Action: Rough numbers, I'll detail it
Deadline: End of Week 3
🔴 DECISION 5: Launch Target
Why: Everything else is scheduled around this
Options: Q3 2026? Q4 2026? Early 2027?
Action: Commit to date, I'll build sprint plan
Deadline: End of Week 4
MY DELIVERABLES THIS WEEK (ParzivalTD)
- TekDek-Strategy.md ✅
- Tool-Requirements.md ✅
- Brick-Profile.md (stub) ✅
- TekDek-Brainstorm-Reference.md ✅
- TekDek-Master-Project-Plan.md ✅ (THIS DOCUMENT)
- Finalize Brick-Profile.md (pending your decision #1)
- Persona Template (for personas 2–10)
- Narrative Arc Template
- Content Curation Workflow doc
- Persona Roster System spec (design)
PHASE 0 TIMELINE
Week 1: Decisions 1–2 locked, Brick finalized, 5 personas sketched
Week 2: Decision 3 locked, Arc 1 planned, content calendar drafted
Week 3: Decision 4 locked, revenue model detailed
Week 4: Decision 5 locked, all templates + specs done, dev team sync
PHASE OVERVIEW (REFERENCE)
| Phase | Timeframe | Goal | Team Lead |
|---|---|---|---|
| Phase 0 | NOW - Week 4 | Lock decisions, design systems | TekDek (Glytcht) |
| Phase 1 | Week 5–12 | Build personas, test narrative, publish content | TekDek + Dev |
| Phase 2 | Week 13–16 | MVP launch, public beta, validate model | Dev (Portal launch) |
| Phase 3 | Week 17–24 | Scale to 10 personas, 2 verticals | TekDek (narrative expansion) |
| Phase 4 | Week 25+ | 3–5 verticals, 50+ personas, enterprise scale | Both teams |
CRITICAL SUCCESS FACTORS (PHASE BY PHASE)
Phase 0 ✅ (This Week)
- Decisions locked
- Personas defined
- Arc 1 planned
- Dev team aligned
Phase 1 ✅ (Week 5–12)
- Brick voice test (2–3 articles) ✅
- 3 personas live ✅
- Arc 1 live with content tied to beats ✅
- APIs operational ✅
- Go/No-Go for Phase 2 (Week 12) ✅
Phase 2 ✅ (Week 13–16)
- Stack Legion MVP public ✅
- 500+ users ✅
- Arc 1 generating engagement ✅
- Revenue streams working ✅
- Go/No-Go for Phase 3 (Week 16) ✅
Phase 3 ✅ (Week 17–24)
- 10 personas across 2 verticals ✅
- Multiple arcs in parallel ✅
- 10K+ monthly users ✅
- Replication template proven ✅
Phase 4 (Week 25+)
- Scale to 3–5 verticals ✅
- 50+ personas ✅
- $50K+ MRR ✅
QUESTIONS FOR DEV TEAM (FIRST SYNC)
- Tech stack? (Rails? Node? Django?)
- Realistic MVP launch date?
- Can you design APIs for persona data, content sync, analytics?
- What's the user scaling limit before we need microservices?
- Payment processing / revenue sharing capability?
- How do we integrate management system (OpenClaw) with portal?
WEEKLY SYNC SCHEDULE (STARTING WEEK 1)
TekDek (Glytcht + ParzivalTD) + Dev Team
When: [TIME TBD]
Duration: 30 min
Agenda:
- Blockers
- Phase 0 checkpoint (week 1–4)
- Next week's deliverables
- Dependency updates
NEXT STEP: RESPOND TO DECISIONS
Once you give me Decisions 1–3 (Brick specialty, 5 personas, first arc), I can:
- Finalize all persona profiles
- Plan content calendar through end of Q2
- Design system architecture (what to build in OpenClaw)
- Provide dev team with technical requirements
Then we're off to the races.
FILES TO REVIEW
Full Strategy:
/knowledge/TekDek-Strategy.md— Vision, layers, models/knowledge/Tool-Requirements.md— What to build/knowledge/personas/Brick-Profile.md— First persona (template)/TekDek-Brainstorm-Reference.md— Quick brain dump
Master Execution:
/knowledge/TekDek-Master-Project-Plan.md— THIS. Read it.
Session Log:
/memory/2026-04-11-extended.md— What we did today
DECISION LOG
[ ] 1. Brick's specialty — PENDING
[ ] 2. Initial persona roster (5–9 people) — PENDING
[ ] 3. First narrative arc — PENDING
[ ] 4. Revenue model — PENDING
[ ] 5. Launch target date — PENDING
Once filled, we move to execution.