Skip to content
Skills Library
Programming · Automation

factory

/factory

Run a change through the software factory: intake → route → isolate → build → prove → judge → ship → close, with a person confirming the card, approving the route, answering stop-and-ask questions and merging. Use for any task in this repo ("/factory add dark mode", "/factory #42"), and for "/factory status" and "/factory resume T-0003". Also use when asked what's left to do in the repo (`factory audit`).

Licence
MIT
Last repository change
12.11.2026

Assessment and security

95/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Run a change through the software factory: intake → route → isolate → build → prove → judge → ship → close, with a person confirming the card, approving the route, answering stop-and-ask questions and merging. Use for any task in this repo ("/factory add dark mode", "/factory #42"), and for "/factory status" and "/factory resume T-0003". Also use when asked what's left to do in the repo (`factory audit`).

Original author description

Run a change through the software factory: intake → route → isolate → build → prove → judge → ship → close, with a person confirming the card, approving the route, answering stop-and-ask questions and merging. Use for any task in this repo ("/factory add dark mode", "/factory #42"), and for "/factory status" and "/factory resume T-0003". Also use when asked what's left to do in the repo (`factory audit`).

How it works

  1. Rules
  2. /factory status
  3. /factory resume <id>
  4. /factory <task text or issue>
  5. What's left in this repo?
Original SKILL.md headings · 99 lines, 845 words
SKILL.md preview
---
name: factory
description: >-
  Run a change through the software factory: intake → route → isolate → build →
  prove → judge → ship → close, with a person confirming the card, approving the
  route, answering stop-and-ask questions and merging. Use for any task in this
  repo ("/factory add dark mode", "/factory #42"), and for "/factory status" and
  "/factory resume T-0003". Also use when asked what's left to do in the repo
  (`factory audit`).
---

# /factory

This repo runs on the software factory (AGENTS.md is the contract). You drive the
`factory` CLI and talk to the person. The CLI does the work: it writes the task
card and the ledger, makes the worktree, runs the sector agent, produces the proof,
judges the change and opens the PR. You don't edit code for a factory task yourself.

## Rules

- Never edit `.factory/**` (the ledger included) or anything in `.worktrees/`.
  The runtime and the sector agent own them. A hook refuses edits to
  `.factory/**`, and to this checkout while it's on the default branch, whether
  through an edit tool or a shell command. It also refuses git commands that
  destroy work (force push, `reset --hard`, `clean -f`, `branch -D`). Don't work
  round it; if the session starts with "factory guard: OFF", tell the person.
- Every approval belongs to the person. Ask the question in the chat and wait for a
  clear yes. Only then run the command with `--yes`, which the ledger records as
  approved through you. Never pass `--yes` on your own judgment.
- Report what the CLI prints. Don't summarise a failure as a success or invent a
  next step: every command ends with `next: …`, and that is the next step.
- The factory never merges. Neither do you.

## /factory status

Run `factory task status` and show each open task with its next step. Tasks live
on the repo's `factory/tasks` branch, so this lists the whole team's tasks.

## /factory resume <id>

Run `factory task resume <id>`. It verifies the ledger and prints it with the next
step, and who holds the task. Carry on from that step in the flow below. If
verification fails, stop and show the problems: a ledger that fails verification
has been tampered with, or was signed with a key this machine doesn't have.

A task is held by one machine at a time. If someone else holds it, say who and
until when, and don't try to work round it. They can hand it over with
`factory task release <id>`; run that yourself only when the person asks to hand
their task over.

## /factory <task text or #issue>

1. **Sync.** Run `factory doctor`. On a ✗, do what it says (usually
   `factory skills sync`) and run it again. Don't start a task on a failing doctor.

