goal
CommandSet, check, or complete the persistent project goal stored in .goal.md. Trigger as /coco-goal or /coco:goal.
@coco-researchInstall CommandDevelopment
Command
/think
Use when the user runs /team think, asks for options analysis, or wants a brainstorm before deciding. Generates structured options, stress-tests them across review layers, and returns a decision matrix with a recommendation.
$ npx -y skills add coco-research/coco --agent claude-code
Command definition
think.mddescription: "Use when the user runs /team think, asks for options analysis, or wants a brainstorm before deciding. Generates structured options, stress-tests them across review layers, and returns a decision matrix with a recommendation."
/team think — Analysis & Brainstorm Pipeline
> Called by team.md router when action is `think`. > Balanced pipeline: L1 researches, L2 generates options, L3 stress-tests them.
Role Selection Bias
| Layer | Preferred Roles | Count | |-------|----------------|-------| | L1 | domain-researcher, technical-analyst, business-analyst | 3-4 | | L2 | senior-pm, senior-backend-eng or senior-frontend-eng (domain-dependent), technical-writer | 2-3 | | L3 | domain-accuracy, doc-quality | 2 | | L4 | principal-architect or principal-pm | 1 |
Pipeline Customization
Layer 1: Problem Analysis
L1 agents decompose the problem:
- **domain-researcher** → What approaches exist in the industry?
- **technical-analyst** → What are the technical constraints and options?
- **business-analyst** → What are the business constraints and stakeholder needs?
Layer 2: Option Generation
L2 agents produce structured options:
- Each option has: Description, Pros, Cons, Effort estimate, Risk assessment
- Options are compared in a decision matrix
- senior-pm frames options from product perspective
- Engineers frame options from technical perspective
**Toolkit integration:**
- Check team:toolkit.md for brainstorming tools
- Apply structured thinking frameworks (MECE, first principles, inversion)
Layer 3: Stress Testing
L3 agents challenge each option:
- What could go wrong?
- What assumptions are we making?
- What's the worst-case scenario?
- Which option survives scrutiny best?
Layer 4: Decision Recommendation
Principal produces:
- Recommended option with rationale
- Risk mitigation plan for the recommended option
- Conditions under which alternative options would be better
- Decision framework for the user to make the final call
GSD Integration
N/A — Brainstorming is project-context-independent.
Read more
description: "Use when the user runs /team think, asks for options analysis, or wants a brainstorm before deciding. Generates structured options, stress-tests them across review layers, and returns a decision matrix with a recommendation."
/team think — Analysis & Brainstorm Pipeline
> Called by team.md router when action is `think`. > Balanced pipeline: L1 researches, L2 generates options, L3 stress-tests them.
Role Selection Bias
| Layer | Preferred Roles | Count | |-------|----------------|-------| | L1 | domain-researcher, technical-analyst, business-analyst | 3-4 | | L2 | senior-pm, senior-backend-eng or senior-frontend-eng (domain-dependent), technical-writer | 2-3 | | L3 | domain-accuracy, doc-quality | 2 | | L4 | principal-architect or principal-pm | 1 |
Pipeline Customization
Layer 1: Problem Analysis
L1 agents decompose the problem:
- **domain-researcher** → What approaches exist in the industry?
- **technical-analyst** → What are the technical constraints and options?
- **business-analyst** → What are the business constraints and stakeholder needs?
Layer 2: Option Generation
L2 agents produce structured options:
- Each option has: Description, Pros, Cons, Effort estimate, Risk assessment
- Options are compared in a decision matrix
- senior-pm frames options from product perspective
- Engineers frame options from technical perspective
**Toolkit integration:**
- Check team:toolkit.md for brainstorming tools
- Apply structured thinking frameworks (MECE, first principles, inversion)
Layer 3: Stress Testing
L3 agents challenge each option:
- What could go wrong?
- What assumptions are we making?
- What's the worst-case scenario?
- Which option survives scrutiny best?
Layer 4: Decision Recommendation
Principal produces:
- Recommended option with rationale
- Risk mitigation plan for the recommended option
- Conditions under which alternative options would be better
- Decision framework for the user to make the final call
GSD Integration
N/A — Brainstorming is project-context-independent.
Ships withcoco
495 personas across 13 departments, 229 skills[^installed] and 388 commands in the full catalog (coco 1.9.0, 2026-10-21). Agent skills, slash commands and subagents for Claude Code, Cursor, Codex and other AI coding agents.
796200 skills53 agents
Stars on GitHub
Momentum
- stars in total
- 796
Other commands on coco.
@coco-researchInstall Commandmermaid
CommandUse when the user asks for a diagram or chart: flowchart, sequence, state, class, ER, or XY chart, as SVG, HTML, or terminal…
@coco-researchInstall Commandread
CommandShow latest emails from a specific person. Usage: /email-read alice
@coco-researchInstall Commandreply
CommandDraft a reply to a specific email. Usage: /email-reply Project Phase 2 Contract Data
@coco-researchInstall Commandsave
CommandSave matching emails to a project folder for sync processing. Usage: /email-save alice to emails/
@coco-researchInstall Commandsearch
CommandSearch emails by subject keywords. Usage: /email-search github webhook
@coco-researchInstall CommandMore commands from other plugins.
Auto-invoked
Auto-invoked
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
@addyosmaniInstall Command