kennykankush

autoreview

Auto Review closeout. Codex review is the default when no engine is set and is the recommended reviewer.

Live watcher mode for product/dev sweeps. Use when the user asks an agent to watch an app, tail logs, verify APIs/DB state, capture experience notes, track discrepancies, or act as a scribe/observer while they test a flow.

trail-scriber

Reconstruct day-by-day work trails from Codex and Claude conversation evidence into a durable agenda/domain graph. Use when the user asks to log what they did across dates, scan conversation history, update an Obsidian-style trail, or infer agendas from user messages.

storyboard

Create cohesive storyboard frames for product-launch and SaaS motion-graphics videos. Use when the user asks for storyboard frames, product-launch motion-design stills, AI-video-ready frame batches, Gemini/Omni/Higgsfield image batches, or wants screenshots converted into a polished launch-film sequence. Must be paired with Codex `$imagegen` / built-in image_gen for every generated frame.

memory-scriber

Capture a conversation's essence into the active host's memory directory, and recall it back like a colleague - not a database. Use at the tail end of a substantive session ("log this", "memory-scribe this"), progressively during one ("scribe as we go", "checkpoint this"), or in reverse when the user asks "where did we leave off", "what do you remember about this project", "pick up the thread". Supports Codex with a Workbench project-memory convention and Claude Code project memory without assuming the two plugin runtimes share state.

research-report

Run a deep research dive on any topic and either produce a polished Quarto HTML report (official mode — files written to research/<umbrella>/<title>/) or reply with structured findings inline (scan mode — no files). Use when the user invokes $workbench:research-report, /workbench:research, /workbench:scan, or says "research X for me", "do a deep dive on X", "give me a quick read on X", "what's the state of X", "scan X for me", "write up findings on X". Covers maximum surface area across web, Reddit, GitHub, ProductHunt, docs, papers, and any other available sources. Always converges output to exactly notes.md + report.html (official mode) or a structured chat reply (scan mode). Never proliferates files.

skill-advisor

Recommend which of the user's ALREADY-INSTALLED skills best fits a task or query. Use when the user asks "what skill should I use for X", "which of my skills fits this", "do I have a skill for Y", "what's at my disposal for Z", "recommend a skill from my toolkit", or when you need to pick the right skill from their available toolkit before starting work. This skill is read-only — it advises, it does not install. For installing new skills, use the separate skill-management workflow available in the current agent environment.

batch-prep

Prepare accepted storyboard frames for AI-video upload batches. Use when the user needs Omni/Gemini 10-image folders, Higgsfield 9-image groups, sequential copies, overlap frames, manifests, contact sheets, or prompt placeholders. File workflow only; does not creatively edit or generate frames.

frame-qa

Review generated storyboard frames or contact sheets for product-launch motion quality. Use when the user asks whether frames look professional, cohesive, AI-video-ready, faithful to screenshots, or should be regenerated. Outputs keep/regenerate decisions and targeted regeneration notes; does not manually edit frames.

launch-narrative

Shape a product-launch or SaaS motion-graphics video into a tight narrative spine before storyboard frame generation. Use when the user is deciding the hook, flow, duration, voiceover, feature emphasis, or ad rhythm for a launch film. Produces beats and frame direction, not generated images.

motion-handoff

Create AI-video motion handoff prompts and keyframe grouping plans from accepted storyboard frames. Use when the user has storyboard images and needs Higgsfield Canvas, Gemini/Omni, Runway, Krea, or another video model to understand frame order, motion intent, clip stitching, and UI stability constraints. Does not generate storyboard frames; pair with videos:storyboard only when new frames are still needed.

style-contract

Distill screenshots, brand assets, and motion references into a reusable visual style contract for storyboard or launch-video generation. Use when the user is sensitive about taste, cohesion, product-launch motion-graphic vibe, reference borrowing, logo fidelity, UI realism, or avoiding generic AI visuals.

devour

Enter codebase mastery mode before implementation. Use when the user asks to DEVOUR a repo or codebase, learn everything, deeply onboard, map architecture, trace runtime flows, understand blast radius, or build intuition about where and when things happen in a system. Persists its atlas to MAP.md at the repo root so later runs, bedrock, and potential start from the map instead of zero.

skill-distiller

Distill a successful chat, project workflow, repeated agent behavior, or a way of thinking into a reusable Codex or Claude skill. Use when the user wants to "skillify" a process, capture a reasoning/voice mode that just worked, create a new skill from what just worked, generalize a workflow without overfitting one project, or update a skillpack/plugin with reusable instructions.

bedrock

Foundation audit mode. Walk a codebase as an adversarial building inspector - stress-test load-bearing logic to bank-grade, limit-test feature flows by actually running them, and file a fragility report backed by runnable repros. Maintains an AUDIT.md ledger at repo root across runs. Use when the user asks to audit the foundations, check whether things are foundationally strong or flaky, run a bank-logic check, limit-test or stress-test features after a heavy build sprint, question the codebase from first principles, or harden what the audit found ("report and fix"). Two modes - report (default) and report-then-fix.

potential

See what a codebase wants to become. The generative counterpart to a foundation audit - read the existing structure and surface the features it already implies, the capacity it isn't using, and the doors it hasn't opened. Two modes - open ("what does this want to become?") and wish (the user brings "I wish it could X" and the structure answers whether and how it can grant it). Use when the user asks what could this become, squeeze the potential of this feature, what features want to be born, what's latent here, run potential, or starts a sentence with "I wish it could". A conversational thinking mode like isomorph - it never implements and never writes files.

vision

Keep a project's vision written down and alive. Creates and maintains VISION.md at the repo root - the statement of what the building is trying to be, which bedrock, potential, devour, and any implementing agent read before judging, dreaming, or building. Three moments - birth (carry a warroom-style exploration's distilled intent into a new project repo), backfill (a project already alive with no vision artifact - read the building, interview the visionary, write it), and refresh (the artifact has drifted from current intent - reconcile and update). Use when the user says write the vision, vision this project, this repo has no vision doc, the vision is stale, refresh the vision, backfill the vision, or wants to hand a project off from exploration into development.

Web & Frontend Listed

max-prompt

Turn vague feedback, screenshots, taste, frustration, or half-formed product intuition into an implementation-ready prompt for a coding agent. Use for UI/UX bugs, frontend polish, animation behavior, component architecture, and "it feels wrong but I don't know how to say it" moments.