Sum Factory
Start or run a factory from a markdown settings file. Use when the user asks to start a factory, run one, or say where a factory lives.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- Sum Factory
- description
- Start or run a factory from a markdown settings file. Use when the user asks to start a factory, run one, or say where a factory lives.
03 SKILL.md 正文
Factory
When to use it
The user asked to start a factory, run a factory, or tell you where one lives. Software and copy use this same skill. The difference is a markdown settings file.
Required inputs and access
The Factory settings in the Sum clone at skills/sum-factory/factories/<name>.md.
A confirmed copy, when one exists, at /workspace/sum/factories/<name>.md.
Notion, when the floor is a Notion page.
Spiral, when the confirmed settings say to call it.
The Sum Dispatch and Sum Persist skills, once a run is actually approved.
Sequence of work
Ask one question at a time. Save the answer under /workspace/sum/factories/ before you ask the next. Recommend from a file or a page you read. Do not invent lanes or tools.
- Name the factory.
copyandsoftwarealready have recommendation files. - Where does it live? Text files, or a Notion page? If they name a page, fetch it.
- What are the lanes, in order? On Notion, read the status options and say the names you saw. Ask them to confirm that order.
- Which lanes does a pass pick up, and what should happen there? Ask which lanes are theirs alone.
For copy, read skills/sum-factory/factories/copy.md in the clone and offer it as the recommendation. Still ask. If the Notion page shows different lanes, say what you saw and ask which order to keep.
Write the confirmed answers to /workspace/sum/factories/<name>.md. Read the file back.
A run comes after that confirmation, as its own request.
runner: softwaremeans follow the software settings file. That lane requires the separately preserved compatible legacy installation pinned in the software settings, including its installed helper; this HC instruction checkout cannot run it. Do not tick it from this chat. Dispatch a worker only when the user asked you to run it there.runner: directivemeans dispatch one worker. The brief is the confirmed settings file plus the piece URL or path they named. The worker does only the pickup lanes, then stops. You do not call Spiral in this chat.
On a Notion floor, a piece URL is the reliable trigger. Search does not see a status property.
How to validate the result
The settings file exists and matches what the user confirmed. A start did not call Spiral and did not move a piece. A run left the coordinator chat free of the lane work. The worker report names the piece, the command, and the status it set.
What to return
On a start: the settings path, the lanes you saw, and the action they confirmed. On a run: the task id, the worker, and the piece or issue it took. Then stop.
What requires approval
Starting a factory, confirming the settings, and each run. A recommendation file is not approval. A piece sitting in Ready is not approval until they ask for a run. Do not post. Do not set Approved. The user merges. The Bot never merges.
04 同仓库更多 Skills
verify
Verify a repository through its project-root VERIFY.md contract - run the canonical `mise run verify`, record candidate-bound evidence, and report manual scenarios truthfully. Works in any clone without sum or Herdr.
maintain-verification
Keep a repository's VERIFY.md and feature maps honest when behavior changes - audit stale tasks, paths, links, and coverage claims, find the features a change touches, record a no-map-change rationale for internal changes, and keep authored map edits separate from run results. Works in any clone without sum or Herdr.
evidence
Capture truthful before/after evidence for one mapped scenario - real screenshots, short screencasts, CLI transcripts, or HTTP responses from the base and the candidate builds - and compare them into one manifest. Works in any clone without sum or Herdr.
create-verification
Bootstrap or extend a repository's project-local verification - the VERIFY.md contract, a `verify` mise task built from checks the project already declares, a feature-map index with seed feature files, and the vendored verify/maintain skills - then prove the generated instructions by running them once. Works in any clone without sum or Herdr.
Sum Verify
Run a distinct coordinator verification of a worker result. Use when a worker reports a candidate or findings, before treating that report as done.
Sum Sweep
Put standing sweeps on a dedicated Sweep worker plus routine. Use for inbox digests and similar repeating work, not for the weekday Inbox status.