runbooks
starsforks
How to install runbooks?
chipagosfinest/enterprise-team/runbooks
$npx -y skills add Chipagosfinest/enterprise-team --skill runbooksPre-built scenario configurations for common multi-agent workflows. Quick-start templates for MVPs, features, campaigns, incidents, and audits. Triggers: runbook, playbook, scenario, launch, mvp, incident response, marketing campaign, security audit, feature build, startup.
SKILL.md
| 1 | # Runbooks — Pre-Built Scenarios |
| 2 | |
| 3 | ## Startup MVP (4-6 weeks, Sprint mode) |
| 4 | |
| 5 | ``` |
| 6 | Activate enterprise-orchestrator in Sprint mode. |
| 7 | |
| 8 | Team: |
| 9 | - PM: product-manager (spec + sprint planning) |
| 10 | - Design: ui-designer (design system + components) |
| 11 | - Engineering: fullstack-engineer or backend-engineer + frontend-engineer |
| 12 | - QA: qa-engineer (task-level) + reality-checker (final gate) |
| 13 | - Infra: devops-engineer (CI/CD + deploy) |
| 14 | |
| 15 | Pipeline: |
| 16 | 1. product-manager creates task list from spec |
| 17 | 2. ui-designer creates design tokens + component sketches |
| 18 | 3. [Dev ↔ QA loop] for each task (max 3 retries per task) |
| 19 | 4. reality-checker final integration check |
| 20 | 5. devops-engineer deploys to staging |
| 21 | ``` |
| 22 | |
| 23 | ## Enterprise Feature (2-4 weeks, Sprint mode) |
| 24 | |
| 25 | ``` |
| 26 | Activate enterprise-orchestrator in Sprint mode. |
| 27 | |
| 28 | Team: |
| 29 | - PM: product-manager (requirements) |
| 30 | - Arch: solutions-architect (design review) |
| 31 | - Dev: backend-engineer + frontend-engineer |
| 32 | - Security: security-engineer (review) |
| 33 | - QA: qa-engineer + reality-checker |
| 34 | - Infra: devops-engineer (feature flags + deploy) |
| 35 | |
| 36 | Pipeline: |
| 37 | 1. solutions-architect reviews architecture impact |
| 38 | 2. security-engineer reviews auth/data implications |
| 39 | 3. [Dev ↔ QA loop] for each task |
| 40 | 4. security-engineer final security review |
| 41 | 5. reality-checker final integration |
| 42 | 6. devops-engineer deploys behind feature flag |
| 43 | ``` |
| 44 | |
| 45 | ## Marketing Campaign (1-2 weeks, Micro mode) |
| 46 | |
| 47 | ``` |
| 48 | Activate enterprise-orchestrator in Micro mode. |
| 49 | |
| 50 | Team: |
| 51 | - Lead: growth-marketer (strategy + channels) |
| 52 | - Content: content-marketer (copy + blog) |
| 53 | - Social: social-media-manager (distribution) |
| 54 | - Design: graphic-designer (assets) |
| 55 | - Analytics: data-analyst (tracking + reporting) |
| 56 | |
| 57 | Pipeline: |
| 58 | 1. growth-marketer defines campaign strategy + channels |
| 59 | 2. content-marketer creates copy, graphic-designer creates assets |
| 60 | 3. brand-marketer reviews for brand consistency |
| 61 | 4. social-media-manager schedules distribution |
| 62 | 5. data-analyst sets up tracking and reports weekly |
| 63 | ``` |
| 64 | |
| 65 | ## Incident Response (hours, Micro mode) |
| 66 | |
| 67 | ``` |
| 68 | Activate enterprise-orchestrator in Micro mode — INCIDENT. |
| 69 | |
| 70 | Severity: [P0/P1/P2] |
| 71 | Team: |
| 72 | - Lead: sre (incident commander) |
| 73 | - Debug: backend-engineer or frontend-engineer (root cause) |
| 74 | - Infra: devops-engineer (rollback/mitigation) |
| 75 | - Comms: communications-specialist (stakeholder updates) |
| 76 | |
| 77 | Pipeline: |
| 78 | 1. sre assesses impact and declares severity |
| 79 | 2. devops-engineer checks for recent deploys (rollback candidate?) |
| 80 | 3. backend/frontend-engineer investigates root cause |
| 81 | 4. Fix → qa-engineer validates → devops-engineer deploys hotfix |
| 82 | 5. sre writes post-mortem with timeline and action items |
| 83 | 6. communications-specialist sends stakeholder update |
| 84 | |
| 85 | MTTR target: P0 < 30 min, P1 < 2 hours, P2 < 1 day |
| 86 | ``` |
| 87 | |
| 88 | ## Security Audit (3-5 days, Micro mode) |
| 89 | |
| 90 | ``` |
| 91 | Activate enterprise-orchestrator in Micro mode. |
| 92 | |
| 93 | Team: |
| 94 | - Lead: security-auditor (assessment + report) |
| 95 | - Code: security-engineer (code review) |
| 96 | - Infra: devops-engineer (infrastructure review) |
| 97 | - Legal: compliance-officer (regulatory check) |
| 98 | |
| 99 | Pipeline: |
| 100 | 1. security-auditor defines scope and creates threat model |
| 101 | 2. security-engineer reviews code (OWASP Top 10) |
| 102 | 3. devops-engineer reviews infrastructure (secrets, access, configs) |
| 103 | 4. compliance-officer checks regulatory requirements |
| 104 | 5. security-auditor compiles final report with severity ratings |
| 105 | 6. engineering-orchestrator assigns fixes by severity |
| 106 | ``` |
| 107 | |
| 108 | ## SOC2 Compliance (4-8 weeks, Full mode) |
| 109 | |
| 110 | ``` |
| 111 | Activate enterprise-orchestrator in Full mode. |
| 112 | |
| 113 | Cross-functional team: |
| 114 | - compliance-officer (requirements matrix) |
| 115 | - security-engineer (technical controls) |
| 116 | - devops-engineer (infrastructure hardening) |
| 117 | - technical-writer (policy documentation) |
| 118 | - legal-counsel (legal review) |
| 119 | |
| 120 | Pipeline: |
| 121 | Phase 1: compliance-officer maps SOC2 requirements to current state |
| 122 | Phase 2: security-engineer + devops-engineer implement controls |
| 123 | Phase 3: technical-writer documents policies and procedures |
| 124 | Phase 4: compliance-officer validates all controls |
| 125 | Phase 5: legal-counsel reviews documentation |
| 126 | Phase 6: reality-checker final audit |
| 127 | ``` |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
