메뉴
Use when completed subprojects are ready to merge — validates SP-DONE.md strict gates, merges --no-ff in merge_order, runs per-SP regression, updates wave-NN-status.md.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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 in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan.
| name | matilha-gather |
| description | Use when completed subprojects are ready to merge — validates SP-DONE.md strict gates, merges --no-ff in merge_order, runs per-SP regression, updates wave-NN-status.md. |
| category | matilha |
| version | 1.0.0 |
| optional_companions | [] |
After /matilha-hunt dispatched a wave and every SP has written a filled SP-DONE.md, the user wants to merge them back and verify regression. This skill is the inverse of /matilha-hunt: it consumes wave-NN-status.md, validates gates, merges in order, runs tests after each merge, and updates status.
docs/matilha/waves/wave-NN-status.md exists and validates against waveSchema.wave-NN-sp-*).SP-DONE.md passes strict gates.docs/matilha/waves/wave-NN-status.md via Read tool; validate against waveSchema.git rev-parse --abbrev-ref HEAD); verify clean tree (git status --porcelain).merge_order where status is not completed: validate <worktree>/SP-DONE.md strict gates (status=completed, tests.passed=true, non-empty commits[], non-null completed_at, tests.count>=1, sp_id/feature/wave match).--dry-run: emit merge plan preview and exit.git merge --no-ff <branch> via Bash; on conflict, run git merge --abort and HALT (5-rule error with conflicting files).npm test via Bash); on failure, HALT (5-rule error with git reset --hard <pre-merge-sha> recovery).--cleanup: for each completed SP, git worktree remove --force <path> + git branch -d <branch>.git merge --no-ff (preserve merge commits as wave markers).-d, not -D).On success, all SP branches merged into main in declared order + regression passed + wave-status updated. On failure, state preserved; 5-rule error with exact recovery commands.
status: completed.wave-NN-status.md always round-trips through waveSchema between updates..gitignore unchanged by gather.current_phase unchanged by gather.No companion integrations in Wave 4a. Review and quality delegation is Wave 3c's /matilha-review territory.
docs/matilha/waves/wave-NN-status.md (status, regression_status, started, ended, per-SP status).--dry-run first; commit wave-status after each gather; wait for wave to settle before --cleanup.--cleanup (opt-in); reset failed SP entry to pending after manual recovery to resume./matilha-hunt <slug> --wave N first.matilha hunt --force --wave N./matilha-hunt --force.git reset --hard <sha> (SHA in error output); fix regression; re-run /matilha-gather.git checkout main before retrying.If matilha CLI is installed (
matilha --versionsucceeds), you can runmatilha gather <slug>to execute this deterministically. The plugin path above works without any CLI installation.