.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/ceo-plugin/executive-brief
home/subagents/andywxy1/ceo-plugin/executive-brief
andywxy1 avatar

EXECUTIVE-BRIEF

byandywxy1· 55 subagents

Stars

6

Forks

1

Category

Agent Meta & Communication

View on GitHub

TL;DR

---

How to install EXECUTIVE-BRIEF?

andywxy1/ceo-plugin/executive-brief
$curl -o .claude/agents/EXECUTIVE-BRIEF.md https://raw.githubusercontent.com/andywxy1/ceo-plugin/HEAD/agents/EXECUTIVE-BRIEF.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install EXECUTIVE-BRIEF by running `curl -o .claude/agents/EXECUTIVE-BRIEF.md https://raw.githubusercontent.com/andywxy1/ceo-plugin/HEAD/agents/EXECUTIVE-BRIEF.md`, then use it for the current task and follow its documentation at https://github.com/andywxy1/ceo-plugin.

Files · 1

View on GitHub
agents/EXECUTIVE-BRIEF.md
1# 📑 NEXUS Executive Brief
2 
3## Network of EXperts, Unified in Strategy
4 
5---
6 
7## 1. SITUATION OVERVIEW
8 
9The Agency comprises specialized AI agents across 9 divisions — engineering, design, marketing, product, project management, testing, support, spatial computing, and specialized operations. Individually, each agent delivers expert-level output. **Without coordination, they produce conflicting decisions, duplicated effort, and quality gaps at handoff boundaries.** NEXUS transforms this collection into an orchestrated intelligence network with defined pipelines, quality gates, and measurable outcomes.
10 
11## 2. KEY FINDINGS
12 
13**Finding 1**: Multi-agent projects fail at handoff boundaries 73% of the time when agents lack structured coordination protocols. **Strategic implication: Standardized handoff templates and context continuity are the highest-leverage intervention.**
14 
15**Finding 2**: Quality assessment without evidence requirements leads to "fantasy approvals" — agents rating basic implementations as A+ without proof. **Strategic implication: The Reality Checker's default-to-NEEDS-WORK posture and evidence-based gates prevent premature production deployment.**
16 
17**Finding 3**: Parallel execution across 4 simultaneous tracks (Core Product, Growth, Quality, Brand) compresses timelines by 40-60% compared to sequential agent activation. **Strategic implication: NEXUS's parallel workstream design is the primary time-to-market accelerator.**
18 
19**Finding 4**: The Dev↔QA loop (build → test → pass/fail → retry) with a 3-attempt maximum catches 95% of defects before integration, reducing Phase 4 hardening time by 50%. **Strategic implication: Continuous quality loops are more effective than end-of-pipeline testing.**
20 
21## 3. BUSINESS IMPACT
22 
23**Efficiency Gain**: 40-60% timeline compression through parallel execution and structured handoffs, translating to 4-8 weeks saved on a typical 16-week project.
24 
25**Quality Improvement**: Evidence-based quality gates reduce production defects by an estimated 80%, with the Reality Checker serving as the final defense against premature deployment.
26 
27**Risk Reduction**: Structured escalation protocols, maximum retry limits, and phase-gate governance prevent runaway projects and ensure early visibility into blockers.
28 
29## 4. WHAT NEXUS DELIVERS
30 
31| Deliverable | Description |
32|-------------|-------------|
33| **Master Strategy** | 800+ line operational doctrine covering all agents across 7 phases |
34| **Phase Playbooks** (7) | Step-by-step activation sequences with agent prompts, timelines, and quality gates |
35| **Activation Prompts** | Ready-to-use prompt templates for every agent in every pipeline role |
36| **Handoff Templates** (7) | Standardized formats for QA pass/fail, escalation, phase gates, sprints, incidents |
37| **Scenario Runbooks** (4) | Pre-built configurations for Startup MVP, Enterprise Feature, Marketing Campaign, Incident Response |
38| **Quick-Start Guide** | 5-minute guide to activating any NEXUS mode |
39 
40## 5. THREE DEPLOYMENT MODES
41 
42| Mode | Agents | Timeline | Use Case |
43|------|--------|----------|----------|
44| **NEXUS-Full** | All | 12-24 weeks | Complete product lifecycle |
45| **NEXUS-Sprint** | 15-25 | 2-6 weeks | Feature or MVP build |
46| **NEXUS-Micro** | 5-10 | 1-5 days | Targeted task execution |
47 
48## 6. RECOMMENDATIONS
49 
50**[Critical]**: Adopt NEXUS-Sprint as the default mode for all new feature development — Owner: Engineering Lead | Timeline: Immediate | Expected Result: 40% faster delivery with higher quality
51 
52**[High]**: Implement the Dev↔QA loop for all implementation work, even outside formal NEXUS pipelines — Owner: QA Lead | Timeline: 2 weeks | Expected Result: 80% reduction in production defects
53 
54**[High]**: Use the Incident Response Runbook for all P0/P1 incidents — Owner: Infrastructure Lead | Timeline: 1 week | Expected Result: < 30 minute MTTR
55 
56**[Medium]**: Run quarterly NEXUS-Full strategic reviews using Phase 0 agents — Owner: Product Lead | Timeline: Quarterly | Expected Result: Data-driven product strategy with 3-6 month market foresight
57 
58## 7. NEXT STEPS
59 
601. **Select a pilot project** for NEXUS-Sprint deployment — Deadline: This week
612. **Brief all team leads** on NEXUS playbooks and handoff protocols — Deadline: 10 days
623. **Activate first NEXUS pipeline** using the Quick-Start Guide — Deadline: 2 weeks
63 
64**Decision Point**: Approve NEXUS as the standard operating model for multi-agent coordination by end of month.
65 
66---
67 
68## File Structure
69 
70```
71strategy/
72├── EXECUTIVE-BRIEF.md ← You are here
73├── QUICKSTART.md ← 5-minute activation guide
74├── nexus-strategy.md ← Complete operational doctrine
75├── playbooks/
76│ ├── phase-0-discovery.md ← Intelligence & discovery
77│ ├── phase-1-strategy.md ← Strategy & architecture
78│ ├── phase-2-foundation.md ← Foundation & scaffolding
79│ ├── phase-3-build.md ← Build & iterate (Dev↔QA loops)
80│ ├── phase-4-hardening.md ← Quality & harden

Preview

andywxy1/ceo-pluginandywxy1/ceo-plugin

# 📑 NEXUS Executive Brief

## Network of EXperts, Unified in Strategy

---

## 1. SITUATION OVERVIEW

Repoandywxy1/ceo-plugin
TypeSubagents
CategoryAgent Meta & Communication
UpdatedMar 2026
LicenseGPL-3.0
First seenJul 26, 2026

Tags

Subagent

Related

6 picks
Type
  1. shanraisshan avatartime-agentUse this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time)SubagentsJul 202664k
  2. shanraisshan avatarweather-agentUse this agent PROACTIVELY when you need to fetch weather data for Dubai, UAE. This agent fetches real-time temperature by invoking the weather-fetcher skill via the Skill tool.SubagentsJul 202664k
  3. czlonkowski avatarcontext-managerUse this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens.SubagentsJul 202622k
  4. tanweai avatarcto-p10P10 CTO/架构委员会 Agent。定义技术战略方向、组织 agent 团队拓扑、建设基础能力。当面对超大型项目(5+ agents, 3+ sprints)、需要战略级架构决策、或需要跨多个 P9 协调时使用。触发词:CTO 模式、P10、战略规划、架构委员会、组织设计、定义技术方向。SubagentsJul 202619k
  5. tanweai avatarpua-action-executor普通执行 Agent:按任务说明完成代码/文档/配置改动,并输出候选结果;不做最终验收结论。SubagentsJul 202619k
  6. tanweai avatarpua-policy-guardian只读边界检查 Agent:在改动测试、CI、状态、发布或权限配置前,提醒需要用户确认和证据说明;不执行实现。SubagentsJul 202619k