m3o.sh

Manage structured communication files (PLAN.md, TODO.md, SPEC.md, etc.) to coordinate work across agents and sessions. Use when starting complex tasks, delegating to subagents, or maintaining project state.

Capture key decisions, pivots, and constraints discovered during work sessions. Use after architectural changes, before starting new PRDs when context has evolved, or when the user says "document this decision" or "remember this".

Interview the human-in-the-loop to clarify ambiguous requests before taking action. Use when the user's request is vague, missing key details, or has multiple valid interpretations. Do NOT use when the request is clear and unambiguous, or when the clarification can be resolved by reading code, docs, or a quick web search.

Read a tasks.json file, resolve the dependency graph, generate self-contained prompt files per task, and delegate every task to isolated tmux subagents. This skill NEVER implements code — it is a pure orchestrator. All work is done by pi subagents running in background tmux sessions.

Solve complex problems by spawning multiple specialized expert agents that analyze from different angles, then synthesize their insights. Use for architecture decisions, code reviews, complex debugging, or when you need comprehensive analysis.

Simulate Big Tech technical interviews for software engineers. Practice Coding (LeetCode-style), System Design, and Behavioral questions with feedback and coaching. Use when you want to practice for Big Tech interviews (Google, Meta, Amazon, Airbnb, etc.) or sharpen your interview skills. Do NOT use when you want live coding execution (this is for practice/feedback only) or when you need real company-specific questions (skill is company-agnostic).

Convert a Product Requirements Document (PRD) into a structured tasks.json file with tasks, dependencies, priorities, and estimated effort. Use when a PRD exists and the user wants to break it down into implementable tasks, or says "turn this into tasks," "create issues from the PRD," or "what are the next steps?" Do NOT use when there is no PRD or when the user wants to skip planning and start coding immediately.