Help me brainstorm about: $ARGUMENTS

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read mission-control/data/brain-dump.json to see existing ideas
3. Read mission-control/data/projects.json to understand active projects
4. Generate 10-15 creative ideas related to the topic
5. Ask me which ones I want to keep
6. Add the selected ideas to brain-dump.json with appropriate tags

Be creative and think from multiple angles: technical, marketing, user experience, business model, partnerships, and unconventional approaches.

You are acting as a Business Analyst and Strategist advising a solo software entrepreneur.

Analysis task: $ARGUMENTS

Before starting:

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read mission-control/data/projects.json to understand current projects
3. Read mission-control/data/goals.json to understand priorities
4. Read mission-control/data/tasks.json for workload context
5. Check docs/ for existing business plans and strategies

Capabilities:

• Market sizing and opportunity analysis
• Feature prioritization (RICE, ICE, or similar frameworks)
• Business model evaluation
• Revenue and growth projections
• Build vs. buy decisions
• Time allocation recommendations

Always ground recommendations in data and the solo entrepreneur context. Focus on highest-leverage activities. One person cannot do everything — help identify what to focus on and what to defer or eliminate.

Save analysis outputs to docs/ with a descriptive filename.

Create my daily plan:

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read mission-control/data/tasks.json
3. Read mission-control/data/brain-dump.json for items needing triage
4. Read mission-control/data/goals.json for upcoming milestone deadlines

Produce a focused plan:

Top 3 Priorities Today

[Important+Urgent tasks first, then Important+Not-Urgent tasks]

Brain Dump Triage

[List unprocessed brain dump items and suggest: convert to task, archive, or delete]

Time Blocks (suggested)

• Morning (high energy): [Deep work tasks]
• Afternoon: [Meetings, communication, lighter tasks]
• Evening (if working): [Planning, research, learning]

Quick Wins

[Not-Important+Urgent items that take <15 min]

Keep the plan realistic for one person. Suggest no more than 5-6 tasks total.

You are acting as a Growth Marketing Specialist for a bootstrapped software business.

Marketing task: $ARGUMENTS

Before starting:

1. Read mission-control/data/ai-context.md for current project context
2. Read mission-control/data/projects.json to understand active projects

Capabilities you should apply:

• Write compelling copy for landing pages, emails, and social media
• Analyze positioning and messaging
• Suggest growth experiments
• Create content outlines for blog posts and documentation
• Review and improve existing marketing materials

Always consider:

• Solo entrepreneur constraints (no big ad budget)
• Focus on organic/content marketing and product-led growth
• Clear, benefit-driven messaging
• Strong calls to action
• SEO best practices

Save any marketing materials to docs/ with a descriptive filename.

Plan the following feature: $ARGUMENTS

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read the relevant project's CLAUDE.md and codebase structure
3. Read mission-control/data/goals.json to understand which goal this supports
4. Break the feature into implementation tasks (5-15 tasks)
5. For each task, determine importance and urgency
6. Create a new milestone in goals.json linked to the appropriate goal
7. Add all tasks to tasks.json with:
   • Proper importance/urgency classification
   • kanban: "not-started"
   • Link to the new milestone and project
   • Appropriate assignedTo agent role
   • 2-4 daily actions per task
8. Present the plan as a summary before saving
9. After saving, run pnpm gen:context in mission-control/ to update the AI context

Ask me clarifying questions before starting if the feature description is ambiguous.

Research the following topic thoroughly: $ARGUMENTS

1. Read mission-control/data/ai-context.md for current project context
2. Search the web for current information on this topic
3. Synthesize findings into a structured markdown document
4. Save the document to research/ with a descriptive filename
5. Include: Summary, Key Findings, Sources, Recommendations, and Next Steps

Focus on actionable insights relevant to a solo entrepreneur building software products.

You are acting as a Research Analyst. Your role is to investigate topics thoroughly and produce actionable insights for a solo software entrepreneur.

Topic to research: $ARGUMENTS

Steps:

1. Read mission-control/data/ai-context.md for current project context
2. Search the web for the most current information on this topic
3. Cross-reference multiple sources for accuracy
4. Focus on practical, actionable findings
5. Consider the solo entrepreneur context (limited time, limited budget, need for leverage)

Save your findings to the research/ directory as a markdown file with a descriptive name.

Format your output as:

Executive Summary

[3-5 sentences]

Key Findings

• [Bulleted list]

Opportunities

• [What can be acted on]

Risks

• [What to watch out for]

Recommended Next Steps

• [Actionable items]

Sources

• [Links and references]

Ship the feature: $ARGUMENTS

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read relevant task and milestone from mission-control/data/
3. Run the test suite and fix any failures
4. Run typecheck (pnpm tsc --noEmit) and fix errors
5. Run lint (pnpm lint) and fix issues
6. Create a git commit with a descriptive message
7. Update task status to "done" in mission-control/data/tasks.json
8. Update milestone progress in goals.json
9. Run pnpm gen:context in mission-control/ to regenerate the AI context
10. Report what was shipped and any remaining work

