# TekDek Tool Requirements

**Last Updated:** 2026-04-11  
**Status:** Brainstorm → Implementation Roadmap

## Overview

This document outlines the tools needed to manage TekDek personas, content, narratives, and community. Some are critical for MVP; others can wait for Phase 2/3.

---

## Critical Path Tools (MVP Phase 2)

### 1. Persona Management System
**Purpose**: Central hub for persona profiles, voice guides, platform presence tracking, and character consistency.

**Must-have features**:
- Persona profile (name, expertise, voice/tone guide, relationships)
- Platform presence tracking (which channels they publish on)
- Voice guide (how they write, speak, communicate across formats)
- Personality consistency rules (what's on-brand vs. off-brand)
- History/timeline (articles, posts, video links across all platforms)

**Data model**:
```
Persona
├── Profile (name, bio, expertise, avatar)
├── Voice Guide (tone, vocabulary, communication style)
├── Relationships (allies, rivals, neutral, team affiliations)
├── Platforms (YouTube URL, TikTok handle, personal site, GitHub)
├── Content Log (all published content, links, dates)
└── Character Arc (current story state, traits, evolution)
```

**Can be**: Markdown docs + knowledge base, or simple database/spreadsheet

**Example**: Brick persona doc with his voice rules, platform presence, and consistency checklist

---

### 2. Storyline & Narrative Planning Tool
**Purpose**: Track character arcs, plan narrative beats, schedule content tie-ins, and coordinate drama.

**Must-have features**:
- Arc planner (3–6 month timelines, character involvement, key beats)
- Content calendar tied to narrative (posts that support specific story moments)
- Conflict/collaboration tracker (who's involved, what's the status)
- Engagement hooks (what will drive user interest)
- Curated content log (you approve/reject content before publication)

**Data model**:
```
Narrative Arc
├── Title (e.g., "The PHP vs Node Debate")
├── Timeline (start date, end date, key milestones)
├── Characters involved (personas, roles)
├── Beats (weekly/monthly story moments)
│   └── Content tie-ins (which posts/videos/articles support this beat)
├── Engagement hooks (what draws people in)
├── Status (planned, active, resolved)
└── Results (virality, user engagement, educational value)
```

**Can be**: Markdown docs + spreadsheet, or custom dashboard

---

### 3. Content Curation & Approval System
**Purpose**: Central intake for persona-generated content; you review for technical accuracy, narrative fit, and voice consistency before publication.

**Must-have features**:
- Content submission form (title, draft, persona, narrative arc tie-in)
- Approval workflow (pending, approved, rejected with feedback)
- Scheduling (publish date/time, multi-platform coordination)
- Consistency check (does this match the persona's voice?)
- SEO/tagging (keywords, trending alignment)

**Can be**: Simple form + spreadsheet, or integrated into Persona Portal

---

## Phase 2 Tools (MVP Nice-to-Have)

### 4. Persona Agent Framework
**Purpose**: AI agents that generate content drafts in each persona's voice.

**Must-have features**:
- Voice consistency (trained on persona's previous work)
- Topic/expertise alignment (generates appropriate content)
- Multi-format output (blog posts, social media captions, code comments)
- Draft generation (not auto-publish; requires your curation)

**Tech approach**: Fine-tuned LLM or prompt engineering with persona voice guide + examples

**Can be**: Custom Python scripts, or built into TekDek agent system (OpenClaw subagents)

---

### 5. Content Syndication System
**Purpose**: Pull content from persona's independent platforms (YouTube videos, blog posts, GitHub repos) into Stack Legion aggregation.

**Must-have features**:
- Feed ingestion (RSS, API, webhook)
- Metadata extraction (title, date, persona, expertise tag)
- Cross-linking (persona's site + Stack Legion)
- Attribution (credit the original source)

**Can be**: Custom integrations or use existing tools like IFTTT, Zapier

---

## Phase 3+ Tools (Growth & Scale)

### 6. Persona Portal
**Purpose**: Publishing and identity management platform for personas.

**Must-have features**:
- Publishing interface (write, schedule, preview)
- Analytics dashboard (views, engagement per persona)
- Revenue tracking (integrations with YouTube, Patreon, course platforms)
- Branding tools (custom templates, fonts, colors)
- Community moderation (comments, member interactions)

**Status**: Under development by external team (mentioned in info dump)

---

### 7. Community & Gamification System
**Purpose**: Stack Legion member engagement through challenges, points, leaderboards.

**Must-have features**:
- Challenge creation (persona-authored coding challenges)
- Points/badges system (users earn for participation)
- Leaderboards (global, per-challenge, per-persona)
- Member-exclusive content (early access to articles, special threads)

**Status**: Part of Stack Legion site (external team)

---

### 8. Analytics & Growth Dashboard
**Purpose**: Track engagement, SEO, trending alignment, and narrative arc performance.

**Must-have features**:
- Persona performance (views, engagement per content)
- Narrative arc metrics (virality, user investment, discussion volume)
- SEO tracking (search rankings, traffic sources)
- Trending alignment (what's being discussed, how our content fits)
- Cohort analysis (which personas drive retention, growth)

**Can be**: Google Sheets + custom queries, or custom dashboard

---

## Nice-to-Have (Future)

### 9. Trend Detection & Engagement Hooks
**Purpose**: Monitor tech trends, industry events, and social media trends to align storylines.

**Must-have features**:
- Trend monitoring (GitHub trending, HN, Reddit, Twitter)
- Engagement tie-ins (how can current personas capitalize on this trend?)
- Content gap analysis (what's missing in the narrative, what would resonate)

---

### 10. Persona Conflict Simulator (Advanced)
**Purpose**: AI-powered brainstorming of conflict scenarios and narrative outcomes.

**Must-have features**:
- "What if" scenarios (what happens if Persona A and B clash over X?)
- Engagement prediction (will this generate discussion?)
- Narrative coherence check (does this fit the arc?)

**Status**: Experimental; lower priority

---

## Build vs. Buy vs. Integrate

### Build
- **Persona Management System**: Custom markdown docs + knowledge base (qmd)
- **Storyline Planning**: Custom docs + spreadsheet
- **Content Curation**: Custom form + workflow
- **Persona Agent Framework**: Custom OpenClaw agents (subagents)

### Buy / Integrate
- **Persona Portal**: Currently under external development
- **Community & Gamification**: Part of Stack Legion (external)
- **Syndication**: Zapier, IFTTT, or custom API integrations
- **Analytics**: Google Sheets, Mixpanel, or custom dashboard

### Partner / Outsource
- **Stack Legion site**: External development team
- **Video hosting**: YouTube, TikTok (personas own these)
- **Course platform**: Udemy, teachable, or custom

---

## Immediate Action Items

1. **This week**: Document Brick persona (voice guide, consistency rules)
2. **This week**: Create narrative arc template and first arc plan
3. **Next week**: Build content curation spreadsheet/form
4. **Next week**: Sketch 3–5 additional persona profiles
5. **Following week**: Start persona agent prototyping (test voice consistency)
6. **Following week**: SEO/growth strategy brainstorm

---

## Questions for Dev Team (External)

These are requests for the Stack Legion development team to handle:

1. Can the Persona Portal support API integrations for automated content ingestion?
2. Does the community system support persona-authored challenges and gamification?
3. Can we hook into analytics to track narrative arc performance?
4. What's the timeline for beta launch?
5. Can we integrate BookStack or similar for persona knowledge bases?