القائمة
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.
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 is in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan.
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-plan |
| description | 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. |
| category | matilha |
| version | 1.0.0 |
| optional_companions | ["superpowers:brainstorming","superpowers:writing-plans"] |
User has Phase 10 research (or skips scout) and wants spec + plan artifacts before dispatching work. Produces docs/matilha/specs/<slug>-spec.md + docs/matilha/plans/<slug>-plan.md.
project-status.md and docs/matilha/. If absent, create minimally:
mkdir -p docs/matilha/specs docs/matilha/plans docs/matilha/researchproject-status.md missing, write a minimal stub with frontmatter current_phase: 10, phase_status: in_progress, project_slug: <derived from cwd or user-provided>, next_action: "matilha-plan in progress". User can later run matilha-init for fuller bootstrap.project-status.md and any existing research in docs/matilha/research/.matilha-compose for canonical template):
superpowers:brainstorming is available, inspect the ambient skill list for skills with plugin namespace matching matilha-*-pack (installed companion packs). Group by plugin namespace.skills/matilha-compose/SKILL.md Step 4 (per-pack mini-synthesis + skill list + guidance paragraph for the receiving skill).superpowers:brainstorming via the Skill tool.superpowers:brainstorming is absent OR zero packs are detected, run the condensed clarifying flow inline (existing behavior — ask 3–5 questions drawing on detected pack skills if any, else use methodology-core heuristics).docs/matilha/specs/<slug>-spec.md with: purpose, context, design principles, target deliverables, architecture, data flow, open questions, exit criteria.superpowers:writing-plans available, invoke via Skill tool to generate the task-by-task plan. Otherwise, write the plan inline following methodology/40-execucao.md conventions.docs/matilha/plans/<slug>-plan.md with: goal, architecture, SPs, per-task steps, exit gates.current_phase: 30, phase_status: complete, feature_artifacts appended, next_action: "Run /matilha-hunt <slug>".planSchema before writing.current_phase past 30 without user approval.User gets two artifacts ready for hunt/gather. Plan must be directly executable via subagent-driven-development or manual hunt.
docs/matilha/specs/<slug>-spec.md.docs/matilha/plans/<slug>-plan.md and parses against planSchema.current_phase: 30 in project-status.md.feature_artifacts entry added.Companion-pack awareness is handled via the pack-aware preamble-injection logic in Step 2 of the Execution Workflow. See skills/matilha-compose/SKILL.md for the canonical pack detection, intent classification, and preamble template.
matilha-*-pack (e.g., matilha-harness-pack:*, matilha-ux-pack:*, matilha-growth-pack:*) — detected at runtime via ambient skill list, referenced by name in the preamble, available for direct invocation downstream.docs/matilha/specs/<slug>-spec.mddocs/matilha/plans/<slug>-plan.mdproject-status.mdplanSchema.methodology/40-execucao.md.If matilha CLI is installed (
matilha --versionsucceeds), you can runmatilha plan <slug>to execute this deterministically. The plugin path above works without any CLI installation.