IMPORTANT: Do not skip any verification step. Every step must pass before shipping.

Generate my daily standup by doing the following:

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read mission-control/data/tasks.json and find tasks with kanban "in-progress"
3. Run git log --oneline --since="yesterday" --all across all project directories
4. Read mission-control/data/goals.json to check milestone progress

Format the output as:

Yesterday

• [List completed work from git commits]

Today

• [List in-progress tasks and their next daily actions]

Blockers

• [Any tasks marked important+urgent that have been in-progress for more than 3 days]

Goal Progress

• [Summary of milestone completion percentages]

Conduct my weekly review:

1. Read mission-control/data/ai-context.md for a quick snapshot of current state
2. Read all data files in mission-control/data/
3. Run git log --oneline --since="7 days ago" --all for all projects
4. Analyze task completion rates and goal progress

Report Format:

Accomplishments This Week

• Tasks completed (list them)
• Git commits summary by project

Goal Progress

• Each active milestone with % complete and trajectory

Eisenhower Matrix Health

• How many tasks in each quadrant?
• Are Important+Not-Urgent tasks getting attention or being neglected?

Stale Items

• Tasks that have been "in-progress" for more than a week
• Brain dump items older than 2 weeks

Recommendations for Next Week

• Top 3 priorities based on goal deadlines and importance
• Suggestions for tasks to delegate, eliminate, or reschedule

Agentic Company Operations

Philosophy

The owner acts as CEO. AI agents handle most execution work. The human focuses on: decisions, approvals, creative direction, and strategic thinking. Goal: maximize time freedom while building multiple income streams.

Agent Team

Task Assignment Rules

1. If the task requires writing or modifying code → developer
2. If the task requires investigation or data gathering → researcher
3. If the task involves marketing copy, content, or growth → marketer
4. If the task involves strategy, numbers, or planning → business-analyst
5. If the task requires a human decision or approval → me
6. If unclear, pick the agent whose description best matches the work

Daily Operations Workflow

1. Morning: Run /daily-plan to review priorities and triage brain dump
2. During work: Agents execute assigned tasks, update kanban status to "in-progress"
3. On completion: Update kanban to "done", set completedAt, run pnpm gen:context
4. End of day: Run /standup to log progress
5. Weekly: Run /weekly-review to assess goal progress and velocity

Scaling the Team

Future agent roles to consider:

• Legal Advisor — contracts, compliance, IP
• Creative Director — design, branding, visual identity
• Customer Support — user communication, feedback handling
• Data Engineer — data pipelines, analytics, monitoring

Eisenhower Matrix Triage

Quadrant Definitions

Triage Rules

1. New tasks default to SCHEDULE unless there is a deadline within 48 hours
2. DELEGATE quadrant tasks should always have assignedTo set to an agent role
3. Never let SCHEDULE accumulate >10 unstarted tasks without review
4. Brain dump items should be triaged into tasks with proper quadrant placement
5. Review the DO quadrant daily — nothing should sit here unstarted for >2 days

Priority Order Within Quadrants

1. DO → by urgency deadline, then by creation date
2. SCHEDULE → by importance to long-term goals, then by milestone deadline
3. DELEGATE → by agent availability, then by urgency
4. ELIMINATE → review weekly, remove or reclassify

Brain Dump Triage Flow

1. Read each unprocessed entry
2. Decide: Is this actionable? → If yes, create a task with importance/urgency
3. Set processed: true on the brain dump entry
4. Set convertedTo: "task_{id}" if converted, or null if archived

Task Management in Mission Control

All data lives in mission-control/data/ as JSON files. Read and write these directly.

Quick Reference

• AI Context: mission-control/data/ai-context.md (read this FIRST for a snapshot)
• Tasks: mission-control/data/tasks.json
• Goals: mission-control/data/goals.json
• Projects: mission-control/data/projects.json
• Brain Dump: mission-control/data/brain-dump.json

Creating a Task

Required fields: id, title, description, importance, urgency, kanban, assignedTo

{
  "id": "task_{Date.now()}",
  "title": "Action-oriented title",
  "description": "What needs to be done",
  "importance": "important",
  "urgency": "urgent",
  "kanban": "not-started",
  "projectId": "proj_001",
  "milestoneId": "mile_001",
  "assignedTo": "developer",
  "dailyActions": [],
  "tags": ["tag1"],
  "notes": "",
  "createdAt": "ISO-8601",
  "updatedAt": "ISO-8601",
  "completedAt": null
}

Updating a Task

• Always update updatedAt to current ISO timestamp
• When kanban becomes "done": set completedAt to current ISO timestamp
• When kanban changes from "done": set completedAt to null

Agent Assignment Rules

• Code/implementation tasks → "developer"
• Research/analysis tasks → "researcher"
• Marketing/content tasks → "marketer"
• Strategy/planning tasks → "business-analyst"
• Decisions/approvals → "me"

After Any Data Modification

Run pnpm gen:context in mission-control/ to regenerate ai-context.md