CentraLearn Centra AI
Getting startedCapabilitiesToolsWorkflowsTrust & safetyResourcesReference

Workflow recipes

Available broadlyLast reviewed This page covers: End-to-end recipes that combine capabilities into a finished deliverable, each with a starter prompt.
View as markdown

Single capabilities are useful; combining them is where Neo replaces a process rather than a step. Each recipe below runs end to end—from raw input to reviewed deliverable—with the checkpoints that keep you in control. Copy the starter prompt, replace the bracketed parts, and adjust the approval points to your risk level.

Every recipe follows the same skeleton: input → transformation → checkpoint → deliverable. The checkpoint is not optional; it is where your judgment enters the loop.

Meeting notes → decision memo

Turn raw notes into a memo that records what was decided, by whom, and what happens next.

  1. Provide the notes and name the decision-makers and audience.
  2. Neo separates decisions, action items, open questions, and context.
  3. Review the decision list first—wrong attributions are the common failure.
  4. Approve the structure, then receive the finished memo.
Try this

Turn the attached meeting notes into a one-page decision memo. List each decision with its owner and rationale, then action items with owners and dates, then open questions. Flag anything ambiguous in the notes rather than guessing. Show me the decision list for confirmation before writing the full memo.

Research → recommendation

Move from an open question to a defensible recommendation with visible evidence.

  1. State the decision, the options, the criteria, and the freshness requirement.
  2. Neo researches with sources cited close to each claim.
  3. Review the evidence table and adjust criterion weights.
  4. Receive a recommendation with the strongest counterargument stated.
Try this

I need to choose between [option A] and [option B] for [purpose]. Research both using sources from the last 12 months, prioritizing primary sources. Build a comparison against these criteria: [criteria]. Cite every material claim, state the research cutoff, then recommend one option and give the strongest case for the other.

Uploaded spreadsheet → executive briefing

Convert a raw data file into a short briefing a decision-maker can act on.

  1. Upload the file and state what decision the briefing supports.
  2. Neo profiles the data first: row counts, ranges, gaps, and anomalies.
  3. Confirm the data reading is correct before any narrative is written.
  4. Receive a one-page briefing: headline findings, supporting figures, caveats.
Try this

Analyze the attached spreadsheet. First report what the data contains—columns, row count, date range, missing values, and anything anomalous—and wait for my confirmation. Then produce a one-page executive briefing with three headline findings, the figures that support each, and the caveats a careful reader should know. State every assumption you made about the data.

Issue description → code change → tests → review

Take a bug or feature request through implementation with evidence at every step.

  1. Provide the issue and the repository scope; Neo reproduces or traces first.
  2. Approve the diagnosis before any edit.
  3. Neo makes the smallest change plus targeted tests, and runs the project's checks.
  4. Review the diff and the test output—not just the summary of them.
Try this

Here is the issue: [description]. Investigate and reproduce it before changing anything, and show me your diagnosis of the cause. After I confirm, implement the smallest fix, add a test that fails without the fix and passes with it, run the project's existing checks, and show me the full diff with the test output.

Inbox backlog → prioritized draft responses

Clear a communication backlog without surrendering the send button.

  1. Neo reads the backlog (where messaging access is connected) or you paste it.
  2. Messages are triaged: needs your decision, routine reply, no action.
  3. Review the triage—especially what was marked "no action."
  4. Neo drafts the routine replies; everything remains draft only until you send.
Try this

Triage these messages into three groups: needs my decision, routine reply I can delegate, and no action needed. Show me the triage with one line of reasoning per message. After I confirm, draft the routine replies in my voice—direct, warm, brief. Do not send anything; leave every message as a draft for my review.

Rough idea → project plan → milestones

Turn an intention into a plan with owners, sequence, and checkpoints.

  1. Describe the outcome, the constraints, and who is involved.
  2. Neo drafts scope: what is in, what is explicitly out, and open assumptions.
  3. Confirm scope before planning—plans built on wrong scope waste the effort.
  4. Receive milestones with dependencies, rough estimates, and review points.
Try this

Help me turn this idea into a project plan: [idea]. First propose the scope—what is included, what is explicitly excluded, and the assumptions you are making—and wait for my corrections. Then produce milestones with dependencies, rough time estimates, the risks most likely to cause slippage, and a checkpoint after each milestone where I review before work continues.

Article or URL → structured knowledge page

Preserve a source as organized knowledge instead of a link you will lose.

  1. Provide the URL or paste the text; state why it matters to your work.
  2. Neo extracts claims, evidence, entities, and open questions—separated, not blended.
  3. Review the claims list against the source.
  4. The result is saved as structured knowledge (where available) or delivered as an artifact you file yourself.
Try this

Read this article: [URL]. Produce a structured knowledge page with: a three-sentence summary; its key claims each with the supporting evidence; entities mentioned and their roles; how it relates to [my project/topic]; and open questions it raises. Distinguish what the article demonstrates from what it merely asserts. Keep the source link and publication date at the top.

Adapt a recipe

To build your own, keep the skeleton and change the parts: define the input and the source of truth, name the transformation, place a checkpoint before anything expensive or hard to reverse, and specify the deliverable's audience and format. The use cases page covers scoping single requests; long-running work covers recipes that outlive one conversation.

Was this page helpful?
Edit this page
PreviousUse casesNext Trust, privacy, and safety