Browse / Software development / mifal
mifal
romiluz13
One engineering workflow for Claude Code, Codex, Droid, Pi and OpenCode, with a validator that refuses a record without its evidence.
Open romiluz13/mifal → Checked against the four rules.
agent-skillsai-agentsclaude-codecodexcoding-agentsdeveloper-toolsengineering-workflowmacos
Works with any agent
ships AGENTS.md, the cross-tool instruction file.
In its own words
Alpha, macOS.
One engineering workflow for the coding agents on your Mac, and the paperwork it leaves behind.
A brief that names every claim, a receipt that answers each one, and a validator that refuses a record missing its required sections.
The Mifal website: the build replay you can scrub through, the gate, and the install run.
An agent's "done" message is not independent proof that the work passed its checks. Mifal detects five agent families (Claude Code, Codex, Droid, Pi and OpenCode) and installs one Guide into the selected Homes it can wire, one or several per agent; a precedence conflict or a symbolic rules file can make it skip an agent or refuse the install. It also installs the same 39 skills (Matt Pocock's engineering skills run as ordered phases, plus DDD, review and team leading) and a contract validator that refuses a brief, receipt or phase record that lacks its required fields and checks selected identities and hashes; it does not verify that tests ran. For a Claude Code worker, validate_contracts.py loads-proof checks the worker's session log for a complete load of each skill its brief selects; that shows the skill was read, not that it was followed, and other agents' logs are not checked. --dry-run previews the planned changes; a plain install prints a short summary and writes. Uninstall removes what Mifal wrote that is unchanged and keeps any file you edited.
The repository's own description, then 11% of its README. Read the rest on GitHub ↗
Read from the repository's git tree on 2026-08-17.