ZacharyZhang-NY
86aa6fdb29
Skills no longer come from the user's ~/.agents library - most users have none, and the CEO branch that compiled the entire catalogue into its prompt overflowed the model context (1.1MB) and failed every CEO run. - Bundle "built-in skills/" with the app (extraResources) and stage it at startup into <profile>/builtin-skills as one dir-per-skill copy - both bundle shapes (SKILL.md dirs and flat category .md files) normalize into the same importable layout - Import the staged catalogue per org at startup and inside onboarding, so the CEO's first run already carries it - Forced house style: resolveRuntimeSnapshot unions the humanizer skill into every agent's runtime (CEO included) as a resolution rule - no binding row to forget, delete, or bypass; revoke_skill refuses it - CEO staffs hires with skills: hire_agent accepts a skills array, grant_skill/revoke_skill adjust later, list_skills now shows descriptions from skill frontmatter - Kill the c_suite compile-all branch; everyone resolves bindings-only, capped at 200k chars with omissions named in the prompt - Remove the Skills settings page and its import/sync/test IPC surface; drop ~/.agents discovery and the AGENTCOMPANY_NEW_SKILLS_ROOT seam in favor of AGENTCOMPANY_NEW_BUILTIN_SKILLS_DIR - Tests: staging/import/forced-resolution/cap units, real-bundle CI check, e2e asserts the tab is gone and the catalogue self-imports
8.1 KiB
8.1 KiB
🚀 Phase 5 Playbook — Launch & Growth
Duration: 2-4 weeks (T-7 through T+14) | Agents: 12 | Gate Keepers: Studio Producer + Analytics Reporter
Objective
Coordinate go-to-market execution across all channels simultaneously. Maximum impact at launch. Every marketing agent fires in concert while engineering ensures stability.
Pre-Conditions
- Phase 4 Quality Gate passed (Reality Checker READY verdict)
- Phase 4 Handoff Package received
- Production deployment plan approved
- Marketing content pipeline ready (from Phase 3 Track B)
Launch Timeline
T-7: Pre-Launch Week
Content & Campaign Preparation (Parallel)
ACTIVATE Content Creator:
- Finalize all launch content (blog posts, landing pages, email sequences)
- Queue content in publishing platforms
- Prepare response templates for anticipated questions
- Create launch day real-time content plan
ACTIVATE Social Media Strategist:
- Finalize cross-platform campaign assets
- Schedule pre-launch teaser content
- Coordinate influencer partnerships
- Prepare platform-specific content variations
ACTIVATE Growth Hacker:
- Arm viral mechanics (referral codes, sharing incentives)
- Configure growth experiment tracking
- Set up funnel analytics
- Prepare acquisition channel budgets
ACTIVATE App Store Optimizer (if mobile):
- Finalize store listing (title, description, keywords, screenshots)
- Submit app for review (if applicable)
- Prepare launch day ASO adjustments
- Configure in-app review prompts
Technical Preparation (Parallel)
ACTIVATE DevOps Automator:
- Prepare blue-green deployment
- Verify rollback procedures
- Configure feature flags for gradual rollout
- Test deployment pipeline end-to-end
ACTIVATE Infrastructure Maintainer:
- Configure auto-scaling for 10x expected traffic
- Verify monitoring and alerting thresholds
- Test disaster recovery procedures
- Prepare incident response runbook
ACTIVATE Project Shepherd:
- Distribute launch checklist to all agents
- Confirm all dependencies resolved
- Set up launch day communication channel
- Brief stakeholders on launch plan
T-1: Launch Eve
FINAL CHECKLIST (Project Shepherd coordinates):
Technical:
☐ Blue-green deployment tested
☐ Rollback procedure verified
☐ Auto-scaling configured
☐ Monitoring dashboards live
☐ Incident response team on standby
☐ Feature flags configured
Content:
☐ All content queued and scheduled
☐ Email sequences armed
☐ Social media posts scheduled
☐ Blog posts ready to publish
☐ Press materials distributed
Marketing:
☐ Viral mechanics tested
☐ Referral system operational
☐ Analytics tracking verified
☐ Ad campaigns ready to activate
☐ Community engagement plan ready
Support:
☐ Support team briefed
☐ FAQ and help docs published
☐ Escalation procedures confirmed
☐ Feedback collection active
T-0: Launch Day
Hour 0: Deployment
ACTIVATE DevOps Automator:
1. Execute blue-green deployment to production
2. Run health checks on all services
3. Verify database migrations complete
4. Confirm all endpoints responding
5. Switch traffic to new deployment
6. Monitor error rates for 15 minutes
7. Confirm: DEPLOYMENT SUCCESSFUL or ROLLBACK
ACTIVATE Infrastructure Maintainer:
1. Monitor all system metrics in real-time
2. Watch for traffic spikes and scaling events
3. Track error rates and response times
4. Alert on any threshold breaches
5. Confirm: SYSTEMS STABLE
Hour 1-2: Marketing Activation
ACTIVATE Twitter Engager:
- Publish launch thread
- Engage with early responses
- Monitor brand mentions
- Amplify positive reactions
- Real-time conversation participation
ACTIVATE Reddit Community Builder:
- Post authentic launch announcement in relevant subreddits
- Engage with comments (value-first, not promotional)
- Monitor community sentiment
- Respond to technical questions
ACTIVATE Instagram Curator:
- Publish launch visual content
- Stories with product demos
- Engage with early followers
- Cross-promote with other channels
ACTIVATE TikTok Strategist:
- Publish launch videos
- Monitor for viral potential
- Engage with comments
- Adjust content based on early performance
Hour 2-8: Monitoring & Response
ACTIVATE Support Responder:
- Handle incoming user inquiries
- Document common issues
- Escalate technical problems to engineering
- Collect early user feedback
ACTIVATE Analytics Reporter:
- Real-time metrics dashboard
- Hourly traffic and conversion reports
- Channel attribution tracking
- User behavior flow analysis
ACTIVATE Feedback Synthesizer:
- Monitor all feedback channels
- Categorize incoming feedback
- Identify critical issues
- Prioritize user-reported problems
T+1 to T+7: Post-Launch Week
DAILY CADENCE:
Morning:
├── Analytics Reporter → Daily metrics report
├── Feedback Synthesizer → Feedback summary
├── Infrastructure Maintainer → System health report
└── Growth Hacker → Channel performance analysis
Afternoon:
├── Content Creator → Response content based on reception
├── Social Media Strategist → Engagement optimization
├── Experiment Tracker → Launch A/B test results
└── Support Responder → Issue resolution summary
Evening:
├── Executive Summary Generator → Daily stakeholder briefing
├── Project Shepherd → Cross-team coordination
└── DevOps Automator → Deployment of hotfixes (if needed)
T+7 to T+14: Optimization Week
ACTIVATE Growth Hacker:
- Analyze first-week acquisition data
- Optimize conversion funnels based on data
- Scale winning channels, cut losing ones
- Refine viral mechanics based on K-factor data
ACTIVATE Analytics Reporter:
- Week 1 comprehensive analysis
- Cohort analysis of launch users
- Retention curve analysis
- Revenue/engagement metrics
ACTIVATE Experiment Tracker:
- Launch systematic A/B tests
- Test onboarding variations
- Test pricing/packaging (if applicable)
- Test feature discovery flows
ACTIVATE Executive Summary Generator:
- Week 1 executive summary (SCQA format)
- Key metrics vs. targets
- Recommendations for Week 2+
- Resource reallocation suggestions
Quality Gate Checklist
| # | Criterion | Evidence Source | Status |
|---|---|---|---|
| 1 | Deployment successful (zero-downtime) | DevOps Automator deployment logs | ☐ |
| 2 | Systems stable (no P0/P1 in 48 hours) | Infrastructure Maintainer monitoring | ☐ |
| 3 | User acquisition channels active | Analytics Reporter dashboard | ☐ |
| 4 | Feedback loop operational | Feedback Synthesizer report | ☐ |
| 5 | Stakeholders informed | Executive Summary Generator output | ☐ |
| 6 | Support operational | Support Responder metrics | ☐ |
| 7 | Growth metrics tracking | Growth Hacker channel reports | ☐ |
Gate Decision
Dual sign-off: Studio Producer (strategic) + Analytics Reporter (data)
- STABLE: Product launched, systems stable, growth active → Phase 6 activation
- CRITICAL: Major issues requiring immediate engineering response → Hotfix cycle
- ROLLBACK: Fundamental problems → Revert deployment, return to Phase 4
Handoff to Phase 6
## Phase 5 → Phase 6 Handoff Package
### For Ongoing Operations:
- Launch metrics baseline (Analytics Reporter)
- User feedback themes (Feedback Synthesizer)
- System performance baseline (Infrastructure Maintainer)
- Growth channel performance (Growth Hacker)
- Support issue patterns (Support Responder)
### For Continuous Improvement:
- A/B test results and learnings (Experiment Tracker)
- Process improvement recommendations (Workflow Optimizer)
- Financial performance vs. projections (Finance Tracker)
- Compliance monitoring status (Legal Compliance Checker)
### Operational Cadences Established:
- Daily: System monitoring, support, analytics
- Weekly: Analytics report, feedback synthesis, sprint planning
- Monthly: Executive summary, financial review, compliance check
- Quarterly: Strategic review, process optimization, market intelligence
Phase 5 is complete when the product is deployed, systems are stable for 48+ hours, growth channels are active, and the feedback loop is operational.