Approval gates, and the one chain without them
Every skill that would change something stops for a person. The 8D skill drafts D1 to D5 and D7 and leaves D6 and D8 empty, because those need something to have actually happened. The morning plant pulse is the only chain with no gate, because it writes to no system of record: it keeps one record per site and production day in its own dashboard's database and redraws the dashboard. A plugin cannot wake itself up, so the trigger is a scheduled task in Cowork or Claude Code.
The layer it leaves open
All of this is daily management: hold the standard, react to the gap. "Output against plan" means against the production schedule. Nothing in the plugin says what the plant must get better at this year, which OEE target is the right one, or which recurring cause deserves an improvement initiative rather than another corrective action. The 8D skill asks you to label an action "improvement, not corrective action", and stops there.
That is the strategy layer, and it composes the same way: an MCP server that holds the strategy, and an agent that reads both. I build one: Hoshin Kanri (
hoshin.app/mcp
), an X-Matrix with vision, annual objectives, initiatives and KPIs, a review cycle, and a maturity grid assessed site by site. It connects to no ERP; the agent composes.
The handoff is a short set of rules, which I wrote as a skill, plant-pulse-to-matrix, in Hoshin's open-source plugin (
github.com/wellknownmcp/hoshin-kanri
):
Read a site's day records for the month, keep the complete days, and write one monthly KPI reading with its provenance: the tool, the first and last record, the freshness of the data. The day record keeps OEE as ratios without the times behind them, so the monthly figure is an unweighted mean of complete days, and the reading says how many it rests on. Never daily figures. Never a target: targets are decided by people.
Turn recurring problems into ideas for the next review: a nonconformance that recurs after a fix that did not hold, a cause shared by several 8Ds, the same machines topping the breakdown ranking month after month. The review decides what becomes an initiative.
Use the records as evidence for the site's maturity assessment, as a draft that people validate.
How the strategy side reads the plant side: the pulse keeps its day records in the database of its own dashboard, an artifact in the plant team's Claude account, and its docs name the tools that read them back (Artifact to find the dashboard by its exact title, ArtifactData to query the records). Same account, same tools, no new integration. When the session has no artifact tools, the skill asks for the morning reports instead of estimating.
Honest status: I read their contracts and wrote the skill against them. I have not run both plugins together on a real plant, and I have not checked whether a dashboard shared from another account can be read the same way. If you run a site with agents and want to try it, reply here.