oroshi

Use when writing or modifying ZSH functions.

Use when user says "ralph <dir>" or "ralph this". Implements the highest-priority issue from state.json in the given directory using TDD, updates docs, runs review in a subagent, fixes actionable feedback, then stops for user to commit. Argument is the directory containing state.json and GUIDANCE.md.

Use when user says "sidequest". Compact conversation context into a document for a fresh agent to pick up.

Use when writing or modifying JavaScript code. Apply when adding functions, fixing bugs, or implementing features.

Use when writing or modifying Python code. Apply when adding functions, fixing bugs, or implementing features.

Use when creating or updating skills.

Use when user says "phone pickup", "pick up the conversation from the phone", "récupère la discussion du téléphone", or wants to retrieve a mobile vocal session saved in Notion.

Use when writing throw-away debug or exploration scripts.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Implement a solution agreed upon in a grill-me session. Use when the user picks "quick implementation" after a grill-me.

Use when the user wants to nail down domain terms, resolve terminology ambiguities, or build a shared language for a module or repo. Drills vocabulary one question at a time and writes to the project GLOSSARY.md.

Use when the user wants to review a slide screenshot for design quality. Triggers on "review slide", "slide review", "review this slide". Evaluates the slide against design principles across 4 axes (Grouping, Readability, Colors, Spacing) using parallel sub-agents.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". Reviews changes along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match the originating issue/PRD?). Runs both axes as parallel sub-agents and reports them side by side.

Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.

Used when user wants to build features or fix bugs using TDD or red-green-refactor loop.

Crafts compelling conference CFP submissions (title, abstract, takeaways). Use when user needs to write a Call for Paper, submit a talk proposal, or transform existing content into conference-ready format.

Use when writing or modifying code in any programming language. Apply when adding functions, fixing bugs, or implementing features.

Use when user needs to write Slack announcement messages but struggles with tone, length, or call-to-action. Triggers include 'help me write a Slack message', sharing personal projects, announcing meetups/events, or posting article links.