Explore strategic tensions and scout multiple routes to find the best path forward. Use when facing a strategic decision with no clear answer. Trigger phrases: 'scout this tension', 'explore multiple routes', 'hold this question open before deciding', 'what are our options here', 'scout to spec pipeline'.
OpenClaw Integration: This skill is invoked by the Dojo Genesis plugin via
/dojo scoutor/dojo run strategic-scout. The agent receives project context automatically via thebefore_agent_starthook. Usedojo_get_contextfor full state,dojo_save_artifactto persist outputs, anddojo_update_stateto record phase transitions and decisions.
Version: 2.1 Created: 2026-02-07 Author: Manus AI Purpose: To provide a structured, repeatable process for navigating strategic uncertainty, exploring multiple possible futures, and aligning on a clear, actionable plan.
Strategic thinking is not about finding the right answer to a problem; it is about exploring the landscape of possibility that a tension reveals. This skill transforms the act of planning from a linear process of problem-solving to a creative process of possibility-seeking.
By beginning with a tension, scouting multiple routes, and continuously aligning on a shared vision, we can navigate uncertainty with clarity and confidence, and arrive at solutions that are both innovative and robust.
This is a 4-step workflow for strategic scouting and decision-making.
Goal: To frame the strategic challenge as a tension to be held, not a problem to be solved.
Goal: To map the landscape of possibility by exploring multiple distinct paths forward.
Goal: To create a hybrid approach that combines the best aspects of multiple routes.
Goal: To ensure that the plan is fully aligned with the user's true strategic vision.
The strategic scout is not standalone — it is phase 1 of a 4-step workflow. Each step produces a persistent artifact:
thinking/[topic]_strategic_scout.mdrelease-specification skilldocs/vX.X.X/[release]_specification.mdimplementation-prompt or zenflow-prompt-writer skilldocs/vX.X.X/prompts/track_[N]_prompt.mdpre-implementation-checklist skill (with Track 0)The scout is the "why." The spec is the "what." The prompts are the "how." Track 0 is the "verify."
Key triggers: "scout to spec", "spec pipeline", "full workflow from tension to implementation"
Before moving to execution, ensure you can answer "yes" to all of the following questions:
When running inside the Dojo Genesis plugin:
dojo_get_context to retrieve full project state, history, and artifactsdojo_save_artifact with appropriate artifact types:
scout → type: "scout-report"spec → type: "specification"tracks → type: "track-decomposition"commission → type: "implementation-prompt"retro → type: "retrospective"dojo_update_state to: