By 45ck
A control-flow runtime for Claude Code with verification gates, persistent state, and deterministic execution. Loops, conditionals, retries, and completion enforcement.
Route clearly-specified single-function implementation tasks to a local Ollama model (qwen3-coder:30b or equivalent) to save frontier API output tokens. Falls back to frontier on oracle fail. Use ONLY for single-function tasks with a deterministic test; do NOT use for multi-file refactors, debugging existing code, or app-build orchestration.
This skill should be used when the user asks to 'check if ready to deploy', 'pre-deploy check', 'verify before deploying', 'deployment readiness', 'is it ready to ship', or wants pre-deployment verification.
This skill should be used when the user asks to 'fix the tests', 'make tests pass', 'tests are failing', 'fix and test', 'green the tests', or wants to iteratively fix failing tests until they pass.
This skill should be used when the user asks to 'validate a flow', 'check my flow', 'lint this flow', 'is this flow correct', 'flow errors', 'flow warnings', or wants to analyze a prompt-language flow for issues before executing it.
This skill should be used when the user asks to 'run QA', 'quality audit', 'test the website', 'run E2E tests', 'lighthouse audit', 'check accessibility', 'visual regression test', 'run Playwright tests', 'quality gate check', or wants comprehensive quality verification of a web project. Use case-by-case when generated sites need validation beyond basic checks.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
A verification-first supervision runtime for coding agents. It wraps supported harnesses such as Claude Code and Codex in a persistent state machine with deterministic control flow, verification gates, and state management.
In one line. A thin orchestrator that turns flaky agents into deterministic pipelines by imposing loops, retries, and verification gates the AI cannot self-report past.
Coding agents are good at producing attempts, but they are unreliable at knowing when work is actually complete. prompt-language adds a small supervision layer that keeps state, runs real checks, retries bounded failures, and blocks completion until the declared gates pass.
Use it when you want:
Research results and active experiments live outside this product README. Start with What Works Now, then use docs/experiments.md or experiments/ for the catalog and raw research tree.
prompt nodes, so the exact deterministic/AI split depends on the flow you write.done when: tests_pass runs real commands and blocks completion until they pass. The AI cannot self-report "done."spawn launches child processes, await collects results, race picks the fastest. Variables flow between parent and children automatically.npx @45ck/prompt-language
Default interactive install requires Claude Code and Node.js >= 22. Headless native runners require Node.js >= 22 plus the selected CLI: Codex CLI, OpenCode, Ollama, or aider. Gemini is currently an eval comparison harness, not a native ci --runner gemini path. See the Harness Conformance Matrix before making runner-support claims.
For the full Claude Code and Codex walkthrough, including install verification, meta-prompt toggles, skill-aware wrapping, and terminal screenshots, see docs/guides/claude-code-and-codex.md.
agents:
reviewer:
model: "opus"
skills: "code-review", "security-review"
flow:
let spec = prompt "Write a detailed technical spec for: ${goal}"
let tasks = prompt "Break this spec into numbered implementation tasks: ${spec}"
while ask "Are there remaining tasks or unresolved review findings?" grounded-by "npm test" max 10
foreach task in ${tasks}
retry max 3
prompt: Implement ${task}. Follow the spec: ${spec}
run: npm test
if command_failed
prompt: Fix the failing tests for ${task}.
end
end
end
spawn "review" as reviewer
prompt: Review all changes against the spec. List any gaps, bugs, or missing edge cases as numbered tasks.
end
await "review" timeout 120
if ${review.findings} != "none"
let tasks = prompt "Convert these review findings into implementation tasks: ${review.findings}"
end
end
done when:
all(tests_pass, lint_pass)
The outer while ask loop keeps iterating as long as there are unresolved tasks or review findings. Each iteration implements tasks with retry, then spawns a reviewer -- if the reviewer finds problems, those become the new task list and the loop continues. The flow only exits when the AI judges there's nothing left and real tests_pass + lint_pass gates confirm it.
Invoke this as a skill from your preferred supported host, or run it headless in CI with npx @45ck/prompt-language ci. Native flow runners currently cover Claude, Codex, OpenCode, Ollama, and aider; Gemini remains comparison-only until it has a native runner adapter.
npx claudepluginhub 45ck/prompt-language --plugin prompt-languageSDLC workflow automation with Storybook-powered planning hub covering full software development lifecycle
Implementation of the babysitter technique - continuous orchestration loops for deterministic development. Run Claude in a loop with orchestration steps based on the babysitter-sdk and technique.
loophaus — Control plane for coding agents
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Harness engineering for Claude Code — hook-enforced dual review, state-machine gates, and fail-closed safety where it counts.
HelloAGENTS — The orchestration kernel that makes any AI CLI smarter. Adds intelligent routing, unified QA gates, safety guards, and notifications.
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT, WHY) while preserving agent autonomy in implementation decisions (HOW). Use when planning task delegation, structuring sub-agent prompts, or coordinating multi-agent workflows.