iterative-scouting
Skill0 starsChanged 9 months agoMITView on GitHub
Iterate through scouting cycles by gathering feedback, identifying reframes, and re-scouting with new lenses. Use when initial scouting raises deeper questions. Trigger phrases: 'scout this, gather feedback, then re-scout', 'what is the reframe hiding in this feedback', 'iterate the scout', 'two-scout rule
In this repository47 other files it gives its agents.
- agent-teachingSkill
- cf-pages-trespies-deploySkill
- compression-ritualSkill
- context-ingestionSkill
- decision-propagationSkill
- documentation-auditSkill
- era-architectureSkill
- file-managementSkill
- frontend-from-backendSkill
- handoff-protocolSkill
- health-auditSkill
- house-poc-builderSkill
- implementation-promptSkill
- mcp-cloudflare-builderSkill
- mcp-server-builderSkill
- memory-gardenSkill
- multi-surface-strategySkill
- parallel-tracksSkill
- patient-learning-protocolSkill
- planning-with-filesSkill
- poc-tool-forgeSkill
- pre-implementation-checklistSkill
- process-extractionSkill
- product-positioningSkill
- project-explorationSkill
- release-specificationSkill
- repo-context-syncSkill
- repo-statusSkill
- research-modesSkill
- research-synthesisSkill
- retrospectiveSkill
- seed-extractionSkill
- seed-librarySkill
- seed-to-skill-converterSkill
- semantic-clustersSkill
- skill-audit-upgradeSkill
- skill-creationSkill
- skill-maintenanceSkill
- spec-constellation-to-prompt-suiteSkill
- static-tool-verifySkill
- status-templateSkill
- status-writingSkill
- strategic-scoutSkill
- strategic-to-tactical-workflowSkill
- web-research-externalSkill
- workflow-routerSkill
- workspace-navigationSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
When facing a complex strategic decision with no obvious answer.
- Distinctive: line 31
When the initial framing of a problem feels too narrow or binary.
- Distinctive: line 32
After an initial strategic scout has been completed and feedback has been gathered.
- Distinctive: line 33
When you need to teach or demonstrate the process of strategic thinking.
- Very specific: line 47
Use /strategic-scout to explore a diverse set of routes.
- Very specific: line 65
Use /strategic-scout again with this new lens.
- Distinctive: line 89
Before concluding the process, ensure you can answer "yes" to all of the following questions:
- Distinctive: line 100
When running inside the Dojo Genesis plugin:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OpenClaw Integration: This skill is invoked by the Dojo Genesis plugin via
/dojo run iterative-scouting. 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.
Iterative Scouting Pattern Skill
Version: 1.0 Created: 2026-02-07 Author: Manus AI Purpose: To formalize the meta-process of strategic scouting, emphasizing its iterative nature and the importance of reframing.
I. The Philosophy: Scouting as a Conversation
Strategic scouting is not a linear process of finding the "right" answer. It is a conversation with the strategic landscape. The goal of the first scout is not to produce a final decision, but to generate a set of provocative routes that will elicit a deeper, more insightful response. The real prize is not the initial answer, but the reframe of the original question.
This skill operationalizes the pattern of scout → feedback → reframe → re-scout, turning a simple exploration into a powerful engine for strategic discovery.
II. When to Use This Skill
- When facing a complex strategic decision with no obvious answer.
- When the initial framing of a problem feels too narrow or binary.
- After an initial strategic scout has been completed and feedback has been gathered.
- When you need to teach or demonstrate the process of strategic thinking.
III. The Workflow
This is a 4-step workflow for the iterative scouting pattern.
Step 1: Initial Scout
Goal: To explore the initial strategic tension and propose a set of viable routes.
Actions:
- Identify the initial tension (e.g., "Deprecate vs. Companion").
- Use
/strategic-scoutto explore a diverse set of routes. - Synthesize the routes and propose a provocative starting point.
Step 2: Gather Feedback & Listen for the Reframe
Goal: To present the initial scouting results and listen for the deeper question hidden in the feedback.
Actions:
- Present the initial routes.
- Listen not just for agreement or disagreement, but for the way the feedback is framed.
- Identify the "question behind the question" (e.g., the shift from "what to do with the web app" to "what is the mobile experience for?").
Step 3: Re-Scout with the New Lens
Goal: To conduct a second round of scouting using the new, more powerful framing.
Actions:
- Articulate the new, reframed tension (e.g., "Deep Work vs. On-the-Go").
- Use
/strategic-scoutagain with this new lens. - Explore routes that are native to the new framing.
Step 4: Synthesize and Align on the Final Vision
Goal: To synthesize the results of the second scouting round into a final, coherent product vision.
Actions:
- Select the best route from the second round.
- Define the final product positioning, timeline, and business model.
- Confirm alignment and commit to the vision.
IV. Best Practices
- The Two-Scout Rule: For any non-trivial strategic decision, assume you will need at least two rounds of scouting.
- The Reframe is the Prize: The most valuable output of the process is the new, more powerful question you discover.
- Scout for Provocation, Not for Consensus: The goal of the first scout is to provoke a better conversation, not to find an answer that everyone agrees with.
V. Quality Checklist
Before concluding the process, ensure you can answer "yes" to all of the following questions:
- Have you completed at least two rounds of scouting?
- Can you clearly articulate the initial tension and the reframed tension?
- Did the reframe lead to a richer, more insightful set of strategic options?
- Is the final vision aligned with the insights from the second scouting round?
- Is the final decision documented and socialized?
OpenClaw Tool Integration
When running inside the Dojo Genesis plugin:
- Start by calling
dojo_get_contextto retrieve full project state, history, and artifacts - During the skill, follow the workflow steps documented above
- Save outputs using
dojo_save_artifactwith theartifactsoutput directory - Update project state by calling
dojo_update_stateto record skill completion and any phase transitions
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

