feat(project): add initial scaffold, CI, and README
This commit is contained in:
nexusct (Blackbox Agent)
157
strategy/runbooks/scenario-enterprise-feature.md
Normal file
157
strategy/runbooks/scenario-enterprise-feature.md
Normal file
@@ -0,0 +1,157 @@
|
||||
# 🏢 Runbook: Enterprise Feature Development
|
||||
|
||||
> **Mode**: NEXUS-Sprint | **Duration**: 6-12 weeks | **Agents**: 20-30
|
||||
|
||||
---
|
||||
|
||||
## Scenario
|
||||
|
||||
You're adding a major feature to an existing enterprise product. Compliance, security, and quality gates are non-negotiable. Multiple stakeholders need alignment. The feature must integrate seamlessly with existing systems.
|
||||
|
||||
## Agent Roster
|
||||
|
||||
### Core Team
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Agents Orchestrator | Pipeline controller |
|
||||
| Project Shepherd | Cross-functional coordination |
|
||||
| Senior Project Manager | Spec-to-task conversion |
|
||||
| Sprint Prioritizer | Backlog management |
|
||||
| UX Architect | Technical foundation |
|
||||
| UX Researcher | User validation |
|
||||
| UI Designer | Component design |
|
||||
| Frontend Developer | UI implementation |
|
||||
| Backend Architect | API and system integration |
|
||||
| Senior Developer | Complex implementation |
|
||||
| DevOps Automator | CI/CD and deployment |
|
||||
| Evidence Collector | Visual QA |
|
||||
| API Tester | Endpoint validation |
|
||||
| Reality Checker | Final quality gate |
|
||||
| Performance Benchmarker | Load testing |
|
||||
|
||||
### Compliance & Governance
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Legal Compliance Checker | Regulatory compliance |
|
||||
| Brand Guardian | Brand consistency |
|
||||
| Finance Tracker | Budget tracking |
|
||||
| Executive Summary Generator | Stakeholder reporting |
|
||||
|
||||
### Quality Assurance
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Test Results Analyzer | Quality metrics |
|
||||
| Workflow Optimizer | Process improvement |
|
||||
| Experiment Tracker | A/B testing |
|
||||
|
||||
## Execution Plan
|
||||
|
||||
### Phase 1: Requirements & Architecture (Week 1-2)
|
||||
|
||||
```
|
||||
Week 1: Stakeholder Alignment
|
||||
├── Project Shepherd → Stakeholder analysis + communication plan
|
||||
├── UX Researcher → User research on feature need
|
||||
├── Legal Compliance Checker → Compliance requirements scan
|
||||
├── Senior Project Manager → Spec-to-task conversion
|
||||
└── Finance Tracker → Budget framework
|
||||
|
||||
Week 2: Technical Architecture
|
||||
├── UX Architect → UX foundation + component architecture
|
||||
├── Backend Architect → System architecture + integration plan
|
||||
├── UI Designer → Component design + design system updates
|
||||
├── Sprint Prioritizer → RICE-scored backlog
|
||||
├── Brand Guardian → Brand impact assessment
|
||||
└── Quality Gate: Architecture Review (Project Shepherd + Reality Checker)
|
||||
```
|
||||
|
||||
### Phase 2: Foundation (Week 3)
|
||||
|
||||
```
|
||||
├── DevOps Automator → Feature branch pipeline + feature flags
|
||||
├── Frontend Developer → Component scaffolding
|
||||
├── Backend Architect → API scaffold + database migrations
|
||||
├── Infrastructure Maintainer → Staging environment setup
|
||||
└── Quality Gate: Foundation verified (Evidence Collector)
|
||||
```
|
||||
|
||||
### Phase 3: Build (Week 4-9)
|
||||
|
||||
```
|
||||
Sprint 1-3 (Week 4-9):
|
||||
├── Agents Orchestrator → Dev↔QA loop management
|
||||
├── Frontend Developer → UI implementation (task by task)
|
||||
├── Backend Architect → API implementation (task by task)
|
||||
├── Senior Developer → Complex/premium features
|
||||
├── Evidence Collector → QA every task (screenshots)
|
||||
├── API Tester → Endpoint validation every API task
|
||||
├── Experiment Tracker → A/B test setup for key features
|
||||
│
|
||||
├── Bi-weekly:
|
||||
│ ├── Project Shepherd → Stakeholder status update
|
||||
│ ├── Executive Summary Generator → Executive briefing
|
||||
│ └── Finance Tracker → Budget tracking
|
||||
│
|
||||
└── Sprint Reviews with stakeholder demos
|
||||
```
|
||||
|
||||
### Phase 4: Hardening (Week 10-11)
|
||||
|
||||
```
|
||||
Week 10: Evidence Collection
|
||||
├── Evidence Collector → Full screenshot suite
|
||||
├── API Tester → Complete regression suite
|
||||
├── Performance Benchmarker → Load test at 10x traffic
|
||||
├── Legal Compliance Checker → Final compliance audit
|
||||
├── Test Results Analyzer → Quality metrics dashboard
|
||||
└── Infrastructure Maintainer → Production readiness
|
||||
|
||||
Week 11: Final Judgment
|
||||
├── Reality Checker → Integration testing (default: NEEDS WORK)
|
||||
├── Fix cycle if needed (2-3 days)
|
||||
├── Re-verification
|
||||
└── Executive Summary Generator → Go/No-Go recommendation
|
||||
```
|
||||
|
||||
### Phase 5: Rollout (Week 12)
|
||||
|
||||
```
|
||||
├── DevOps Automator → Canary deployment (5% → 25% → 100%)
|
||||
├── Infrastructure Maintainer → Real-time monitoring
|
||||
├── Analytics Reporter → Feature adoption tracking
|
||||
├── Support Responder → User support for new feature
|
||||
├── Feedback Synthesizer → Early feedback collection
|
||||
└── Executive Summary Generator → Launch report
|
||||
```
|
||||
|
||||
## Stakeholder Communication Cadence
|
||||
|
||||
| Audience | Frequency | Agent | Format |
|
||||
|----------|-----------|-------|--------|
|
||||
| Executive sponsors | Bi-weekly | Executive Summary Generator | SCQA summary (≤500 words) |
|
||||
| Product team | Weekly | Project Shepherd | Status report |
|
||||
| Engineering team | Daily | Agents Orchestrator | Pipeline status |
|
||||
| Compliance team | Monthly | Legal Compliance Checker | Compliance status |
|
||||
| Finance | Monthly | Finance Tracker | Budget report |
|
||||
|
||||
## Quality Requirements
|
||||
|
||||
| Requirement | Threshold | Verification |
|
||||
|-------------|-----------|-------------|
|
||||
| Code coverage | > 80% | Test Results Analyzer |
|
||||
| API response time | P95 < 200ms | Performance Benchmarker |
|
||||
| Accessibility | WCAG 2.1 AA | Evidence Collector |
|
||||
| Security | Zero critical vulnerabilities | Legal Compliance Checker |
|
||||
| Brand consistency | 95%+ adherence | Brand Guardian |
|
||||
| Spec compliance | 100% | Reality Checker |
|
||||
| Load handling | 10x current traffic | Performance Benchmarker |
|
||||
|
||||
## Risk Management
|
||||
|
||||
| Risk | Probability | Impact | Mitigation | Owner |
|
||||
|------|------------|--------|-----------|-------|
|
||||
| Integration complexity | High | High | Early integration testing, API Tester in every sprint | Backend Architect |
|
||||
| Scope creep | Medium | High | Sprint Prioritizer enforces MoSCoW, Project Shepherd manages changes | Sprint Prioritizer |
|
||||
| Compliance issues | Medium | Critical | Legal Compliance Checker involved from Day 1 | Legal Compliance Checker |
|
||||
| Performance regression | Medium | High | Performance Benchmarker tests every sprint | Performance Benchmarker |
|
||||
| Stakeholder misalignment | Low | High | Bi-weekly executive briefings, Project Shepherd coordination | Project Shepherd |
|
||||
217
strategy/runbooks/scenario-incident-response.md
Normal file
217
strategy/runbooks/scenario-incident-response.md
Normal file
@@ -0,0 +1,217 @@
|
||||
# 🚨 Runbook: Incident Response
|
||||
|
||||
> **Mode**: NEXUS-Micro | **Duration**: Minutes to hours | **Agents**: 3-8
|
||||
|
||||
---
|
||||
|
||||
## Scenario
|
||||
|
||||
Something is broken in production. Users are affected. Speed of response matters, but so does doing it right. This runbook covers detection through post-mortem.
|
||||
|
||||
## Severity Classification
|
||||
|
||||
| Level | Definition | Examples | Response Time |
|
||||
|-------|-----------|----------|--------------|
|
||||
| **P0 — Critical** | Service completely down, data loss, security breach | Database corruption, DDoS attack, auth system failure | Immediate (all hands) |
|
||||
| **P1 — High** | Major feature broken, significant performance degradation | Payment processing down, 50%+ error rate, 10x latency | < 1 hour |
|
||||
| **P2 — Medium** | Minor feature broken, workaround available | Search not working, non-critical API errors | < 4 hours |
|
||||
| **P3 — Low** | Cosmetic issue, minor inconvenience | Styling bug, typo, minor UI glitch | Next sprint |
|
||||
|
||||
## Response Teams by Severity
|
||||
|
||||
### P0 — Critical Response Team
|
||||
| Agent | Role | Action |
|
||||
|-------|------|--------|
|
||||
| **Infrastructure Maintainer** | Incident commander | Assess scope, coordinate response |
|
||||
| **DevOps Automator** | Deployment/rollback | Execute rollback if needed |
|
||||
| **Backend Architect** | Root cause investigation | Diagnose system issues |
|
||||
| **Frontend Developer** | UI-side investigation | Diagnose client-side issues |
|
||||
| **Support Responder** | User communication | Status page updates, user notifications |
|
||||
| **Executive Summary Generator** | Stakeholder communication | Real-time executive updates |
|
||||
|
||||
### P1 — High Response Team
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| **Infrastructure Maintainer** | Incident commander |
|
||||
| **DevOps Automator** | Deployment support |
|
||||
| **Relevant Developer Agent** | Fix implementation |
|
||||
| **Support Responder** | User communication |
|
||||
|
||||
### P2 — Medium Response
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| **Relevant Developer Agent** | Fix implementation |
|
||||
| **Evidence Collector** | Verify fix |
|
||||
|
||||
### P3 — Low Response
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| **Sprint Prioritizer** | Add to backlog |
|
||||
|
||||
## Incident Response Sequence
|
||||
|
||||
### Step 1: Detection & Triage (0-5 minutes)
|
||||
|
||||
```
|
||||
TRIGGER: Alert from monitoring / User report / Agent detection
|
||||
|
||||
Infrastructure Maintainer:
|
||||
1. Acknowledge alert
|
||||
2. Assess scope and impact
|
||||
- How many users affected?
|
||||
- Which services are impacted?
|
||||
- Is data at risk?
|
||||
3. Classify severity (P0/P1/P2/P3)
|
||||
4. Activate appropriate response team
|
||||
5. Create incident channel/thread
|
||||
|
||||
Output: Incident classification + response team activated
|
||||
```
|
||||
|
||||
### Step 2: Investigation (5-30 minutes)
|
||||
|
||||
```
|
||||
PARALLEL INVESTIGATION:
|
||||
|
||||
Infrastructure Maintainer:
|
||||
├── Check system metrics (CPU, memory, network, disk)
|
||||
├── Review error logs
|
||||
├── Check recent deployments
|
||||
└── Verify external dependencies
|
||||
|
||||
Backend Architect (if P0/P1):
|
||||
├── Check database health
|
||||
├── Review API error rates
|
||||
├── Check service communication
|
||||
└── Identify failing component
|
||||
|
||||
DevOps Automator:
|
||||
├── Review recent deployment history
|
||||
├── Check CI/CD pipeline status
|
||||
├── Prepare rollback if needed
|
||||
└── Verify infrastructure state
|
||||
|
||||
Output: Root cause identified (or narrowed to component)
|
||||
```
|
||||
|
||||
### Step 3: Mitigation (15-60 minutes)
|
||||
|
||||
```
|
||||
DECISION TREE:
|
||||
|
||||
IF caused by recent deployment:
|
||||
→ DevOps Automator: Execute rollback
|
||||
→ Infrastructure Maintainer: Verify recovery
|
||||
→ Evidence Collector: Confirm fix
|
||||
|
||||
IF caused by infrastructure issue:
|
||||
→ Infrastructure Maintainer: Scale/restart/failover
|
||||
→ DevOps Automator: Support infrastructure changes
|
||||
→ Verify recovery
|
||||
|
||||
IF caused by code bug:
|
||||
→ Relevant Developer Agent: Implement hotfix
|
||||
→ Evidence Collector: Verify fix
|
||||
→ DevOps Automator: Deploy hotfix
|
||||
→ Infrastructure Maintainer: Monitor recovery
|
||||
|
||||
IF caused by external dependency:
|
||||
→ Infrastructure Maintainer: Activate fallback/cache
|
||||
→ Support Responder: Communicate to users
|
||||
→ Monitor for external recovery
|
||||
|
||||
THROUGHOUT:
|
||||
→ Support Responder: Update status page every 15 minutes
|
||||
→ Executive Summary Generator: Brief stakeholders (P0 only)
|
||||
```
|
||||
|
||||
### Step 4: Resolution Verification (Post-fix)
|
||||
|
||||
```
|
||||
Evidence Collector:
|
||||
1. Verify the fix resolves the issue
|
||||
2. Screenshot evidence of working state
|
||||
3. Confirm no new issues introduced
|
||||
|
||||
Infrastructure Maintainer:
|
||||
1. Verify all metrics returning to normal
|
||||
2. Confirm no cascading failures
|
||||
3. Monitor for 30 minutes post-fix
|
||||
|
||||
API Tester (if API-related):
|
||||
1. Run regression on affected endpoints
|
||||
2. Verify response times normalized
|
||||
3. Confirm error rates at baseline
|
||||
|
||||
Output: Incident resolved confirmation
|
||||
```
|
||||
|
||||
### Step 5: Post-Mortem (Within 48 hours)
|
||||
|
||||
```
|
||||
Workflow Optimizer leads post-mortem:
|
||||
|
||||
1. Timeline reconstruction
|
||||
- When was the issue introduced?
|
||||
- When was it detected?
|
||||
- When was it resolved?
|
||||
- Total user impact duration
|
||||
|
||||
2. Root cause analysis
|
||||
- What failed?
|
||||
- Why did it fail?
|
||||
- Why wasn't it caught earlier?
|
||||
- 5 Whys analysis
|
||||
|
||||
3. Impact assessment
|
||||
- Users affected
|
||||
- Revenue impact
|
||||
- Reputation impact
|
||||
- Data impact
|
||||
|
||||
4. Prevention measures
|
||||
- What monitoring would have caught this sooner?
|
||||
- What testing would have prevented this?
|
||||
- What process changes are needed?
|
||||
- What infrastructure changes are needed?
|
||||
|
||||
5. Action items
|
||||
- [Action] → [Owner] → [Deadline]
|
||||
- [Action] → [Owner] → [Deadline]
|
||||
- [Action] → [Owner] → [Deadline]
|
||||
|
||||
Output: Post-Mortem Report → Sprint Prioritizer adds prevention tasks to backlog
|
||||
```
|
||||
|
||||
## Communication Templates
|
||||
|
||||
### Status Page Update (Support Responder)
|
||||
```
|
||||
[TIMESTAMP] — [SERVICE NAME] Incident
|
||||
|
||||
Status: [Investigating / Identified / Monitoring / Resolved]
|
||||
Impact: [Description of user impact]
|
||||
Current action: [What we're doing about it]
|
||||
Next update: [When to expect the next update]
|
||||
```
|
||||
|
||||
### Executive Update (Executive Summary Generator — P0 only)
|
||||
```
|
||||
INCIDENT BRIEF — [TIMESTAMP]
|
||||
|
||||
SITUATION: [Service] is [down/degraded] affecting [N users/% of traffic]
|
||||
CAUSE: [Known/Under investigation] — [Brief description if known]
|
||||
ACTION: [What's being done] — ETA [time estimate]
|
||||
IMPACT: [Business impact — revenue, users, reputation]
|
||||
NEXT UPDATE: [Timestamp]
|
||||
```
|
||||
|
||||
## Escalation Matrix
|
||||
|
||||
| Condition | Escalate To | Action |
|
||||
|-----------|------------|--------|
|
||||
| P0 not resolved in 30 min | Studio Producer | Additional resources, vendor escalation |
|
||||
| P1 not resolved in 2 hours | Project Shepherd | Resource reallocation |
|
||||
| Data breach suspected | Legal Compliance Checker | Regulatory notification assessment |
|
||||
| User data affected | Legal Compliance Checker + Executive Summary Generator | GDPR/CCPA notification |
|
||||
| Revenue impact > $X | Finance Tracker + Studio Producer | Business impact assessment |
|
||||
187
strategy/runbooks/scenario-marketing-campaign.md
Normal file
187
strategy/runbooks/scenario-marketing-campaign.md
Normal file
@@ -0,0 +1,187 @@
|
||||
# 📢 Runbook: Multi-Channel Marketing Campaign
|
||||
|
||||
> **Mode**: NEXUS-Micro to NEXUS-Sprint | **Duration**: 2-4 weeks | **Agents**: 10-15
|
||||
|
||||
---
|
||||
|
||||
## Scenario
|
||||
|
||||
You're launching a coordinated marketing campaign across multiple channels. Content needs to be platform-specific, brand-consistent, and data-driven. The campaign needs to drive measurable acquisition and engagement.
|
||||
|
||||
## Agent Roster
|
||||
|
||||
### Campaign Core
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Social Media Strategist | Campaign lead, cross-platform strategy |
|
||||
| Content Creator | Content production across all formats |
|
||||
| Growth Hacker | Acquisition strategy, funnel optimization |
|
||||
| Brand Guardian | Brand consistency across all channels |
|
||||
| Analytics Reporter | Performance tracking and optimization |
|
||||
|
||||
### Platform Specialists
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Twitter Engager | Twitter/X campaign execution |
|
||||
| TikTok Strategist | TikTok content and growth |
|
||||
| Instagram Curator | Instagram visual content |
|
||||
| Reddit Community Builder | Reddit authentic engagement |
|
||||
| App Store Optimizer | App store presence (if mobile) |
|
||||
|
||||
### Support
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Trend Researcher | Market timing and trend alignment |
|
||||
| Experiment Tracker | A/B testing campaign variations |
|
||||
| Executive Summary Generator | Campaign reporting |
|
||||
| Legal Compliance Checker | Ad compliance, disclosure requirements |
|
||||
|
||||
## Execution Plan
|
||||
|
||||
### Week 1: Strategy & Content Creation
|
||||
|
||||
```
|
||||
Day 1-2: Campaign Strategy
|
||||
├── Social Media Strategist → Cross-platform campaign strategy
|
||||
│ ├── Campaign objectives and KPIs
|
||||
│ ├── Target audience definition
|
||||
│ ├── Platform selection and budget allocation
|
||||
│ ├── Content calendar (4-week plan)
|
||||
│ └── Engagement strategy per platform
|
||||
│
|
||||
├── Trend Researcher → Market timing analysis
|
||||
│ ├── Trending topics to align with
|
||||
│ ├── Competitor campaign analysis
|
||||
│ └── Optimal launch timing
|
||||
│
|
||||
├── Growth Hacker → Acquisition funnel design
|
||||
│ ├── Landing page optimization plan
|
||||
│ ├── Conversion funnel mapping
|
||||
│ ├── Viral mechanics (referral, sharing)
|
||||
│ └── Channel budget allocation
|
||||
│
|
||||
├── Brand Guardian → Campaign brand guidelines
|
||||
│ ├── Campaign-specific visual guidelines
|
||||
│ ├── Messaging framework
|
||||
│ ├── Tone and voice for campaign
|
||||
│ └── Do's and don'ts
|
||||
│
|
||||
└── Legal Compliance Checker → Ad compliance review
|
||||
├── Disclosure requirements
|
||||
├── Platform-specific ad policies
|
||||
└── Regulatory constraints
|
||||
|
||||
Day 3-5: Content Production
|
||||
├── Content Creator → Multi-format content creation
|
||||
│ ├── Blog posts / articles
|
||||
│ ├── Email sequences
|
||||
│ ├── Landing page copy
|
||||
│ ├── Video scripts
|
||||
│ └── Social media copy (platform-adapted)
|
||||
│
|
||||
├── Twitter Engager → Twitter-specific content
|
||||
│ ├── Launch thread (10-15 tweets)
|
||||
│ ├── Daily engagement tweets
|
||||
│ ├── Reply templates
|
||||
│ └── Hashtag strategy
|
||||
│
|
||||
├── TikTok Strategist → TikTok content plan
|
||||
│ ├── Video concepts (3-5 videos)
|
||||
│ ├── Hook strategies
|
||||
│ ├── Trending audio/format alignment
|
||||
│ └── Posting schedule
|
||||
│
|
||||
├── Instagram Curator → Instagram content
|
||||
│ ├── Feed posts (carousel, single image)
|
||||
│ ├── Stories content
|
||||
│ ├── Reels concepts
|
||||
│ └── Visual aesthetic guidelines
|
||||
│
|
||||
└── Reddit Community Builder → Reddit strategy
|
||||
├── Subreddit targeting
|
||||
├── Value-first post drafts
|
||||
├── Comment engagement plan
|
||||
└── AMA preparation (if applicable)
|
||||
```
|
||||
|
||||
### Week 2: Launch & Activate
|
||||
|
||||
```
|
||||
Day 1: Pre-Launch
|
||||
├── All content queued and scheduled
|
||||
├── Analytics tracking verified
|
||||
├── A/B test variants configured
|
||||
├── Landing pages live and tested
|
||||
└── Team briefed on engagement protocols
|
||||
|
||||
Day 2-3: Launch
|
||||
├── Twitter Engager → Launch thread + real-time engagement
|
||||
├── Instagram Curator → Launch posts + stories
|
||||
├── TikTok Strategist → Launch videos
|
||||
├── Reddit Community Builder → Authentic community posts
|
||||
├── Content Creator → Blog post published + email blast
|
||||
├── Growth Hacker → Paid campaigns activated
|
||||
└── Analytics Reporter → Real-time dashboard monitoring
|
||||
|
||||
Day 4-5: Optimize
|
||||
├── Analytics Reporter → First 48-hour performance report
|
||||
├── Growth Hacker → Channel optimization based on data
|
||||
├── Experiment Tracker → A/B test early results
|
||||
├── Social Media Strategist → Engagement strategy adjustment
|
||||
└── Content Creator → Response content based on reception
|
||||
```
|
||||
|
||||
### Week 3-4: Sustain & Optimize
|
||||
|
||||
```
|
||||
Daily:
|
||||
├── Platform agents → Engagement and content posting
|
||||
├── Analytics Reporter → Daily performance snapshot
|
||||
└── Growth Hacker → Funnel optimization
|
||||
|
||||
Weekly:
|
||||
├── Social Media Strategist → Campaign performance review
|
||||
├── Experiment Tracker → A/B test results and new tests
|
||||
├── Content Creator → New content based on performance data
|
||||
└── Analytics Reporter → Weekly campaign report
|
||||
|
||||
End of Campaign:
|
||||
├── Analytics Reporter → Comprehensive campaign analysis
|
||||
├── Growth Hacker → ROI analysis and channel effectiveness
|
||||
├── Executive Summary Generator → Campaign executive summary
|
||||
└── Social Media Strategist → Lessons learned and recommendations
|
||||
```
|
||||
|
||||
## Campaign Metrics
|
||||
|
||||
| Metric | Target | Owner |
|
||||
|--------|--------|-------|
|
||||
| Total reach | [Target based on budget] | Social Media Strategist |
|
||||
| Engagement rate | > 3% average across platforms | Platform agents |
|
||||
| Click-through rate | > 2% on CTAs | Growth Hacker |
|
||||
| Conversion rate | > 5% landing page | Growth Hacker |
|
||||
| Cost per acquisition | < [Target CAC] | Growth Hacker |
|
||||
| Brand sentiment | Net positive | Brand Guardian |
|
||||
| Content pieces published | [Target count] | Content Creator |
|
||||
| A/B tests completed | ≥ 5 | Experiment Tracker |
|
||||
|
||||
## Platform-Specific KPIs
|
||||
|
||||
| Platform | Primary KPI | Secondary KPI | Agent |
|
||||
|----------|------------|---------------|-------|
|
||||
| Twitter/X | Impressions + engagement rate | Follower growth | Twitter Engager |
|
||||
| TikTok | Views + completion rate | Follower growth | TikTok Strategist |
|
||||
| Instagram | Reach + saves | Profile visits | Instagram Curator |
|
||||
| Reddit | Upvotes + comment quality | Referral traffic | Reddit Community Builder |
|
||||
| Email | Open rate + CTR | Unsubscribe rate | Content Creator |
|
||||
| Blog | Organic traffic + time on page | Backlinks | Content Creator |
|
||||
| Paid ads | ROAS + CPA | Quality score | Growth Hacker |
|
||||
|
||||
## Brand Consistency Checkpoints
|
||||
|
||||
| Checkpoint | When | Agent |
|
||||
|-----------|------|-------|
|
||||
| Content review before publishing | Every piece | Brand Guardian |
|
||||
| Visual consistency audit | Weekly | Brand Guardian |
|
||||
| Voice and tone check | Weekly | Brand Guardian |
|
||||
| Compliance review | Before launch + weekly | Legal Compliance Checker |
|
||||
154
strategy/runbooks/scenario-startup-mvp.md
Normal file
154
strategy/runbooks/scenario-startup-mvp.md
Normal file
@@ -0,0 +1,154 @@
|
||||
# 🚀 Runbook: Startup MVP Build
|
||||
|
||||
> **Mode**: NEXUS-Sprint | **Duration**: 4-6 weeks | **Agents**: 18-22
|
||||
|
||||
---
|
||||
|
||||
## Scenario
|
||||
|
||||
You're building a startup MVP — a new product that needs to validate product-market fit quickly. Speed matters, but so does quality. You need to go from idea to live product with real users in 4-6 weeks.
|
||||
|
||||
## Agent Roster
|
||||
|
||||
### Core Team (Always Active)
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Agents Orchestrator | Pipeline controller |
|
||||
| Senior Project Manager | Spec-to-task conversion |
|
||||
| Sprint Prioritizer | Backlog management |
|
||||
| UX Architect | Technical foundation |
|
||||
| Frontend Developer | UI implementation |
|
||||
| Backend Architect | API and database |
|
||||
| DevOps Automator | CI/CD and deployment |
|
||||
| Evidence Collector | QA for every task |
|
||||
| Reality Checker | Final quality gate |
|
||||
|
||||
### Growth Team (Activated Week 3+)
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Growth Hacker | Acquisition strategy |
|
||||
| Content Creator | Launch content |
|
||||
| Social Media Strategist | Social campaign |
|
||||
|
||||
### Support Team (As Needed)
|
||||
| Agent | Role |
|
||||
|-------|------|
|
||||
| Brand Guardian | Brand identity |
|
||||
| Analytics Reporter | Metrics and dashboards |
|
||||
| Rapid Prototyper | Quick validation experiments |
|
||||
| AI Engineer | If product includes AI features |
|
||||
| Performance Benchmarker | Load testing before launch |
|
||||
| Infrastructure Maintainer | Production setup |
|
||||
|
||||
## Week-by-Week Execution
|
||||
|
||||
### Week 1: Discovery + Architecture (Phase 0 + Phase 1 compressed)
|
||||
|
||||
```
|
||||
Day 1-2: Compressed Discovery
|
||||
├── Trend Researcher → Quick competitive scan (1 day, not full report)
|
||||
├── UX Architect → Wireframe key user flows
|
||||
└── Senior Project Manager → Convert spec to task list
|
||||
|
||||
Day 3-4: Architecture
|
||||
├── UX Architect → CSS design system + component architecture
|
||||
├── Backend Architect → System architecture + database schema
|
||||
├── Brand Guardian → Quick brand foundation (colors, typography, voice)
|
||||
└── Sprint Prioritizer → RICE-scored backlog + sprint plan
|
||||
|
||||
Day 5: Foundation Setup
|
||||
├── DevOps Automator → CI/CD pipeline + environments
|
||||
├── Frontend Developer → Project scaffolding
|
||||
├── Backend Architect → Database + API scaffold
|
||||
└── Quality Gate: Architecture Package approved
|
||||
```
|
||||
|
||||
### Week 2-3: Core Build (Phase 2 + Phase 3)
|
||||
|
||||
```
|
||||
Sprint 1 (Week 2):
|
||||
├── Agents Orchestrator manages Dev↔QA loop
|
||||
├── Frontend Developer → Core UI (auth, main views, navigation)
|
||||
├── Backend Architect → Core API (auth, CRUD, business logic)
|
||||
├── Evidence Collector → QA every completed task
|
||||
├── AI Engineer → ML features if applicable
|
||||
└── Sprint Review at end of week
|
||||
|
||||
Sprint 2 (Week 3):
|
||||
├── Continue Dev↔QA loop for remaining features
|
||||
├── Growth Hacker → Design viral mechanics + referral system
|
||||
├── Content Creator → Begin launch content creation
|
||||
├── Analytics Reporter → Set up tracking and dashboards
|
||||
└── Sprint Review at end of week
|
||||
```
|
||||
|
||||
### Week 4: Polish + Hardening (Phase 4)
|
||||
|
||||
```
|
||||
Day 1-2: Quality Sprint
|
||||
├── Evidence Collector → Full screenshot suite
|
||||
├── Performance Benchmarker → Load testing
|
||||
├── Frontend Developer → Fix QA issues
|
||||
├── Backend Architect → Fix API issues
|
||||
└── Brand Guardian → Brand consistency audit
|
||||
|
||||
Day 3-4: Reality Check
|
||||
├── Reality Checker → Final integration testing
|
||||
├── Infrastructure Maintainer → Production readiness
|
||||
└── DevOps Automator → Production deployment prep
|
||||
|
||||
Day 5: Gate Decision
|
||||
├── Reality Checker verdict
|
||||
├── IF NEEDS WORK: Quick fix cycle (2-3 days)
|
||||
├── IF READY: Proceed to launch
|
||||
└── Executive Summary Generator → Stakeholder briefing
|
||||
```
|
||||
|
||||
### Week 5-6: Launch + Growth (Phase 5)
|
||||
|
||||
```
|
||||
Week 5: Launch
|
||||
├── DevOps Automator → Production deployment
|
||||
├── Growth Hacker → Activate acquisition channels
|
||||
├── Content Creator → Publish launch content
|
||||
├── Social Media Strategist → Cross-platform campaign
|
||||
├── Analytics Reporter → Real-time monitoring
|
||||
└── Support Responder → User support active
|
||||
|
||||
Week 6: Optimize
|
||||
├── Growth Hacker → Analyze and optimize channels
|
||||
├── Feedback Synthesizer → Collect early user feedback
|
||||
├── Experiment Tracker → Launch A/B tests
|
||||
├── Analytics Reporter → Week 1 analysis
|
||||
└── Sprint Prioritizer → Plan iteration sprint
|
||||
```
|
||||
|
||||
## Key Decisions
|
||||
|
||||
| Decision Point | When | Who Decides |
|
||||
|---------------|------|-------------|
|
||||
| Go/No-Go on concept | End of Day 2 | Studio Producer |
|
||||
| Architecture approval | End of Day 4 | Senior Project Manager |
|
||||
| Feature scope for MVP | Sprint planning | Sprint Prioritizer |
|
||||
| Production readiness | Week 4 Day 5 | Reality Checker |
|
||||
| Launch timing | After Reality Checker READY | Studio Producer |
|
||||
|
||||
## Success Criteria
|
||||
|
||||
| Metric | Target |
|
||||
|--------|--------|
|
||||
| Time to live product | ≤ 6 weeks |
|
||||
| Core features complete | 100% of MVP scope |
|
||||
| First users onboarded | Within 48 hours of launch |
|
||||
| System uptime | > 99% in first week |
|
||||
| User feedback collected | ≥ 50 responses in first 2 weeks |
|
||||
|
||||
## Common Pitfalls & Mitigations
|
||||
|
||||
| Pitfall | Mitigation |
|
||||
|---------|-----------|
|
||||
| Scope creep during build | Sprint Prioritizer enforces MoSCoW — "Won't" means won't |
|
||||
| Over-engineering for scale | Rapid Prototyper mindset — validate first, scale later |
|
||||
| Skipping QA for speed | Evidence Collector runs on EVERY task — no exceptions |
|
||||
| Launching without monitoring | Infrastructure Maintainer sets up monitoring in Week 1 |
|
||||
| No feedback mechanism | Analytics + feedback collection built into Sprint 1 |
|
||||
Reference in New Issue
Block a user