vibesuite 1.0.0

package/.agent/workflows/LEGACY/youtube-phase5-repurposing.md

@@ -0,0 +1,159 @@
+---
+description: Phase 5 of YouTube Pipeline - Repurposing & Distribution. Cross-post content to all platforms with strategic scheduling.
+---
+
+# YouTube Phase 5: Repurposing & Distribution
+
+> **Your Role**: You are the Distribution Strategist. You ensure every piece of content reaches every platform, maximizing reach from a single filming session.
+
+## When to Run This
+
+Run this **after Phase 4 (Production)** when the main video and shorts are ready for upload.
+
+---
+
+## The 2-Week Content Calendar
+
+After filming one main video, you have **7 pieces of content** to distribute:
+
+| Day | YouTube | TikTok | Instagram | LinkedIn |
+|-----|---------|--------|-----------|----------|
+| **Monday (Day 1)** | Main Video + Topic Short 1 | Topic Short 1 | Topic Short 1 (Reel) | Topic Short 1 + Text Post 1 |
+| **Wednesday** | Topic Short 2 | Topic Short 2 | Topic Short 2 (Reel) | Topic Short 2 |
+| **Friday** | Topic Short 3 | Topic Short 3 | Topic Short 3 (Reel) | Topic Short 3 + Text Post 2 |
+| **Next Monday** | Extract Short 1 | Extract Short 1 | Extract Short 1 (Reel) | Extract Short 1 |
+| **Next Wednesday** | Extract Short 2 | Extract Short 2 | Extract Short 2 (Reel) | Extract Short 2 + Text Post 3 |
+| **Next Friday** | Extract Short 3 | Extract Short 3 | Extract Short 3 (Reel) | Extract Short 3 |
+
+---
+
+## Platform-Specific Notes
+
+### YouTube
+- Main video: Full description, tags, end screen, cards
+- Shorts: Post to YouTube Shorts naturally (under 60 seconds, vertical)
+
+### TikTok & Instagram Reels
+- **Same content as YouTube Shorts** — just repost
+- Remove any YouTube-specific CTAs (like "link in description")
+- Use platform-native captions/hashtags
+
+### LinkedIn (Multi-Format)
+
+LinkedIn gets the **most content variety**:
+
+| Content Type | Quantity | Schedule |
+|--------------|----------|----------|
+| **Video Shorts** | All 6 | Same schedule as YouTube |
+| **Text Posts** | 3 | Mon/Fri/Wed of Week 1 and Week 2 |
+| **Stories** | As available | Behind-the-scenes, teasers |
+
+#### LinkedIn Text Post Templates
+
+**Post 1: The Hook/Pain (Monday with main video)**
+```
+[Attention-grabbing first line about the problem]
+
+Here's what most people get wrong about [topic]:
+- [Mistake 1]
+- [Mistake 2]
+- [Mistake 3]
+
+I just dropped a full breakdown on this.
+
+[Link to main video]
+
+#YourHashtags
+```
+
+**Post 2: The Insight (Friday Week 1)**
+```
+💡 [Key insight from the video]
+
+[2-3 sentences expanding on the insight]
+
+This changed how I approach [topic].
+
+Full breakdown here: [Link]
+```
+
+**Post 3: The Result/CTA (Wednesday Week 2)**
+```
+[Result or outcome statement]
+
+If you're struggling with [pain point], this will help:
+→ [Key takeaway 1]
+→ [Key takeaway 2]
+→ [Key takeaway 3]
+
+Link to watch: [Link]
+```
+
+---
+
+## Step 1: Prepare Assets
+
+**Ask the user:**
+1. "Do you have all 6 Shorts exported in vertical (9:16) format?"
+2. "Is the main video fully uploaded and scheduled on YouTube?"
+3. "Do you have the LinkedIn text posts drafted?"
+
+**Checklist:**
+- [ ] Main video uploaded (YouTube)
+- [ ] 3x Topic Shorts exported
+- [ ] 3x Extract Shorts exported
+- [ ] 3x LinkedIn text posts written
+
+---
+
+## Step 2: Schedule Cross-Platform Posts
+
+**Recommended Tools:**
+- **Later** or **Buffer** for TikTok/Instagram scheduling
+- **LinkedIn native** for LinkedIn posts
+- **YouTube Studio** for Shorts scheduling
+
+**Or Manual:** Post at these times:
+- YouTube/TikTok/IG: Post at your peak audience time (check analytics)
+- LinkedIn: Best times are Tue-Thu, 8-10am or 12pm
+
+---
+
+## Step 3: Optional Bonus Content
+
+If time allows, capture these during filming:
+
+| Content | What It Is | Platform |
+|---------|------------|----------|
+| **Behind-the-scenes photo** | You filming, setup shot | LinkedIn, Instagram Stories |
+| **B-Roll clips** | 15-second "day in the life" | Instagram Stories, TikTok |
+| **Blooper reel** | Funny outtakes | TikTok, Instagram Reels |
+
+---
+
+## Step 4: Lock Phase 5 Output
+
+```
+📌 PHASE 5 OUTPUT: DISTRIBUTION COMPLETE
+
+Main Video: [YouTube URL]
+Shorts Posted:
+- [ ] Topic Short 1: YT / TikTok / IG / LinkedIn
+- [ ] Topic Short 2: YT / TikTok / IG / LinkedIn
+- [ ] Topic Short 3: YT / TikTok / IG / LinkedIn
+- [ ] Extract Short 1: YT / TikTok / IG / LinkedIn
+- [ ] Extract Short 2: YT / TikTok / IG / LinkedIn
+- [ ] Extract Short 3: YT / TikTok / IG / LinkedIn
+
+LinkedIn Text Posts:
+- [ ] Post 1 (Hook/Pain)
+- [ ] Post 2 (Insight)
+- [ ] Post 3 (Result/CTA)
+```
+
+---
+
+## Interaction Rules
+- **If user only wants YouTube:** "You're leaving views on the table. At minimum, repost Shorts to TikTok—it's literally the same file."
+- **If user doesn't use LinkedIn:** "Skip the text posts, but still post the Shorts there. LinkedIn video is underrated."
+- **If user is overwhelmed:** "Focus on YouTube + TikTok first. Add Instagram/LinkedIn once those are habit."

