massa-th0th

Orchestrate memory-driven development workflows with th0th tool references and session routing.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill massa-th0th
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: massa-th0th
Source: https://github.com/luizgmassa/Useful-Agent-Skills/tree/main/skills/massa-th0th
Command: npx skills add https://github.com/luizgmassa/Useful-Agent-Skills --skill massa-th0th

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps agents deliver consistent engineering outcomes across sessions by providing a unified, memory-driven system that combines tool usage knowledge, session/workflow orchestration, and decision heuristics.

Core Features & Use Cases

  • Unified memory stack (meta-skill): Composes specialized sub-skills into one cohesive operating model for repeated development tasks.
  • Tool reference + orchestration: Ensures the agent uses th0th tools correctly while operating inside stable sessions.
  • Decision-grade reasoning: Applies structured engineering heuristics so debugging and trade-offs are justified and persist for future work.
  • Use case: When building or maintaining a codebase, load massa-th0th so the agent recalls prior decisions, routes work by intent, and persists root-cause explanations and patterns.

Quick Start

Load the massa-th0th skill and follow its loading order by reading the sub-skills’ SKILL.md files first, then execute your task using the prescribed session and recall/remember behavior.

Frequently Asked Questions about massa-th0th

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain engineering decisions across persistent agent sessions?▼

You can maintain engineering decisions across persistent agent sessions by using a memory-driven workflow that enforces strict sessionId reuse and conditionally persists root-cause explanations, trade-offs, and patterns for future recall.

What is a memory-driven development workflow for multi-agent handoffs?▼

A memory-driven development workflow for multi-agent handoffs orchestrates specialized sub-skills into a unified system, requiring recall-before-action and stable session routing to ensure consistent engineering outcomes across different agents.

How do I structure debugging heuristics to persist root-cause explanations?▼

Structure debugging heuristics to persist root-cause explanations by applying importance calibration rules that conditionally save engineering decisions and trade-offs into a compounding memory stack during your development workflow.

Does this agent orchestration workflow support ADR and TDD planning?▼

Yes, this agent orchestration workflow supports ADR and TDD planning by routing work by intent and applying structured engineering heuristics to justify trade-offs within stable, persistent development sessions.

When should I use a recall-before-action rule in software engineering sessions?▼

You should use a recall-before-action rule in software engineering sessions when executing debugging, refactors, or feature work to ensure the agent retrieves prior decisions and context before making new engineering changes.