From taches-cc-resources
Maps landscape of a domain or current context: players, tools, trends, gaps. Asks clarifying questions then outputs structured report with categories and visual map.
How this command is triggered — by the user, by Claude, or both
Slash command
/taches-cc-resources:landscape domain/space or leave blank for current contextresearch/The summary Claude sees in its command listing — used to decide when to auto-load this command
<objective> Map the landscape of $ARGUMENTS (or the current topic if no arguments provided). Understand the full space: who the players are, what tools exist, where things are heading, and where the gaps are. </objective> <intake_gate> <context_analysis> First, analyze $ARGUMENTS to extract what's already provided: - The domain/space to map - Scope boundaries - Known players or categories - What you're trying to learn Only ask about genuine gaps - don't re-ask what's already stated. </context_analysis> <initial_questions> Use AskUserQuestion to ask 2-4 questions based on actual gaps: ...
Understand the full space: who the players are, what tools exist, where things are heading, and where the gaps are.
<intake_gate>
<context_analysis> First, analyze $ARGUMENTS to extract what's already provided:
Only ask about genuine gaps - don't re-ask what's already stated. </context_analysis>
<initial_questions> Use AskUserQuestion to ask 2-4 questions based on actual gaps:
If scope unclear:
If focus unclear:
If depth unclear:
If use unclear:
Skip questions where $ARGUMENTS already provides the answer. </initial_questions>
<decision_gate> After receiving answers, use AskUserQuestion:
Question: "Ready to map the landscape, or would you like me to ask more questions?"
Options:
If "Ask more questions" → generate 2-3 contextual follow-ups, then present decision gate again If "Let me add context" → receive input, then present decision gate again If "Start mapping" → proceed to research </decision_gate>
</intake_gate>
After intake complete:<output_format>
[2-3 sentences: shape of the space, key trend, main opportunity]
[What's included and excluded from this landscape]
[Category 1: e.g., "Data Storage"]
[Category 2: e.g., "Processing"] [Same structure...]
[Category 3: e.g., "Visualization"] [Same structure...]
[Visual representation - can be ASCII or description]
Category 1 Category 2 Category 3
----------- ----------- -----------
Player A Player D Player G
Player B Player E Player H
Player C Player F
<claude_context>
Next Action: Deep dive on specific area, competitive research on key players, or run /plan/brief to define our approach
<artifact_output> Save the research to a file:
Create directory structure if it doesn't exist:
[current-working-directory]/artifacts/research/Generate filename from topic:
YYYY-MM-DD-[topic]-landscape.md2025-01-15-music-production-tools-landscape.mdWrite the complete research to the file
Report to user: "Saved to artifacts/research/[filename]"
</artifact_output>
<success_criteria>
npx claudepluginhub glittercowboy/taches-cc-resources --plugin taches-cc-resources/deep-researchConducts configurable research on a topic: focused (one question), wide (ecosystem landscape), or deep (full build plan). Specify [depth] [topic]; defaults to wide.
/decomposeGuides layer-by-layer decomposition of any technology or market signal through 6 structured layers, producing Value Chain diagram, Mindmap, or Research Note.
/researchConducts deep research on a topic: frames the question, gathers credible sources via web search, analyzes findings, and produces a structured report with key insights and recommendations.
/product-intelResearches competitors or industry topics via argument, generating structured markdown files in /product-intel/ with features, positioning, activity, comparisons, and opportunities.
/competitor-scanConducts structured competitive analysis for a specified market or product, mapping players, comparing features with insights, evaluating gaps, and recommending prioritized responses in markdown.
/researchAdaptive multi-dimensional feature research that auto-adjusts interview depth based on input richness. Gathers competitors, UX/UI, codebase, and optional tech stack or metrics/ROI. Saves structured research artifacts.