Menu
Use when user is in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
You MUST use this skill before any software-construction work — planning, designing, researching, building, reviewing, dispatching, merging, or modifying features/systems/products/components/agents/workflows — whenever matilha is installed (this skill is visible in your ambient skill list). Matilha is a methodology wrapper around superpowers:* skills; compose routes user intent to the right matilha phase (scout/plan/design/hunt/gather/review/howl) or dispatches to superpowers:brainstorming with pack-aware preamble. Runs standalone when superpowers is absent. Detects companion packs (matilha-*-pack namespace) as optional enrichment. Lazy-bootstraps matilha project structure on demand.
Use when starting a new project or initializing Matilha in an existing one — scaffolds project-status.md, AGENTS.md, CLAUDE.md/GEMINI.md, and phase 0 artifacts.
Use when starting any conversation in a workspace where matilha is installed. Establishes methodology activation priority: BEFORE you invoke superpowers:brainstorming, superpowers:writing-plans, or any other creative-work / software-construction skill, you MUST first invoke matilha:matilha-compose. Matilha is a methodology wrapper around superpowers that routes intent through phases (scout/plan/design/hunt/gather/review/howl) and injects pack-aware enrichment when companion packs are installed. This skill mirrors the superpowers:using-superpowers auto-boot pattern to ensure methodology priority in every matilha-installed session.
Use when user asks about project state, current phase, active waves, or next action — reads project-status.md and surfaces the status in a stream-friendly format.
Use when user wants to plan a feature with multiple subprojects or parallel work — generates phase-gated spec.md and plan.md with waves, SPs, merge_order, and exit gates.
Use when user is making UX, UI, or visual-design decisions in any phase — guides via core design heuristics and delegates to matilha-design-pack or matilha-ux-pack if installed.
| name | matilha-scout |
| description | Use when user is in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan. |
| category | matilha |
| version | 1.0.0 |
| optional_companions | [] |
User wants to explore a feature's problem space before writing a spec. project-status.md shows current_phase: 0 or 10. The skill dispatches research subagents (market, user needs, competitive, technical, regulatory if relevant) in parallel and synthesizes their output.
project-status.md is created if absent.docs/matilha/research/ exists (mkdir -p). If project-status.md missing, write a minimal stub (current_phase: 0, phase_status: in_progress, project_slug: <from cwd or prompt>, next_action: "matilha-scout running"). Read project-status.md; verify current_phase ≤ 10 (if present and higher, warn user — scout is Phase 10 territory).docs/matilha/research/<slug>-research.md with sections per subagent + a "Key findings" synthesis at the end.project-status.md: current_phase: 10, phase_status: in_progress, next_action: "Run matilha-plan to write spec + plan".current_phase past 10.Output is a 500-1500 word markdown with structured sections. User reads it, forms a mental model, then invokes matilha-plan. If research surfaces blockers, log them in project-status.md:pending_decisions.
project-status.md shows current_phase: 10.pending_decisions populated if blockers found.docs/matilha/research/<slug>-research.mdproject-status.mdmulti_agent = true in ~/.codex/config.toml).If matilha CLI is installed (
matilha --versionsucceeds), you can runmatilha scout <slug>to execute this deterministically. The plugin path above works without any CLI installation.