Deskarden
WORKFLOW LIBRARY

A useful process.
Ready to repeat.

Choose an outcome, give it the right source material and keep a review step where judgment matters.

6 workflows shown.

Research

A brief with its evidence attached.

Turn a selected source set into a structured brief, with findings, citations and unanswered questions.

Inputs, steps and outputs
Bring
A project question, source documents and a desired format.
  1. Reader collects relevant passages and records their locations.
  2. Analyst groups evidence and highlights conflicting findings.
  3. Editor drafts a brief with sources and open questions.
  4. You review claims and accept the final document.
Keep
A brief, source index and open-question list.
Access
Read selected project files; write a draft. Web research is a separate opt-in permission.
Operations

A sensible home for incoming documents.

Extract useful details and propose a project destination without losing the original file.

Inputs, steps and outputs
Bring
Incoming PDF, text or Markdown documents and your project naming rules.
  1. Reader extracts the text and key fields.
  2. Analyst suggests tags, a project and a useful filename.
  3. The workflow stages a summary and proposed changes.
  4. You approve the destination and keep the source.
Keep
A proposed filing record and a short document summary.
Access
Read incoming documents; stage metadata. Moving or replacing a file requires approval.
Writing

A weekly update without the archaeology.

Bring together completed work, decisions and blockers into a clear status update.

Inputs, steps and outputs
Bring
Selected project activity, accepted outputs and the reporting period.
  1. Reader collects changes within the selected period.
  2. Analyst groups progress, decisions and unresolved blockers.
  3. Editor drafts an update with links to the underlying work.
  4. You check tone and completeness before sharing.
Keep
A concise update and a linked action list.
Access
Read the selected project; write a draft. Sending the update is a separate action.
Research

Compare proposals on the same terms.

Apply one evaluation framework to several proposals, then inspect the evidence behind each difference.

Inputs, steps and outputs
Bring
Proposal documents, evaluation criteria and your priorities.
  1. Reader extracts each proposal against the same criteria.
  2. Analyst builds a comparison and flags omissions.
  3. Editor summarizes tradeoffs and questions to ask.
  4. You confirm the evidence and decide the next step.
Keep
A comparison table, decision note and clarification questions.
Access
Read the selected proposals; write comparison drafts. No automatic selection or commitment.
Operations

Make the next steps easy to find.

Turn supplied meeting notes or a transcript into decisions, owners and follow-up tasks.

Inputs, steps and outputs
Bring
A text transcript or meeting notes plus the project’s terminology.
  1. Reader separates decisions from discussion.
  2. Analyst extracts tasks and flags unclear ownership.
  3. Editor prepares a recap and proposed action list.
  4. You confirm names, commitments and due dates.
Keep
A meeting recap and reviewed action list.
Access
Read supplied text and stage tasks. Assigning or notifying people requires approval.
Writing

Package the work for the next person.

Prepare a handoff that explains what is included, what changed and what still needs attention.

Inputs, steps and outputs
Bring
Accepted project outputs, a handoff checklist and the intended reader.
  1. Reader inventories the selected deliverables.
  2. Analyst checks completeness against the checklist.
  3. Editor prepares an index and handoff note.
  4. You approve the package and choose how to share it.
Keep
A deliverable index, handoff note and outstanding-item list.
Access
Read accepted outputs; create a new draft package. No external sharing without approval.
MAKE IT YOUR OWN

Templates are a start.
Your process is the point.

Change the instructions, source selection and review requirements to fit the way you work. Save that combination as a reusable project workflow.

Start with a small source set and a clear output. A workflow is easier to trust when you can inspect what each step contributed.

  1. Define the input

    Specify the files, questions and fields the workflow needs.

  2. Connect the steps

    Choose agent roles, dependencies and where a person must review.

  3. Define “finished”

    Give the result a format, a destination and a clear acceptance check.

Keep the good process.

Understand run states, review points and what to do when a task needs attention.

Read the guide ↗