Run any Skill in Manus with one click

matilha-howl

Stars1

Forks0

UpdatedApril 22, 2026 at 21:02

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.

Installation

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.

Run Skill in Manus

Source

danilods

danilods/matilha-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	matilha-howl
description	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.
category	matilha
version	1.0.0
optional_companions	[]

When this fires

User asks "where am I?", "what's next?", "what's the state?", or similar intent. Read-only; no mutations. Works at any phase.

Preconditions

None. matilha-howl lazy-bootstraps project-status.md stub when absent, then reports on the stub.

Execution Workflow

Check project-status.md. If missing, write a minimal stub (current_phase: 0, phase_status: not_started, project_slug: <cwd basename>, next_action: "Run matilha-scout to begin discovery, matilha-plan to plan a feature, or matilha-init for fuller bootstrap"). Then read it via Read tool.
Parse frontmatter.
Read any docs/matilha/waves/wave-*-status.md files via Glob + Read; summarize (how many active, completed, failed).
Emit a streaming section listing: current_phase, phase_status, next_action, active_waves, recent_decisions (last 3), blockers.
If current_phase === 40 and a wave is in_progress, surface per-SP status per wave.
End with the next_action prompt from project-status.md.

Rules: Do

Keep output concise (≤ 50 lines).
Prioritize next_action.
Surface blockers prominently.

Rules: Don't

Modify any file (read-only).
Guess next_action (use the one in project-status.md).
Over-summarize if there are many waves (show them all).

Expected Behavior

User reads output and knows exactly what to do next without further questions.

Quality Gates

Output mentions current_phase, phase_status, next_action.
Active and completed waves enumerated.

Companion Integration

No companion integrations in Wave 4a.

Output Artifacts

None (read-only).

Example Constraint Language

Use "must" for: read project-status.md.
Use "must not" for: modify any file.
Use "may" for: include relative-time labels like "3 days ago" for stale phases.

Troubleshooting

"project-status.md missing": Instruct user to run /matilha-init.
"frontmatter invalid": Instruct user to restore via matilha init --force or manual fix.

CLI shortcut (optional)

If matilha CLI is installed (matilha --version succeeds), you can run matilha howl to execute this deterministically. The plugin path above works without any CLI installation.

More from this repository

same repository

matilha-compose

danilods/matilha-skills

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.

2026-05-061

matilha-init

danilods/matilha-skills

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.

2026-05-051

matilha-bootstrap

danilods/matilha-skills

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.

2026-04-221

matilha-plan

danilods/matilha-skills

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.

2026-04-221

matilha-scout

danilods/matilha-skills

Use when user is in Phase 10 discovery for a feature — runs parallel research subagents and produces a research markdown that feeds matilha-plan.

2026-04-221

matilha-design

danilods/matilha-skills

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.

2026-04-221

name	matilha-howl
description	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.
category	matilha
version	1.0.0
optional_companions	[]

When this fires

User asks "where am I?", "what's next?", "what's the state?", or similar intent. Read-only; no mutations. Works at any phase.

Preconditions

None. matilha-howl lazy-bootstraps project-status.md stub when absent, then reports on the stub.

Execution Workflow

Check project-status.md. If missing, write a minimal stub (current_phase: 0, phase_status: not_started, project_slug: <cwd basename>, next_action: "Run matilha-scout to begin discovery, matilha-plan to plan a feature, or matilha-init for fuller bootstrap"). Then read it via Read tool.
Parse frontmatter.
Read any docs/matilha/waves/wave-*-status.md files via Glob + Read; summarize (how many active, completed, failed).
Emit a streaming section listing: current_phase, phase_status, next_action, active_waves, recent_decisions (last 3), blockers.
If current_phase === 40 and a wave is in_progress, surface per-SP status per wave.
End with the next_action prompt from project-status.md.

Rules: Do

Keep output concise (≤ 50 lines).
Prioritize next_action.
Surface blockers prominently.

Rules: Don't

Modify any file (read-only).
Guess next_action (use the one in project-status.md).
Over-summarize if there are many waves (show them all).

Expected Behavior

User reads output and knows exactly what to do next without further questions.

Quality Gates

Output mentions current_phase, phase_status, next_action.
Active and completed waves enumerated.

Companion Integration

No companion integrations in Wave 4a.

Output Artifacts

None (read-only).

Example Constraint Language

Use "must" for: read project-status.md.
Use "must not" for: modify any file.
Use "may" for: include relative-time labels like "3 days ago" for stale phases.

Troubleshooting

"project-status.md missing": Instruct user to run /matilha-init.
"frontmatter invalid": Instruct user to restore via matilha init --force or manual fix.

CLI shortcut (optional)

If matilha CLI is installed (matilha --version succeeds), you can run matilha howl to execute this deterministically. The plugin path above works without any CLI installation.