EveryInc

Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left…

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.

Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.

Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without…

Take a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when the user explicitly asks for autonomous end-to-end work or invokes lfg directly.…

Help and orientation for Compound Engineering: place the user's work on the compounding loop and recommend the next command, without running it. Use when the user invokes ce-help to ask which skill fits, what comes next, how setup, configuration, cost, or…

Check Compound Engineering health and repo-local config, scaffold a Compound Pack with `pack:<id>`, or draft or refresh coding standards and review docs with `standards`.

Run a multi-round deliberation between reviewers. Unlike /cw-panel (which synthesizes), /cw-debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.

Review a draft for big-picture issues in argument, structure, stakes, evidence, and payoff. Use when a piece needs developmental editing, a top-level diagnosis, or substantial restructuring before sentence polish.

Compose existing Compound Writing skills and runtime capabilities for open-ended writing outcomes that no single skill covers, such as cross-draft analysis, source-to-outline comparison, or multi-pass revision.

Generate 3 hook options tailored to your content. Invoke with /cw-hook or /cw-hook [topic/context].

Reads your writing through the meanest, least-charitable lens. Challenges every claim, questions every assumption, pokes holes in the logic. Use for later drafts when you want hard feedback.

Surfaces counterarguments, objections, and "yeah buts" a reader might have to your argument. Helps you anticipate and address resistance before it derails the piece.

Begin or refresh the separate VOICE.md, STYLE.md, and optional AUDIENCE.md guides in a writer's durable writing home from a short conversation, existing writing, or maintained context. Use during first-run writing-home setup and when the user wants to define,…

Convene a panel of reviewers to analyze a draft from multiple perspectives, then synthesize their feedback into consensus findings, productive tensions, and prioritized recommendations.

Plan and improve marketing strategy, launches, copy, and art direction using Every’s methods. Route to the smallest useful workflow and learn from approved edits without importing old campaign facts.

Audit an entire Every email campaign before final edits. Review current strategy, Notion and Slack decisions, reviewer comments, Kit performance, copy, cadence, and assets; return no more than 10 recommendations, obtain any missing approval, and apply…

Route brand and marketing copy through the smallest useful workflow: interview an incomplete brief, identify the persuasion job, develop a concept, draft, select one copywriter reviewer, and compound from meaningful edits when useful.

Coordinate brand and marketing work through Compound Strategy, Compound GTM, Compound Copywriting, or Compound Art Direction, using shared theory, source standards, brand context, and evidence-based learning.

Develop or revise brand and marketing strategy, positioning, audiences, messaging architecture, and program choices from evidence. Use before launch execution or creative production when the governing choices are unresolved.

Develop visual identities and assets, guide beginners through layout, typography and color, diagnose design problems, and improve future work from reviewed visual corrections.

Write and revise marketing copy across email, social, web, scripts, and campaigns; select the appropriate copywriter review and apply confirmed editing lessons to fresh work.

Turn approved strategy into a launch or campaign plan, distribution approach, lifecycle, calendar, social brief, or approval deck. Use for GTM execution and scoped revisions, not to rebuild settled positioning.

Reads your writing through the meanest, least-charitable lens. Challenges every claim, questions every assumption, pokes holes in the logic. Use for later drafts when you want hard feedback.

Run a multi-round deliberation between reviewers. Unlike /panel (which synthesizes), /debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.

Review a draft for big-picture issues—argument, structure, stakes, and payoff. Invoke with /dev-edit after drafting or with any draft the user provides.

Checks writing for clarity and accessibility. Flags jargon without explanation, hand-wavy process descriptions, and skipped steps. Ensures content is specific enough for experts AND clear enough for newcomers. Use when reviewing technical or process-heavy…

Scan any Every draft for recurring editorial-review failures: clarity and evidence gaps, argument problems, mechanics red flags, second-order AI tells, and, for Working Overtime only, column-specific voice tics and structural throat-clearing. Use when…

Cuts ruthlessly. Flags every adjective, adverb, and unnecessary word. Demands you kill your darlings.

