← ClaudeAtlas

oogwaylisted

Compact, causally-linked status report on the last round of agent work — what shipped and whether it was any good, why the agent stopped, which past change caused each current problem, what hasn't broken yet but will, and what to do next with its payoff and trade-offs. Use when the user runs /oogway, or asks "what did you just do", "why did you stop", "where are we", "what's the status", "review the last round", "what's next / is it worth doing", "what could go wrong", "why is this broken", or wants a standup, weekly update, or handoff doc.
tensorboy/oogway · ★ 0 · Code & Development · score 65
Install: claude install-skill tensorboy/oogway
# oogway > **"There are no accidents."** Three sections, bound by that one rule: - **📜 Past — yesterday is history.** What shipped, and an honest review of it. Not commit titles: read the diffs, grade each change, name what it planted. - **🎁 Current — today is a gift.** Where things stand. **Every problem traced back to the change that caused it.** - **🌫️ Future — tomorrow is a mystery.** Unless you price it. Every item traced forward to the payoff it produces and when that payoff lands. These are not three lists side by side. They are one causal line read in one direction: - A problem in **Current** with no cause in **Past** is unexplained. There are no accidents — go find the cause, or say out loud that you couldn't. - An item in **Future** with no driver in **Current** is a wish. Cut it, or justify it. The report is not finished when three sections are written. It is finished when **the chain closes**. Write it for "you tomorrow morning," or for the person taking this over. ## Arguments `/oogway [scope] [--save]` | Argument | Meaning | | |---|---|---| | *(none)* | **The last turn** — what the agent just did, why it stopped, what it left behind | ← default | | `session` | The whole conversation, not just the last turn | | | `7d` / `2w` / `1m` | Widen to a git-history window | | | `<path>` | Focus on one subdirectory / module | | | `--save` | Also write `docs/progress/YYYY-MM-DD.md` | | **The default is one turn: from the user's most recent message until now.**