Skip to content
Back to search

orchflows

2 skills, composable into workflows, which can then be built into more complex workflows

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/danmcinerney--orchflows/badge.svg)](/listings/danmcinerney--orchflows)

HTML

<a href="/listings/danmcinerney--orchflows"><img src="/api/listings/danmcinerney--orchflows/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Requires Python 3.11+ and an agent with native subagents, such as Codex or Claude Code. [Supported hosts](docs/hosts.md).

git clone https://github.com/DanMcInerney/orchflows.git
cd orchflows
python scripts/orchflows.py setup

Follow any host steps printed by setup, then start a new agent session.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 12 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "orchflows-local",
  3. "owner": {
  4. "name": "orchflows"
  5. },
  6. "plugins": [
  7. {
  8. "name": "orchflows",
  9. "source": "./"
  10. }
  11. ]
  12. }
README.md · README · 132 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # orchflows
  2. **Build an agent workflow once. Reuse it inside bigger jobs.**
  3. ## Install
  4. Requires Python 3.11+ and an agent with native subagents, such as Codex or Claude Code. [Supported hosts](docs/hosts.md).
  5. ```sh
  6. git clone https://github.com/DanMcInerney/orchflows.git
  7. cd orchflows
  8. python scripts/orchflows.py setup
  9. ```
  10. Follow any host steps printed by setup, then start a new agent session.
  11. ## Build your first workflow
  12. Make a **clear-writing** workflow. All you need is text to paste:
  13. > Use orch-build-workflow to create clear-writing: have a worker rewrite my text concisely, then have an independent reviewer check that the meaning and tone survived. Revise at most once to address the review, check the changes, and return the final text with any unresolved concerns separately.
  14. The [builder](skills/orch-build-workflow/SKILL.md) saves a Markdown skill in your personal library, rehearses it with sample text, and independently reviews it. It also checks host registration; follow any reported steps and start a new session to use it by name:
  15. > Use clear-writing. Keep this friendly and under 25 words: "Just wanted to check if you could possibly send me the draft by Friday so I can take a look before our meeting on Monday."
  16. Example result:
  17. > Could you send me the draft by Friday so I can review it before Monday's meeting?
  18. Next time, change the text, audience, or tone in your prompt. Reuse the same workflow.
  19. ## Try a dynamic workflow
  20. For a task you only need once:
  21. > Use orch-dynamic-workflow to develop three approaches to this message in parallel, combine the strongest ideas, then independently review and revise once if needed: "Our team should record meeting decisions."
  22. [Dynamic](skills/orch-dynamic-workflow/SKILL.md) assembles and runs a process for the current task. It adapts the work and review to the task; simple tasks can use a direct check unless you request independent review. If you also ask to save the process, it uses Build to author and test the reusable workflow.
  23. ## Why save the process?
  24. You find a process that works: split up the work, combine the results, get a second opinion, fix the issues. Then the next session starts, and you explain it all again.
  25. Orchflows saves those choices in editable Markdown: **what happens, what gets checked, and when to stop.** Your host runs the agents; orchflows supplies the reusable process.
  26. ## Put specificity where it belongs
  27. **Most task-specific detail belongs in the prompt.** Skills keep reusable steps. Root guidance docs hold shared standards; optional extension docs add increasingly specific preferences you want to reuse.
  28. ```mermaid
  29. flowchart TB
  30. P["PROMPT · this task<br/>Rewrite this customer email.<br/>Warm. Under 80 words.<br/>[paste email]"]
  31. subgraph G["GUIDANCE · standards across tasks"]
  32. direction TB
  33. B["Root guidance<br/>guidance/writing.md<br/>Lead with the point."]
  34. E["Optional extension<br/>writing.email.md<br/>One clear next action."]
  35. S["Narrower extension<br/>writing.email.support.md<br/>Acknowledge the issue."]
  36. B -->|specialize if useful| E -->|specialize further| S
  37. end
  38. subgraph W["SKILL · the same reusable process"]
  39. direction LR
  40. A[Rewrite] --> R[Independent review] --> F[Revise at most once] --> C[Check]
  41. end
  42. P -->|task and constraints| W
  43. G -.->|selected standards guide work and review| W
  44. classDef prompt fill:#dbeafe,stroke:#2563eb,color:#1e3a8a,stroke-width:2px;
  45. classDef guidance fill:#fef3c7,stroke:#b45309,color:#78350f,stroke-width:2px;
  46. classDef extension fill:#ffedd5,stroke:#c2410c,color:#7c2d12,stroke-width:2px;
  47. classDef work fill:#d1fae5,stroke:#059669,color:#064e3b,stroke-width:2px;
  48. classDef review fill:#ede9fe,stroke:#7c3aed,color:#4c1d95,stroke-width:2px;
  49. class P prompt;
  50. class B guidance;
  51. class E,S extension;
  52. class A,F work;
  53. class R,C review;
  54. style G fill:#fffbeb,stroke:#b45309,color:#78350f;
  55. style W fill:#eff6ff,stroke:#2563eb,color:#1e3a8a;
  56. ```
  57. The extension names above are examples you could add in your own library. A saved workflow selects only what applies: general writing → email → support email. Extensions refine shared standards; the current request still controls the task. [How guidance composes](DESIGN.md#how-does-guidance-compose).
  58. ## Start small. Compose upward.
  59. **1. Make something, then get an independent review.**
  60. ```mermaid
  61. flowchart LR
  62. W["orch-work<br/>Make a result"] --> R["orch-review<br/>Review the result"]
  63. classDef work fill:#d1fae5,stroke:#059669,color:#064e3b,stroke-width:2px;
  64. classDef review fill:#ede9fe,stroke:#7c3aed,color:#4c1d95,stroke-width:2px;
  65. class W work;
  66. class R review;
  67. ```
  68. These are the two primitives: [work](skills/orch-work/SKILL.md) launches a fresh maker; [review](skills/orch-review/SKILL.md) launches a fresh reviewer who did not make the result. The reviewer reports findings without changing it.
  69. **2. Work in parallel, then review the combined result.**
  70. ```mermaid
  71. flowchart LR
  72. A[Worker A] & B[Worker B] --> J[Combine]
  73. J --> R[Review once] --> F["Revise if needed<br/>at most once"] --> C[Check]
  74. classDef work fill:#d1fae5,stroke:#059669,color:#064e3b,stroke-width:2px;
  75. classDef review fill:#ede9fe,stroke:#7c3aed,color:#4c1d95,stroke-width:2px;
  76. class A,B,J,F work;
  77. class R,C review;
  78. ```
  79. The optional [shared library](https://github.com/DanMcInerney/orchflows/tree/main/example-workflows/shared) packages the last three steps as `shared:review-revise-once`. It stops after the checks, reporting anything unresolved.
  80. **3. Use whole workflows as steps in a bigger workflow.**
  81. ```mermaid
  82. flowchart LR
  83. subgraph U[Team update workflow]
  84. direction LR
  85. N["Extract decisions<br/>workflow"] --> D["Draft an update<br/>workflow"] --> C["clear-writing<br/>workflow"]
  86. end
  87. classDef workflow fill:#dbeafe,stroke:#2563eb,color:#1e3a8a,stroke-width:2px;
  88. class N,D,C workflow;
  89. style U fill:#eff6ff,stroke:#2563eb,color:#1e3a8a;
  90. ```
  91. Each box can contain the patterns above—or other workflows. Your **clear-writing** workflow keeps its review and revision steps when reused here. One coordinator connects the procedures and delegates the actual work.
  92. ## Go further
  93. - [Example libraries](https://github.com/DanMcInerney/orchflows/tree/main/example-workflows): research, software development, video, and improvement loops.
  94. - [Setup and updates](docs/home.md) · [Host support](docs/hosts.md) · [Model and effort settings](docs/architecture.md#model-and-effort).
  95. - [Design and built-ins](DESIGN.md) · [Library authoring](docs/libraries.md) · [Agent contracts](docs/architecture.md) · [Native history](docs/history.md).
  96. - [Behavior tests and evidence](https://github.com/DanMcInerney/orchflows/tree/main/tests/e2e) · [MIT license](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.