| name | factory-improvement |
| version | 1.1 |
| last_updated | 2026-08-08 |
| id | factory-improvement |
| one_line_purpose | Audit and propose factory self-improvement automation. |
| entry_point | docs/skills/factory-improvement/SKILL.md |
| category | meta |
| mcp_compliance_level | partial |
| optimization_status | draft |
| status | active |
| dependencies | [] |
| tags | ["factory","automation","improvement"] |
| description | Self-improving factory loop for projectbluefin. Use when identifying automation gaps, proposing workflows, or auditing ACMM maturity. |
| metadata | {"type":"reference"} |
Factory Improvement — Self-Improving Loop
When to Use
- Dedicated "improve the factory" sessions
- After an architectural review surfaces gaps
- Onboarding a new repo into the factory standard
- Quarterly health check: design vs. reality drift
When NOT to Use
- Fixing a specific bug (use the repo's AGENTS.md + relevant skill)
- Reviewing a single PR (use
hive-review or pr-review)
- Active incident response — fix the incident first, then run this loop
Mission
Full automation of everything that does not require a human judgment call.
The factory should be self-healing: issues flow through the pipeline, agents handle
the mechanical work, and humans make only the decisions requiring accountability,
context, or trust. Every manual step that could be automated is a reliability tax.
Human Gates — Intentional and Non-Negotiable
Never automate these. Never propose automating them without explicit maintainer approval:
| Gate | Why it must be human |
|---|
Admitting an issue to a queue (3-human-queue / 3-clanker-queue) | Prioritization judgment; agent scope assignment |
| PR merge approval (1 human reviewer per CODEOWNERS) | Accountability; trust for org-critical changes |
| Release blocker calls during a promotion window | Release impact judgment |
| Production promotion decisions (Tuesday 06:00 UTC, N=7 floor) | Final go/no-go for user-facing changes |
| Reassigning or closing a stale PR | Judgment on abandoned vs. still-active work |
Any write or automated action to ublue-os/* namespace | Absolute prohibition — reads only. |
Everything else is automatable.
The Improvement Loop
MEASURE → TRIAGE → IMPLEMENT → CAPTURE → VERIFY → LOOP
See references/loop-detail.md for the full MEASURE/TRIAGE/IMPLEMENT/CAPTURE/VERIFY commands and patterns.
~/src/hive-status
gh search issues --label --owner projectbluefin --state open \
--json number,title,repository
gh search issues --label --owner projectbluefin --state open \
--json number,title,repository
