Can the strategist see my source code?

No, the strategist acts as a remote consultant without direct codebase access. This ensures they provide an unbiased perspective based solely on the conceptual context and constraints you provide.

When should I avoid using the strategist-cooperation skill?

Avoid using it for straightforward implementation tasks, syntax questions, or debugging issues that require the agent to see specific lines of code.

How do I continue a conversation with the strategist?

You can use the 'resume' parameter within the task tool along with the Agent ID provided in your previous session to maintain full context and continuity.

What is the best way to prepare context for the strategist?

State your problem and constraints neutrally. Avoid 'leading the witness' by suggesting your preferred solution; instead, focus on facts, metrics, and what you have already tried.

Strategist Cooperation

Name: Strategist Cooperation
Author: qduc

byqduc

Collaboration Tools

Facilitates high-level architectural consultations and strategic decision-making through unbiased remote expert collaboration.

About

Strategist Cooperation empowers developers to navigate complex architectural dilemmas and technical trade-offs by providing a structured framework for consulting a remote strategist sub-agent. Because the strategist cannot access your codebase, this skill helps you provide objective, unbiased context to receive fresh, high-level perspectives on system design and problem-solving. It includes specialized protocols for session continuity via Agent IDs, neutral context preparation, and iterative consultation cycles, making it an essential tool for breaking through technical blockers and validating major design decisions before committing resources.

Key Features

Session continuity via Agent ID persistence for ongoing consultations
Iterative consultation workflows for evolving technical challenges
Guidance on distinguishing between strategic problems and implementation tasks
Neutral context preparation guidelines to ensure unbiased expert advice
Strategic architectural analysis and complex trade-off evaluation
0 GitHub stars

Use Cases

Resolving technical deadlocks when a project hits a complex logic wall
Validating significant infrastructure or dependency changes before implementation
Evaluating competing architectural patterns like microservices versus monoliths

About

Key Features

Session continuity via Agent ID persistence for ongoing consultations
Iterative consultation workflows for evolving technical challenges
Guidance on distinguishing between strategic problems and implementation tasks
Neutral context preparation guidelines to ensure unbiased expert advice
Strategic architectural analysis and complex trade-off evaluation
0 GitHub stars

Use Cases

Resolving technical deadlocks when a project hits a complex logic wall
Validating significant infrastructure or dependency changes before implementation
Evaluating competing architectural patterns like microservices versus monoliths