blueprint
Design. Plan. Build. Validate. Blueprint gives coding agents twelve focused skills. They cover understanding existing code, deciding what to build, and delivering reviewed pull requests.
Open source software factory infrastructure for advanced AI coding workflows
$ npx -y skills add owainlewis/machinist --agent claude-code
What's inside
Machinist is an open-source software factory implementation. It runs on your machine, keeps repository access and credentials local, and records the work from request to handoff. Commands can invoke Codex, Claude Code, another agent CLI, a test runner, a shell script, or repository-owned orchestration.
Please note: this is early access software and subject to change.
Build and initialize Machinist:
git clone https://github.com/owainlewis/machinist.git
cd machinist
mkdir -p ./bin && go build -o ./bin/machinist ./cmd/machinist
./bin/machinist init
init writes ~/.machinist/config.toml with two commands, task-to-pr and audit.
Each is a prompt, an executor, and a timeout:
# ~/.machinist/config.toml
[commands.task-to-pr]
executor = "codex"
prompt_file = "prompts/task-to-pr.md" # optional
timeout = "120m"
Run it directly:
./bin/machinist run --command=task-to-pr --repo=/path/to/repo --prompt="Complete https://github.com/owner/repo/issues/42"
For a direct run, Machinist maps the configured command name to a fixed executable and uses the path supplied with --repo as the working directory. Managed submissions instead resolve an approved repository name from the worker configuration. In both cases, Machinist renders the prompt, sends it on standard input, streams stdout and stderr, and applies one overall timeout and cancellation. Exit code 0 succeeds; every non-zero exit code fails.
Inside each command, scripts are intentionally opaque. Their internal stages appear in logs, but Machinist does not infer their internal stages. A killed script restarts from the beginning unless the script owns checkpointing.
For explicit steps, configure a workflow:
[workflows.deliver]
steps = ["task-to-pr"]
Workflow tasks retain results and saved files, support approval and feedback, and keep earlier attempts in history. Each stage can read and write {{task.output_dir}}; Machinist restores and saves the shared folder between stages.
Start with your first task workflow: create a task from an issue or spec, follow it on the board, and review the result. The classify-then-merge example adds independent risk assessment and a conservative merge policy.
| Guide | What it covers |
|---|---|
| Documentation | Choose the right setup and operations guide |
| Task workflow guide | Set up planning, approval, shared files, and build |
| Configuration | Commands, executors, workers, models, and repositories |
| Development | Build, test, and work on Machinist locally |
| VM deployment | Run the control plane and worker as services |
| Workflow examples | Prompt-driven and scripted workflows |
Read CONTRIBUTING.md for development setup and pull-request expectations. Security issues should follow SECURITY.md.
Machinist is released under the MIT License.
Design. Plan. Build. Validate. Blueprint gives coding agents twelve focused skills. They cover understanding existing code, deciding what to build, and delivering reviewed pull requests.
FAQ
machinist is a Claude Code plugin with 1 hand-picked skill for agent orchestration work, indexed on Flowy. Install it with the command on its page. It includes machinist. Its skills do not fire on their own yet. Request auto-invocation to have Flowy route them as you prompt. Free and open source.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it