Kiln plugin
Claude Code plugin that builds software from a conversation in eight phases, with Claude and GPT checking each other's work.
- 226 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The plugin writes and runs project code through many agents and, in auto-proceed mode, does not wait for approval at every step.
- When Codex CLI takes part, parts of the project go to OpenAI, so closed code should be checked for permission to share it.
- By the author's own statement the plugin has not yet built a real project end to end.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/fredasterehub-kilnDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin writes and runs project code through many agents and, in auto-proceed mode, does not wait for approval at every step.
- When Codex CLI takes part, parts of the project go to OpenAI, so closed code should be checked for permission to share it.
- By the author's own statement the plugin has not yet built a real project end to end.
This is third-party code. Review the repository files before installing.
What it does
Kiln is a Claude Code plugin that takes a project from an idea to finished software. The `/kiln:fire` command runs eight phases: environment check and interview, idea discussion, source research, the plan, freezing of acceptance criteria, work in small milestones, scenario runs against the built product, and handover. Twenty-two agents from two model families take part. GPT-5.6 through Codex CLI writes code by default, Opus takes interfaces and creative parts, and each piece is judged by a model from the other family. Without Codex the plugin still builds the whole project, with two Claude models checking each other. The full record of the run sits in the project's `.kiln/` folder: state, decision ledger, plan, verification results and the final report. `/kiln:fire` resumes interrupted work where it stopped.
Who it is for. Developers and founders who want to describe a product in plain words and get a verified build in Claude Code, with or without Codex CLI alongside.
Good fit when
- There is an app or API idea but no specification, and an interview is needed to produce one.
- Acceptance criteria must be frozen before the first line of code so the finished product can be checked against them.
- One model family writes the code and another family has to review it.
- A build stopped midway and has to resume from where it stopped using the `.kiln/` files.
Not a fit when
- A small edit in existing code: eight phases are overkill for it.
- The project cannot be run in auto mode without reading every step, while the plugin is built for that.
- A battle-tested system is required: by the author's own statement the plugin has not yet completed a real project end to end.
Example request
/kiln:fire an online card shop with payments and an admin panelLimitations
Claude Code 2.1.198 or newer and Node for the helper scripts are required. Codex CLI is optional, but without it the second model family is replaced by Claude models, and the plugin says so up front. The author marks the status as red: a real project has not yet been built end to end (entry dated 29 July 2026, version 3.2.2). Only one Kiln session is allowed per folder. Updates do not arrive on their own and are installed with `claude plugin update kiln@kiln`.
How to disable. Remove the plugin with `claude plugin uninstall kiln@kiln`. The `.kiln/` folder in projects can stay as a log or be deleted: the project's code is not affected.
FAQ
How do I install Kiln?
Run `claude plugin marketplace add Fredasterehub/kiln`, then `claude plugin install kiln@kiln` in a terminal. After that `/kiln:fire` and `/kiln:doctor` are available in Claude Code.
What is `/kiln:doctor` for?
It checks the environment and launches nothing: the Claude Code version, Node and whether Codex CLI is present. It is a good first step.
Is Codex CLI required?
No. Without it the plugin builds the whole project and Claude models take the GPT seats. It says so before work starts.
Where is the record of the run kept?
In the project's `.kiln/` folder: `state.json`, `ledger.jsonl`, the plan, verification results and a `delivery/` folder with the final report.
Can an interrupted build be resumed?
Yes. `/kiln:fire` reads the files on disk and continues from where it stopped.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin that hands coding tasks to Codex agents, monitors them and verifies the results independently
Claude Code plugin that runs complex tasks as step-by-step workflows with quality gates and reviews changes against project rules.
Workflows for Claude Code: /do, /omo, /bmad-pilot and more commands, with Codex, Gemini or OpenCode writing the code through codeagent-wrapper
Claude Code supervises while Codex, opencode and pi work on your quota: delegated edits, independent review, model discussions
A one-person coding factory: Claude Code manages the project while Codex, Qwen, Grok and Kimi write code as separate processes.
A Claude Code plugin where the main model plans and signs off while search, edits and verification go to roles running on cheaper models
README in short
The README is written in a stylized voice of Kiln itself and describes the phases, the `.kiln/` folder layout and the discipline rules. It states outright that the system was rewritten from scratch and has not yet completed a real project.