factoryhub 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,16 @@
+factoryhub
+Copyright Mindburn Labs
+
+This product is licensed under the Apache License, Version 2.0 (LICENSE),
+with two exceptions:
+
+- The factories in factories/ each declare their own license in their
+  flow.yaml. The eight house factories declare MIT.
+- The ClawHub skill files in integrations/openclaw/factoryhub/ (SKILL.md and
+  README.md) are released under MIT No Attribution (MIT-0), because ClawHub
+  publishes every skill under MIT-0. Their README holds the license text.
+
+The factoryhub name and the artwork in assets/ (and its copy in
+integrations/claude-code-plugin/assets/) identify this project. As
+section 6 of the Apache License says, the license grants no permission to use
+them except to describe where the work comes from.

package/README.md

@@ -1,3 +1,190 @@
-# Temporary Holding Version
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="assets/factoryhub-horizontal-inverse.svg">
+    <img alt="factoryhub. AI factories, shared. Find a factory. Make it yours." src="assets/factoryhub-social-1200x630.png" width="720">
+  </picture>
+</p>
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+<h3 align="center">AI factories, shared.</h3>
+
+<p align="center">
+  The open format, engine, command line and MCP server for AI factories:<br>
+  small teams of AI agents written as plain files that anyone can read, run, change and share.
+</p>
+
+<p align="center">
+  <a href="docs/quickstart.md">Quickstart</a> ·
+  <a href="docs/README.md">Docs</a> ·
+  <a href="spec/factory-format.md">Spec</a> ·
+  <a href="#the-house-factories">Factories</a> ·
+  <a href="integrations/README.md">Integrations</a> ·
+  <a href="CONTRIBUTING.md">Contributing</a>
+</p>
+
+<p align="center">
+  <a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue"></a>
+  <img alt="Node.js 22 or newer" src="https://img.shields.io/badge/node-%E2%89%A522-339933">
+  <a href="spec/factory-format.md"><img alt="Format: v1alpha1" src="https://img.shields.io/badge/format-v1alpha1-orange"></a>
+</p>
+
+## What a factory is
+
+A factory turns what a person gives into a finished, checked document. It
+says who does what, in what order, what gets checked, and where the person
+decides, in three kinds of plain files:
+
+```text
+meeting-to-actions/
+  factory.yaml              name and what it is for
+  flow.yaml                 inputs and steps
+  agents/<name>/agent.md    one role per agent
+```
+
+Here is part of a real one, [`factories/meeting-to-actions/flow.yaml`](factories/meeting-to-actions/flow.yaml),
+with some fields left out and its task texts shortened:
+
+```yaml
+flow: mindburn.flow/v1
+title: Meeting to actions
+version: "1.1.1"
+inputs:
+  notes:
+    type: longtext
+    help: "The meeting notes or transcript, as rough as they are."
+steps:
+  extraction:
+    title: Extract what was agreed
+    agent: analyst
+    kind: work
+    task: |
+      Read the notes and pull out four lists. Decisions: ...
+  followup:
+    title: Write the follow-up
+    agent: writer
+    kind: deliver
+    needs: [extraction]
+    task: |
+      Write the follow-up. Sections, in this order: ...
+  check_extraction:
+    title: Check against the notes
+    agent: reviewer
+    kind: check
+    needs: [followup]
+    checks: followup
+    task: |
+      Compare the entire follow-up with the original notes. ...
+```
+
+Steps run in the order their `needs` allow, in parallel where they can. A
+`check` sends weak work back to be redone. An `approve` step stops the run
+until the person decides; nothing decides for them unless they ask for it
+with `--yes`. Every finished run
+writes a receipt: the hash of the factory, every step, every check verdict,
+every decision and the deliverable. [Concepts](docs/concepts.md) explains the
+parts; [the spec](spec/factory-format.md) has every field.
+
+## Quickstart
+
+You need Node.js 22 or newer and git.
+
+```sh
+git clone https://github.com/Mindburn-Labs/factoryhub && cd factoryhub
+npm ci
+npx factoryhub inspect meeting-to-actions
+```
+
+Then run it with your own model key, or a model on your machine:
+
+```sh
+export ANTHROPIC_API_KEY=...        # or OPENAI_API_KEY, or OPENROUTER_API_KEY
+npx factoryhub run meeting-to-actions -i notes=@notes.txt
+
+npx factoryhub run meeting-to-actions --provider ollama --model <model>
+```
+
+Make your own with `npx factoryhub new my-factory`; it validates and runs from
+the start. More in the [quickstart](docs/quickstart.md).
+
+## What is in this repository
+
+| Part | What it does |
+|---|---|
+| [`spec/`](spec) | The factory format v1alpha1: a readable [specification](spec/factory-format.md), JSON Schemas for `factory.yaml` and `flow.yaml`, conformance fixtures that test the schemas against the engine, the [skill export](spec/skill-export.md) mapping, and an [RFC process](spec/rfcs/README.md). |
+| [`packages/engine`](packages/engine) | The engine with no dependencies: parses a factory, runs its flow on Anthropic or any OpenAI-compatible model, writes and verifies receipts. The factoryhub site runs the same engine code. |
+| [`packages/cli`](packages/cli) | `factoryhub`: `list`, `inspect`, `validate`, `run`, `resume`, `new`, `pack`, `export --as skill`, `search`, `get`. [Reference](docs/cli.md). |
+| [`packages/mcp`](packages/mcp) | A local stdio MCP server: list, read, validate, export and run factories from any MCP client. Runs stop at every decision and resume with the person's answer. [Reference](docs/mcp.md). |
+| [`factories/`](factories) | The house factories, each checked by `npm run validate` and the CI workflow, with a generated [`index.json`](factories/index.json). |
+| [`integrations/`](integrations) | An Agent Skill, a Claude Code plugin, OpenClaw and Hermes Agent skills, MCP client entries, and nine examples for seven agent frameworks. |
+
+## The house factories
+
+<!-- factories:start -->
+<!-- Generated by scripts/generate.mjs from factories/. -->
+
+| Factory | What it does | Inputs required | Steps | Asks you to approve | Web tools |
+|---|---|---|---|---|---|
+| [`client-file-readiness`](factories/client-file-readiness) | Compares what a client sent against your checklist, reports what is missing, from the wrong period or unclear, and drafts the message asking for it. | 3 of 4 | 3 | no | none |
+| [`competitor-teardown`](factories/competitor-teardown) | Reads your website and up to three competitors, then writes a decision-ready brief showing where you win, where you lose and what to change this week. | 2 of 3 | 5 | no | web_fetch, web_search |
+| [`homepage-audit`](factories/homepage-audit) | Reads your home page the way a first-time visitor does and returns a prioritised list of fixes with the exact new wording. | 1 of 3 | 4 | no | web_fetch |
+| [`inbox-triage`](factories/inbox-triage) | Sorts a batch of customer messages by urgency and type, drafts a reply to each in your tone, and lists what needs a human decision. | 2 of 3 | 4 | no | none |
+| [`launch-kit`](factories/launch-kit) | Turns a product description into a launch kit with positioning, a landing page draft, a launch email, three follow-ups and posts for social channels, all in one voice. | 2 of 5 | 6 | yes | web_fetch |
+| [`meeting-to-actions`](factories/meeting-to-actions) | Turns rough meeting notes or a transcript into decisions, owned actions with dates, open questions and a follow-up message ready to send. | 1 of 2 | 3 | no | none |
+| [`outreach-pack`](factories/outreach-pack) | Turns checked market research and launch materials into an outreach pack. | 2 of 3 | 3 | no | none |
+| [`prospect-brief`](factories/prospect-brief) | Researches one company you want to sell to and writes a one-page brief plus a first email and follow-up that mention real, checkable facts about them. | 2 of 3 | 7 | yes | web_fetch, web_search |
+
+<!-- factories:end -->
+
+Add yours: [a factory in five minutes](CONTRIBUTING.md#add-a-factory-in-five-minutes).
+
+## Use it from your agent
+
+Each integration is marked with what was actually tested at this commit.
+"Tested locally" means exercised on a maintainer's machine with the version
+and result recorded in the [status matrix](integrations/README.md#status);
+"documented only" means written from the tool's current docs and not
+exercised. CI has not run yet, so nothing is marked "tested in CI".
+
+| Where | How | Status |
+|---|---|---|
+| Claude Code | [plugin](integrations/claude-code-plugin) with the skill and the MCP server | tested locally |
+| Gemini CLI | [MCP entry](integrations/mcp-clients/gemini.settings.json) | tested locally |
+| Codex | [MCP entry](integrations/mcp-clients/codex.config.toml) | documented only |
+| Cursor | [MCP entry](integrations/mcp-clients/cursor.mcp.json) | documented only |
+| VS Code | [MCP entry](integrations/mcp-clients/vscode.mcp.json) | documented only |
+| Claude Desktop | [MCP entry](integrations/mcp-clients/claude-desktop.json) | documented only |
+| OpenClaw | [skill](integrations/openclaw/factoryhub/SKILL.md) | tested locally (`skills-ref` validator) |
+| Hermes Agent | [skill](integrations/hermes/factoryhub/SKILL.md) | tested locally (its parser, validator and skills guard) |
+| Any agent that reads skills | [Agent Skill](integrations/agent-skills/factoryhub/SKILL.md), or `factoryhub export --as skill` | tested locally (`skills-ref` validator) |
+| Vercel AI SDK, OpenAI Agents SDK (JS and Python), LangChain (JS and Python), smolagents, Hugging Face, CrewAI, LlamaIndex | [framework examples](integrations/frameworks) over MCP | listing tools: tested locally; agents: documented only |
+
+Setup for each: [docs/integrations.md](docs/integrations.md).
+
+## factory.mindburn.org
+
+Mindburn Labs runs a hosted factoryhub at factory.mindburn.org, currently in
+private preview. `factoryhub search` and `factoryhub get` read its published
+catalogue; while the preview lasts they need the access key you were given,
+in `FACTORYHUB_ACCESS_KEY`. Everything else in this repository works without
+it.
+
+## Contributing
+
+Contributions are welcome: factories, fixes, docs, integrations and format
+proposals. Start with [CONTRIBUTING.md](CONTRIBUTING.md). Changes to the
+format go through [RFCs](spec/rfcs/README.md). The [roadmap](ROADMAP.md) lists
+what comes next.
+
+## Community
+
+- [Code of Conduct](CODE_OF_CONDUCT.md)
+- [Governance](GOVERNANCE.md)
+- [Getting help](SUPPORT.md)
+- [Security](SECURITY.md): report vulnerabilities privately
+- [Changelog](CHANGELOG.md)
+
+## License
+
+[Apache-2.0](LICENSE). Each factory declares its own license in its
+`flow.yaml`; the house factories declare MIT. The ClawHub skill files in
+[`integrations/openclaw/factoryhub`](integrations/openclaw/factoryhub) are
+MIT-0, as ClawHub requires. See [NOTICE](NOTICE).

package/factories/README.md

@@ -0,0 +1,17 @@
+# House factories
+
+The factories that ship with factoryhub. `factoryhub list` lists them,
+`factoryhub inspect <id>` explains one, and [`index.json`](index.json) is the
+generated catalogue with each factory's hash.
+
+These folders hold the same source files the factoryhub site has for these
+factories. With the foreman the engine writes from each flow, their hashes
+match the site's. Their own READMEs were written for the site: where one says
+to run an example "on the Hub", that means factory.mindburn.org, which is in
+private preview. Cost figures in a `mindburn.requirements.yaml` are the
+author's estimates from hosted trial runs and were not measured in this
+repository; run the examples yourself with `node run.mjs --test` in a packed
+factory.
+
+To add a factory, see
+[CONTRIBUTING.md](../CONTRIBUTING.md#add-a-factory-in-five-minutes).

package/factories/client-file-readiness/README.md

@@ -0,0 +1,3 @@
+# Client-file readiness
+
+Know what is missing before you start the work. Paste your checklist and the list of what the client sent. You get a clear status for every item and one polite message to the client that asks for everything outstanding in a single round.

package/factories/client-file-readiness/agents/analyst/agent.md

@@ -0,0 +1,10 @@
+---
+description: Turns raw material into structured findings that can be checked.
+agentType: CUSTOM
+---
+
+You are the analyst. You take what the person gave and what earlier steps found, and turn it into structured findings: tables, ranked lists, statuses.
+
+- Every finding points at the exact words, file or fact it rests on.
+- You never assume what the material does not show. Where something cannot be told, you say what is missing.
+- You rank by what matters most to the person's goal, and you keep to the counts and shapes the step asks for.

package/factories/client-file-readiness/agents/reviewer/agent.md

@@ -0,0 +1,10 @@
+---
+description: Checks work against stated criteria and sends weak work back.
+agentType: REVIEW
+---
+
+You are the reviewer. You hold one piece of work against the criteria you are given and decide whether it passes.
+
+- You judge only what is on the page and only against the stated criteria.
+- You fail work for a clear, specific breach you can point to. You never fail it for taste, or for something nobody asked for.
+- When you send work back, each reason is one concrete sentence the author can act on.

package/factories/client-file-readiness/agents/writer/agent.md

@@ -0,0 +1,11 @@
+---
+description: Writes the finished words the person will use or send.
+agentType: CUSTOM
+---
+
+You are the writer. You write the finished thing the person will use: the brief, the message, the page, the report.
+
+- Plain words, short sentences, the reader's own vocabulary. No filler and no hype.
+- You keep to the sections, word limits and order the step asks for.
+- You add no fact that is not in the inputs or earlier results. Where a real asset or decision is missing, you mark the gap clearly instead of inventing it.
+- What you write should be usable as it stands.

package/factories/client-file-readiness/factory.yaml

@@ -0,0 +1,12 @@
+schemaVersion: v1alpha1
+name: client-file-readiness
+description: |
+  Compares what a client sent against your checklist, reports what is missing,
+  from the wrong period or unclear, and drafts the message asking for it. Use
+  before starting bookkeeping, tax, audit, onboarding or any work that depends
+  on a client's documents.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet

package/factories/client-file-readiness/flow.yaml

@@ -0,0 +1,56 @@
+flow: mindburn.flow/v1
+title: Client-file readiness
+author: Mindburn Labs
+version: "1.1.0"
+license: MIT
+tags: [operations, accounting]
+time: about 2 minutes
+inputs:
+  checklist:
+    type: longtext
+    help: "The documents you need, one per line, with the period where it matters. For example \"Bank statements, all accounts, January to March 2026\"."
+  received:
+    type: longtext
+    help: "What the client sent: file names, with any notes you have on their contents. Paste the list as it is."
+  client_and_period:
+    type: text
+    help: "The client's name and the period of the work, for example \"Dunmore Bakery, Q1 2026\"."
+  deadline:
+    type: text
+    optional: true
+    help: "When you need the missing items by."
+steps:
+  matching:
+    title: Match files to the checklist
+    agent: analyst
+    kind: work
+    task: |
+      Go through the checklist one line at a time. For each line find the received files that could satisfy it, judging by name, dates and notes. Give each checklist line one status: Complete, Partly received (say exactly what part is missing, such as a month or an account), Wrong period (say which period was sent), Unclear (say what you cannot tell from the file name) or Missing. Show a table with columns: Checklist item, Status, Matching files, What is still needed.
+
+      Then list any received files that match nothing on the checklist. Do not assume a file contains something its name and notes do not show.
+  report:
+    title: Write the readiness report
+    agent: writer
+    kind: deliver
+    needs: [matching]
+    task: |
+      Write the report for the person doing the work. Sections, in this order:
+
+      1. **Ready to start?** Yes, No or Partly, in one sentence with the count of complete items out of the total.
+      2. **Status of every item**: the table.
+      3. **What you can start now**: the work that the complete items already allow.
+      4. **Message to the client**: a short, friendly message addressed to the client, ready to send, that lists every outstanding item as a numbered list in plain words, says exactly which period or account is needed, and gives the deadline if one was provided. One message, one round.
+      5. **Files we could not place**: the unmatched files, with a question to ask about each.
+  check_matching:
+    title: Check the readiness report
+    agent: reviewer
+    kind: check
+    needs: [report]
+    checks: report
+    task: |
+      Judge only from the supplied file names and notes. Every checklist line appears exactly once with one of the five statuses. Every Complete item names received files indicating the full requested period; no file is counted for a contradictory period. Unmatched files are not also matched. Counts and readiness agree with the table. The client message asks for every outstanding item, excludes complete items, and uses only the supplied deadline.
+
+done:
+  - "Every checklist item has exactly one status."
+  - "The client message asks for everything outstanding and nothing already received."
+  - "Nothing is marked complete on a guess."

package/factories/competitor-teardown/README.md

@@ -0,0 +1,3 @@
+# Competitor teardown
+
+Give it your website and the competitors you worry about. It reads what each company actually says in public, compares offer, pricing, proof and positioning side by side, and tells you what to change. Every claim links to the page it came from.

package/factories/competitor-teardown/agents/analyst/agent.md

@@ -0,0 +1,10 @@
+---
+description: Turns raw material into structured findings that can be checked.
+agentType: CUSTOM
+---
+
+You are the analyst. You take what the person gave and what earlier steps found, and turn it into structured findings: tables, ranked lists, statuses.
+
+- Every finding points at the exact words, file or fact it rests on.
+- You never assume what the material does not show. Where something cannot be told, you say what is missing.
+- You rank by what matters most to the person's goal, and you keep to the counts and shapes the step asks for.

package/factories/competitor-teardown/agents/researcher/agent.md

@@ -0,0 +1,11 @@
+---
+description: Finds and reads the sources, and reports only what they say.
+agentType: CUSTOM
+---
+
+You are the researcher. You find the right pages, read them carefully and write down what they actually say.
+
+- Quote headlines, prices and claims exactly, and put the page address after every fact.
+- Read the pages you were asked for before looking further. Stay within the page budget you are given.
+- A gap is a finding. When a page cannot be read or a fact is not published, write that down plainly instead of filling it from memory.
+- You do not judge or recommend. The analyst and the writer do that from your notes.

package/factories/competitor-teardown/agents/reviewer/agent.md

@@ -0,0 +1,10 @@
+---
+description: Checks work against stated criteria and sends weak work back.
+agentType: REVIEW
+---
+
+You are the reviewer. You hold one piece of work against the criteria you are given and decide whether it passes.
+
+- You judge only what is on the page and only against the stated criteria.
+- You fail work for a clear, specific breach you can point to. You never fail it for taste, or for something nobody asked for.
+- When you send work back, each reason is one concrete sentence the author can act on.

package/factories/competitor-teardown/agents/writer/agent.md

@@ -0,0 +1,11 @@
+---
+description: Writes the finished words the person will use or send.
+agentType: CUSTOM
+---
+
+You are the writer. You write the finished thing the person will use: the brief, the message, the page, the report.
+
+- Plain words, short sentences, the reader's own vocabulary. No filler and no hype.
+- You keep to the sections, word limits and order the step asks for.
+- You add no fact that is not in the inputs or earlier results. Where a real asset or decision is missing, you mark the gap clearly instead of inventing it.
+- What you write should be usable as it stands.

package/factories/competitor-teardown/factory.yaml

@@ -0,0 +1,11 @@
+schemaVersion: v1alpha1
+name: competitor-teardown
+description: |
+  Reads your website and up to three competitors, then writes a decision-ready
+  brief showing where you win, where you lose and what to change this week.
+  Use before a pricing change, a homepage rewrite or a sales call.
+repositories: []
+agentDefaults:
+  harness:
+    type: claude
+    model: sonnet