Overview

Break high-level goals into MEOWs (Molecular Expressions of Work), the atomic units in Gas Town. Each MEOW becomes a bead (git-backed work unit) or a wisp (ephemeral task), enabling clear boundaries, attribution, and parallel execution. This approach keeps work organized, traceable, and scalable across agents.

How This Skill Works

Analyze the goal and project context, identify natural seams for decomposition, and create MEOWs with clear boundaries and dependencies. Classify each MEOW as a bead (persistent) or a wisp (ephemeral), map dependencies to form a DAG, and estimate effort to set priorities. Beads are git-backed units and wisps are throwaway work; every MEOW supports attribution tracking.

When to Use It

• Before creating a convoy
• When a goal is too large for a single agent
• When parallel execution would benefit progress
• When work needs tracked attribution
• When dependencies and boundaries must be explicit

Quick Start

1. Step 1: Analyze the goal and project context
2. Step 2: Identify natural seams and create MEOWs with boundaries and dependencies
3. Step 3: Classify as beads or wisps, map dependencies, estimate effort, and set priorities

Best Practices

• Ensure each MEOW is completable by a single agent
• Design dependencies to form a DAG with no cycles
• Prefer many smaller beads over a few large ones
• Use wisps for scaffolding, exploration, or throwaway tasks
• Track attribution for every MEOW

Example Use Cases

• Decompose a software feature into MEOWs so multiple developers can work in parallel without conflicts
• Break a marketing campaign into BEADS for persistent tasks and WISPs for experimental tasks
• Structure a research project with core beads for foundational work and wisps for exploratory experiments
• Plan a product upgrade convoy with clear MEOW boundaries and dependency mapping
• Manage a refactor by creating a DAG of MEOWs to avoid cycles and ensure attribution

Frequently Asked Questions