2. **Intake.** Work out the card with the person:
   - title, type (`feature | fix | chore | refactor | spike`), and a description of
     what and why. For an issue, read it with `gh issue view <n>` and use
     `--source issue#<n>`.
   - acceptance criteria. Each one is a concrete, checkable sentence with a verify
     kind: `e2e | unit | manual | screenshot | contract | review`. If the task is
     vague, interview the person one question at a time until every criterion is
     concrete. Don't guess criteria.
   - optional: `--touches <glob>` for the paths it will change, `--page /path` for
     the pages a UI proof should shoot, `--out-of-scope`, `--constraint`,
     `--risk low|medium|high`.

   Then draft it:

   ```bash
   factory task new "<title>" --type fix --description "<what and why>" \
     --accept "<criterion>::unit" --accept "<criterion>::e2e" --touches "src/x/**"
   ```

   Show the card (`.factory/tasks/<id>/card.yml`, which `factory task confirm` prints
   too) and ask: "Confirm this card?" On a clear yes, run
   `factory task confirm <id> --yes`. To change an unconfirmed card, either the
   person edits `card.yml` themselves, or you draft a corrected card with
   `factory task new` and drop the old one with
   `factory task close <old id> --abandon "redrafted as <new id>"`.

3. **Route.** Run `factory task route <id>`. Show the sectors with their reasons,
   the skills, the checks, the proof and the budget. Mention any sectors that fell
   under the threshold. Ask: "Approve this assembly?" On a clear yes, run
   `factory task approve <id> --yes`. If the person wants changes, they edit
   `.factory/tasks/<id>/assembly.yml` themselves before approving. You don't edit it.

4. **Run.** Run `factory task run <id>`. It isolates, builds, proves, judges and
   ships, printing each ledger entry as it lands. It stops when a person is
   needed, and its last line says why:
   - **stop-and-ask** (exit 2): show the question (a new dependency, a schema
     change, a protected path, the budget, or the judge needing a person) and ask
     the person. Then run `factory task answer <id> --allow "<their note>"` or
     `--deny "<what to do instead>"`, and run `factory task run <id>` again.
   - **shipped** (exit 0): show the draft PR link. The person reviews it, marks it
     ready and merges it. You don't.
   - **an error** (exit 1): show it and stop. Don't work around it by doing the
     beat's work yourself.

5. **Close.** After the person says the PR is merged (or closed), run
   `factory task close <id>`. To drop a task at any point, run
   `factory task close <id> --abandon "<why>"`. Close seals the ledger.

## What's left in this repo?

When asked about the repo's state rather than a task, run
`factory audit --format json`. Report the `fail` and `needs-evidence` controls,
highest severity first, and suggest starting the fixes as `/factory` tasks.

Versions

RepositoryScoreLicence
This page · arynbht/software-factory95MIT
fayssal-elmofatiche/factory-sandbox100GPL-3.0
andriiklymiuk/corgi100MIT
uiverify/uiverify100MIT
BuilderIO/skills100MIT
chrisgagne/grounded-forge100MIT
TDSchreur/tds-factory100MIT
momoathome/software-factory100MIT
hybridlabor-api/aos100Apache-2.0

Database snapshot: 13.11.2026 · package version d8aaef0160e7 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90factory-run
    Driver of the factory. Use this, instead of editing the code yourself or calling the factory skills one by one, whenever the user asks for a bug fix, idea or feature to be built and delivered as a pull request or taken end to end, however small the change looks (\"build it and…
  • 82factory-config
    Help the owner write or change a Pipeline or a Run graph of the Software Factory, starting from a shipped one and ending with a diagram that `factory check` accepts. Use when the owner wants to change how Tickets are built, reviewed or picked, or how a Run ends.
  • 90factory-run
    Operate the local factory in plain words. "start" installs the 10-minute tick and the dashboard and runs a first tick; "stop" removes them; "status" shows targets, workers, parked tickets and the last tick; "tick" runs one pass now; "pause <target>" / "resume <target>" flips a…
  • 90review
    /factory:review <pr>. Run the Factory reviewer in this session on one PR of the current repository: one comment-only pass of line-tied findings. Use when the user asks to review a Factory PR by number.
  • 100eminzo-factory
    Run the Eminzo software factory v2. A GitHub issue labeled `factory` becomes a job (with `issue <n>`, `<feature>` or `xs <request>`, or from the queue by `run` when `run_mode` is `queue`); `job new` claims it for the gh user. Each job goes through intake, routing, spec (and an…
  • 90software-factory
    Deliver software through a canonical ticket queue, versioned repository, evaluations, CI/CD, live QA and measured follow-up; or improve that delivery system. Use for end-to-end software delivery and factory engineering.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.