package/.agent/workflows/LEGACY/youtube-pipeline.md

@@ -0,0 +1,161 @@
+---
+description: Master orchestrator for the complete YouTube video pipeline. Chains through all 6 phases from ideation to distribution.
+---
+
+# YouTube Pipeline - Master Orchestrator
+
+> **Your Role**: You are the brutal expert YouTube strategist guiding the user through the entire video creation process. You manage state, track progress, and ensure no step is skipped.
+
+## How This Works
+This workflow chains through 6 phases:
+1. **Phase 1: Strategy Engine** - Find a mathematically proven topic (3-source validation)
+2. **Phase 2: Packaging Lab** - Engineer title & thumbnail
+3. **Phase 3: Scripting Forge** - Write a retention-optimized script
+4. **Phase 3.5: Shorts Bridge** - Create 6 Shorts (3 Topic + 3 Extract)
+5. **Phase 4: Production** - Film, edit, polish
+6. **Phase 5: Repurposing** - Distribute to all platforms
+
+You can start from Phase 1, or resume from any phase if you've already completed earlier ones.
+
+---
+
+## Entry Point
+
+Ask the user:
+"Where are we starting?
+1. **Fresh start** - Phase 1 (I have nothing yet)
+2. **I have a topic** - Phase 2 (Skip to packaging)
+3. **I have title & thumbnail** - Phase 3 (Skip to scripting)
+4. **I have a script** - Phase 4 (Skip to production)
+5. **Resume** - Pick up where we left off"
+
+---
+
+## State Tracking
+Maintain and display progress after each phase:
+
+```
+📊 PIPELINE STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Phase 1: Strategy      [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+Phase 2: Packaging     [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+Phase 3: Scripting     [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+Phase 3.5: Shorts      [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+Phase 4: Production    [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+Phase 5: Repurposing   [✅ COMPLETE / 🔄 IN PROGRESS / ⬜ NOT STARTED]
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+---
+
+## Phase Handoffs
+
+### After Phase 1 → Phase 2
+Confirm outputs before proceeding:
+```
+📌 PHASE 1 OUTPUT
+- Topic: [locked]
+- Format: [locked]
+- Outlier Link: [locked]
+- Market Gap: [locked]
+```
+Then invoke: `/youtube-phase2-packaging`
+
+### After Phase 2 → Phase 3
+Confirm outputs before proceeding:
+```
+📌 PHASE 2 OUTPUT
+- Title: [locked]
+- Thumbnail Concept: [locked]
+- Thumbnail Image: [generated/prompt provided]
+- Avatar: [locked]
+- Stakes: [locked]
+```
+Then invoke: `/youtube-phase3-scripting`
+
+### After Phase 3 → Phase 3.5
+Confirm outputs before proceeding:
+```
+📌 PHASE 3 OUTPUT
+- Full Script: [locked]
+- Hook: [locked]
+- Main Points: [locked]
+- Outro CTA: [locked]
+```
+
+Ask: "Do you want to extract Shorts from this video? (Phase 3.5)"
+- If yes → invoke: `/youtube-phase3.5-shorts`
+- If no → skip to Phase 4
+
+### After Phase 3.5 → Phase 4
+Confirm outputs before proceeding:
+```
+📌 PHASE 3.5 OUTPUT (6 SHORTS)
+- Topic Short 1 (Hot Take): Script
+- Topic Short 2 (Quick Win): Script
+- Topic Short 3 (Story Hook): Script
+- Extract Short 1 (Result): Timestamp + Hook + CTA
+- Extract Short 2 (Pain): Timestamp + Hook + CTA
+- Extract Short 3 (Value): Timestamp + Hook + CTA
+```
+Then invoke: `/youtube-phase4-production`
+
+### After Phase 4 → Phase 5
+Confirm outputs before proceeding:
+```
+📌 PHASE 4 OUTPUT
+- Main Video: [exported/uploaded]
+- 6 Shorts: [exported]
+- Thumbnail: [final]
+```
+Then invoke: `/youtube-phase5-repurposing`
+
+### After Phase 5 → Complete
+```
+📌 PIPELINE COMPLETE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+Main Video: [YouTube URL]
+Shorts: 6 posted (YouTube + TikTok + IG + LinkedIn)
+LinkedIn Posts: 3 published
+Status: FULLY DISTRIBUTED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+---
+
+## Phase Workflow References
+Each phase has its own detailed workflow:
+- Phase 1: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase1-strategy.md`
+- Phase 2: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase2-packaging.md`
+- Phase 3: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase3-scripting.md`
+- Phase 3.5: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase3.5-shorts.md`
+- Phase 4: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase4-production.md`
+- Phase 5: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\.agent\workflows\youtube-phase5-repurposing.md`
+
+Each workflow also reads from source knowledge:
+- Source 1: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Phase 1.md`
+- Source 2: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Phase 2.md`
+- Source 3: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Phase 3.md`
+- Source 4: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Phase 4.md`
+- Research: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Research.md`
+- Repurposing: `c:\CreativeOS\Creator_Command_Hub_Obsidian\📁 YouTube Brain\📂 Processed_Notes\Workflow\Repurposing.md`
+
+---
+
+## Interaction Mode Selection
+At start, ask:
+"How do you want to work?
+- **Guided** (default): I generate everything, you pick and refine
+- **Manual**: You do the work, I critique ruthlessly"
+
+User can switch modes at any step.
+
+---
+
+## Rules for the Brutal Expert
+- Never yes-man. Weak ideas get called out.
+- Demand proof for "viral" claims.
+- Teach the "why" behind every step.
+- Generate outputs for user to pick from.
+- Never let user skip steps without justification.
+- Track state across phases. Don't lose context.

package/.agent/workflows/README.md

@@ -0,0 +1,349 @@
+---
+description: A Detailed Explanation of what the vibe code protocol is
+---
+
+# VibeCode Workflow Guide
+
+This document explains how all workflows in `.agent/workflows/` relate to each other, which ones are "parent" workflows, and the recommended order of operations.
+
+---
+
+## Workflow Hierarchy
+
+```
+┌──────────────────────────────────────────────────────────────────────────────┐
+│                           PROJECT LIFECYCLE                                   │
+├──────────────────────────────────────────────────────────────────────────────┤
+│                                                                              │
+│  ┌─────────────────────────────────────────────────────────────────────────┐ │
+│  │  🧠 /VIBE-ORCHESTRATOR — THE BRAIN (Autonomous Mode)                    │ │
+│  │  Understands all workflows. Spawns sub-agents. Builds full projects.    │ │
+│  └─────────────────────────────────────────────────────────────────────────┘ │
+│                              │                                               │
+│              ┌───────────────┴───────────────┐                               │
+│              ▼                               ▼                               │
+│  NEW PROJECT                         EXISTING PROJECT                        │
+│       │                                    │                                 │
+│       ▼                                    ▼                                 │
+│  /init_vibecode_genesis ──────────►  /reverse_genesis                        │
+│       │                                    │                                 │
+│       ▼                                    │                                 │
+│  /init_vibecode_design                     │                                 │
+│       │                                    │                                 │
+│       ▼                                    │                                 │
+│  /build_vibecode_project ◄─────────────────┘                                 │
+│       │                                                                      │
+│       ├───► /init_smart_ops (bootstraps smart_start/complete)                │
+│       │                                                                      │
+│       ├───► /spawn-jstar-code-review (adds J-Star Reviewer)                  │
+│       │                                                                      │
+│       ▼                                                                      │
+│  ┌────────────────────────────────────────────────────────────────────────┐  │
+│  │                      DAILY DEVELOPMENT LOOP                             │  │
+│  │  ┌──────────────────────────────────────────────────────────────────┐  │  │
+│  │  │ /prime_agent ──► /smart_start ──► WORK ──► /smart_complete       │  │  │
+│  │  └──────────────────────────────────────────────────────────────────┘  │  │
+│  │                            │                                            │  │
+│  │                            ▼                                            │  │
+│  │           /spawn_task (for complex features)                            │  │
+│  │           /analyze_component (for refactoring)                          │  │
+│  │           /review_code (for quality gates)                              │  │
+│  │           /sync_docs (keep docs updated)                                │  │
+│  └────────────────────────────────────────────────────────────────────────┘  │
+│                                                                              │
+│  PARALLEL DEVELOPMENT             QUALITY ASSURANCE                          │
+│       │                                 │                                    │
+│       ▼                                 ▼                                    │
+│  /git_worktree ◄──────────────►  /deep_code_audit                            │
+│       │                                 │                                    │
+│       ▼                                 ▼                                    │
+│  /vibe-orchestrator ◄─────────►  /review_code                                │
+│                                                                              │
+│  WHEN STUCK                       WHEN CHAT GETS STALE                       │
+│       │                                 │                                    │
+│       ▼                                 ▼                                    │
+│  /escalate                         /migrate                                  │
+│                                                                              │
+└──────────────────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Workflow Categories
+
+### 🏗️ Project Initialization (Run Once)
+
+| Workflow | Purpose | When to Use | Generates |
+|----------|---------|-------------|-----------|
+| `/init_vibecode_genesis` | The Architect — Plans a new project | Starting a brand new project | `docs/Project_Requirements.md`, `docs/Coding_Guidelines.md`, `docs/Builder_Prompt.md`, GitHub Issues |
+| `/init_vibecode_design` | The Designer — Creates visual system | After Genesis, before Build | `docs/design/design-system.html`, `docs/mockups/*.html` |
+| `/build_vibecode_project` | The Builder — Scaffolds and builds | After Genesis (and optionally Design) | Project structure, MUS features, `docs/Builder_Handoff_Report.md` |
+| `/build_vibecode_project_v2` | The Builder v2 — pnpm + PowerShell safe | Same as above, Windows-optimized | Same as above |
+| `/init_smart_ops` | Bootstraps GitHub integration | After Build, when project has `src/` | `src/scripts/smart-ops.ts`, `smart_start.md`, `smart_complete.md` |
+| `/reverse_genesis` | Onboards to existing codebase | Joining an existing project | `docs/autopsy_report.md` |
+| `/spawn-jstar-code-review` | Adds J-Star Reviewer to project | Any project needing code review | `.jstar/` directory, `.env.example` |
+
+### 🔄 Daily Development (Run Often)
+
+| Workflow | Purpose | When to Use |
+|----------|---------|-------------|
+| `/prime_agent` | Load project context | Start of session, before complex work |
+| `/smart_start` | Start work on a feature/bug | Beginning any task |
+| `/smart_complete` | Mark work as done | Finishing any task |
+| `/spawn_task` | Create detailed task prompt | Complex features needing breakdown |
+| `/analyze_component` | Audit component quality | Refactoring, code review |
+| `/sync_docs` | Update feature documentation | After completing code changes |
+
+### 🔍 Code Quality & Review
+
+| Workflow | Purpose | When to Use |
+|----------|---------|-------------|
+| `/review_code` | Run J-Star review loop | Before commits, quality gates |
+| `/deep_code_audit` | Manual security & logic audit | Major releases, security review |
+| `/Vercel Ai SDK` | Learn AI SDK patterns | Building AI-powered features |
+
+### 🔀 Parallel Development (Multi-Agent)
+
+| Workflow | Purpose | When to Use |
+|----------|---------|-------------|
+| `/git_worktree` | Manage isolated dev environments | Multiple agents on same repo |
+| `/vibe-orchestrator` | **The Brain** — Autonomous full project builds | Kilo Code, automated pipelines |
+| `/multi_agent_strategy` | Architecture docs for multi-agent | Planning parallel execution |
+
+### 🆘 Recovery & Migration
+
+| Workflow | Purpose | When to Use |
+|----------|---------|-------------|
+| `/escalate` | Generate handoff report | Agent is stuck, need fresh perspective |
+| `/migrate` | Transfer context to new chat | Chat is stale, losing context |
+
+---
+
+## Recommended Flows
+
+### Flow 1: New Project (Full VibeCode)
+
+```
+1. /init_vibecode_genesis    → Get PRD, Guidelines, Issues
+2. /init_vibecode_design     → Get design system, mockups (UI projects)
+3. /build_vibecode_project   → Scaffold and build MUS
+4. /spawn-jstar-code-review  → Add code review tooling
+5. /init_smart_ops           → Set up GitHub automation
+6. /prime_agent              → Start daily work loop
+```
+
+### Flow 2: Joining Existing Project
+
+```
+1. /reverse_genesis          → Generate autopsy report
+2. /prime_agent              → Load coding/styling context
+3. /smart_start              → Pick up first task
+```
+
+### Flow 3: Daily Work Session
+
+```
+1. /prime_agent              → (Optional) Refresh context
+2. /smart_start              → Declare what you're working on
+3. ... do the work ...
+4. /review_code              → Check code quality before commit
+5. /smart_complete           → Close out the task
+```
+
+### Flow 4: Complex Feature Implementation
+
+```
+1. /spawn_task               → Generate detailed task prompt
+2. /smart_start              → Link to GitHub issue
+3. ... implement phases ...
+4. /analyze_component        → Audit any large components
+5. /review_code              → Quality gate before merge
+6. /sync_docs                → Update feature documentation
+7. /smart_complete           → Mark as done
+```
+
+### Flow 5: Agent Recovery
+
+```
+# If agent is stuck:
+/escalate                    → Generate damage report for fresh agent
+
+# If chat is stale:
+/migrate                     → Generate state snapshot for new session
+```
+
+### Flow 6: Code Review Loop (Quality Gate)
+
+```
+1. git add .                 → Stage changes
+2. /review_code              → Run J-Star review
+3. Fix P0/P1 issues          → Address critical findings
+4. Repeat until clean        → Max 3 loops
+5. Commit                    → Code is ready
+```
+
+### Flow 7: Deep Security Audit
+
+```
+1. /deep_code_audit          → Full manual audit
+2. Define scope (FULL/FEATURE/DIFF)
+3. Phase 1: Static analysis (Detective)
+4. Phase 2: Data flow tracing (Graph)
+5. Phase 3: Spec vs Code (Auditor)
+6. Phase 4: Logic probing (Judge)
+7. Phase 5: Quality checks (Architect)
+8. Generate report → .jstar/audit_report.md
+9. Fix CRITICAL/HIGH issues
+```
+
+### Flow 8: Parallel Development (Multi-Agent)
+
+```
+1. /git_worktree             → Choose [NEW] to create agent environment
+2. Name the agent            → e.g., "feat-auth", "agent-2"
+3. Copy .env + DB            → Migrate context to worktree
+4. pnpm install              → Bootstrap dependencies
+5. Work in isolation         → Each agent has own directory
+6. /review_code              → Quality check in worktree
+7. Merge to main             → Via PR or direct merge
+8. /git_worktree             → Choose [KILL] to teardown
+```
+
+### Flow 9: Documentation Sync
+
+```
+1. Complete code changes     → Feature/fix is done
+2. /sync_docs                → Identify impacted docs
+3. UPDATE or CREATE          → Modify existing or add new doc
+4. Follow template           → Consistent structure
+5. Verify file paths         → Ensure links work
+```
+
+---
+
+## Parent-Child Relationships
+
+### `/init_vibecode_genesis` is Parent of:
+- `/init_vibecode_design` (uses the PRD)
+- `/build_vibecode_project` (uses PRD, Guidelines, Builder Prompt)
+
+### `/build_vibecode_project` is Parent of:
+- `/init_smart_ops` (needs `src/` to exist)
+- `/spawn-jstar-code-review` (needs project structure)
+
+### `/init_smart_ops` Generates:
+- `/smart_start` (the actual workflow used daily)
+- `/smart_complete` (the actual workflow used daily)
+
+### `/spawn-jstar-code-review` Enables:
+- `/review_code` (requires J-Star to be set up)
+
+### `/git_worktree` Enables:
+- `/multi_agent_strategy` (parallel execution depends on isolation)
+
+### Standalone (No Parent):
+- `/prime_agent` — Can run anytime
+- `/analyze_component` — Can run anytime
+- `/spawn_task` — Can run anytime
+- `/deep_code_audit` — Can run anytime
+- `/sync_docs` — Can run anytime
+- `/escalate` — Run when stuck
+- `/migrate` — Run when chat stale
+- `/reverse_genesis` — Alternative to Genesis for existing projects
+- `/Vercel Ai SDK` — Reference documentation
+
+---
+
+## Stack-Specific Notes
+
+### Universal Shell Script (All Stacks)
+The Smart Ops system now uses a **universal shell script** (`scripts/smart-ops.sh`) that works with ANY project stack:
+
+| Stack | Works? | Notes |
+|-------|--------|-------|
+| Node.js/TypeScript | ✅ | Shell script runs in any terminal |
+| Python | ✅ | Shell script works |
+| Rust | ✅ | Shell script works |
+| Go | ✅ | Shell script works |
+| Any Unix/Linux/macOS | ✅ | Native bash |
+| Windows | ✅ | Git Bash, WSL, or PowerShell with bash |
+
+### J-Star Code Reviewer (All Languages)
+The J-Star Reviewer works with **any programming language**:
+
+| Language | Works? | Notes |
+|----------|--------|-------|
+| TypeScript/JavaScript | ✅ | Full support |
+| Python | ✅ | Full support |
+| Rust | ✅ | Full support |
+| Go | ✅ | Full support |
+| Any other | ✅ | Uses Gemini for analysis |
+
+---
+
+## Timeline Tracking (GitHub Projects)
+
+The Smart Ops system supports **timeline tracking** for GitHub Projects:
+
+### Features:
+- **Start Date** — Automatically set when moving to "In Progress"
+- **Target Date** — Set when creating issues (based on estimate)
+- **Duration Tracking** — Calculate actual vs estimated time on completion
+- **Timeline View** — View in GitHub Projects Roadmap/Timeline
+
+### Setup:
+1. In your GitHub Project, create these fields:
+   - "Start Date" (Date type)
+   - "Target Date" (Date type)
+2. Run `/init_smart_ops` to detect field IDs
+3. The script will auto-populate dates
+
+### Workflow:
+```
+/smart_start → "How long will this take?" → Sets target date
+... work ...
+/smart_complete → Calculates actual duration → Reports variance
+```
+
+### Commands:
+```bash
+# Create issue with 7-day estimate
+./scripts/smart-ops.sh create "Fix login" "Description" "bug" 7
+
+# Set target date manually
+./scripts/smart-ops.sh target <item_id> 14           # 14 days from now
+./scripts/smart-ops.sh target <item_id> 2024-12-25   # Specific date
+
+# Set start date
+./scripts/smart-ops.sh started <item_id>              # Today
+./scripts/smart-ops.sh started <item_id> 2024-12-10  # Specific date
+```
+
+---
+
+## Quick Reference
+
+| I want to... | Use this workflow |
+|--------------|-------------------|
+| Start a new project | `/init_vibecode_genesis` |
+| Design the UI | `/init_vibecode_design` |
+| Build the foundation | `/build_vibecode_project` |
+| Add code review tooling | `/spawn-jstar-code-review` |
+| Set up GitHub automation | `/init_smart_ops` |
+| Join an existing project | `/reverse_genesis` |
+| Brief the agent on rules | `/prime_agent` |
+| Start a work session | `/smart_start` |
+| End a work session | `/smart_complete` |
+| Break down a complex feature | `/spawn_task` |
+| Audit a component | `/analyze_component` |
+| Run code review | `/review_code` |
+| Deep security audit | `/deep_code_audit` |
+| Update documentation | `/sync_docs` |
+| Set up parallel agents | `/git_worktree` |
+| **Build full project autonomously** | `/vibe-orchestrator` |
+| Plan multi-agent architecture | `/multi_agent_strategy` |
+| Hand off to fresh agent | `/escalate` |
+| Move to new chat | `/migrate` |
+| Learn AI SDK patterns | `/Vercel Ai SDK` |
+| Set issue target date | `./scripts/smart-ops.sh target` |
+| Track work duration | `/smart_complete` (auto) |