Reviews for suspense and tension. Where's the bomb under the table? What does the reader know that someone doesn't?

Deep, rigorous pass for sentence- and word-level issues. Delivers a clean draft with a summary of changes. Invoke with /line-edit after dev-edit or with any draft.

Use when you need to read Monologue notes through the public API, search and list a user's notes, fetch a specific note, paginate through all notes, or pull transcripts, summaries, and original recording links through the Monologue CLI.

Clean a supplied transcript, transcript file, or verified Monologue note without changing its meaning. Use when a user wants to remove filler, stutters, repeated phrases, or abandoned false starts; improve punctuation and paragraphing; preserve speaker…

Turn a verified Monologue customer-call recording into evidence-backed product work, such as a bug report, issue draft, investigation brief, or implementation plan. Use when the user asks to connect customer feedback or a support call to a repository, issue…

Turn a recent Monologue morning note into a focused, evidence-backed work-session brief. Use when the user asks what to work on today, wants to start from a morning voice note, or wants decisions, questions, today's tasks, later ideas, and a recommended first…

Synthesize what a user has said about a topic across multiple Monologue notes, including the central thesis, examples, evolution, contradictions, gaps, and a dated source trail. Use when the user asks to find a theme across recordings, compare their thinking…

Process recent Monologue voice notes into a private, sourced inbox of decisions, tasks, ideas, questions, and people follow-ups. Use when a user wants to review recent recordings, clear a voice-note backlog, find commitments, or organize captured thoughts…

Draft an evidence-backed weekly work update from Monologue voice notes. Use when a user wants to review a week, summarize project progress and decisions, identify next steps, blockers, or owners, or prepare a status update from multiple recordings.

Brain dump and compile knowledge before structuring a plan. Use when starting any non-trivial knowledge work — after a meeting, when tackling a new problem, or when you need to pull together what you know before planning.

Extract and save learnings from a completed knowledge work session. Saves to docs/knowledge/ so future plans automatically find them.

Gut-check what you know and don't know before proceeding. Use at any point to assess confidence, surface gaps, and decide whether to proceed or dig deeper.

Research past work and structure a knowledge work plan. Use when starting strategy docs, campaign plans, content briefs, research synthesis, or operational playbooks.

Multi-reviewer quality check for knowledge work. Runs strategic alignment and data accuracy reviewers on plans, briefs, and strategy docs.

Execute a knowledge work plan. Break it into tasks, do the work, and track what happened. Use after planning to actually produce the deliverables.

Land a local PR by resolving conflicts and squash-merging the feature

Merge local `main` into the current branch and resolve merge conflicts

Finalize the local feature branch and create or update a local PR record on

Use the local `tasks` CLI to read/write `tasks.json` — the offline-demo replacement for Linear. Covers reading issues, posting/editing comments, transitioning issue state, attaching local PRs, and creating follow-up issues. Use when working a ticket through…

Create well-formed git commits from current changes. Use when staging and committing work-in-progress on the issue branch.

Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to…

Create a durable visual teaching artifact for something worth learning. Use when the user wants to be taught, wants a deep explainer, wants to understand a substantial change, or wants a work recap built for retention. Not for ordinary Q&A, operational…

Check Compound Engineering health and repo-local config.

Your AI CFO for bootstrapped startups, named after Charlie Munger who embodied the principle that capital discipline is a competitive advantage. Provides financial frameworks for cash management, runway calculations, unit economics (LTV:CAC), capital…

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes reading, analyzing, or extracting content from presentations; editing text, images, styles, or layout of existing decks; creating new slides, shapes,…

Arm this Claude session as Tend's Claude lane — open the feed in the in-app preview, register presence, and start the wake monitor so queued work activates this thread. Use when Dan says "/tend", "arm tend", "watch the feed", or opens Tend in the preview and…

Build polished product launch videos in Remotion from brief → storyboard → render → multi-agent review → iterate. Designed for 15-30s social clips for product launches, feature demos, and before/after transformations. Triggers on: product video, launch video,…