← ClaudeAtlas

x-manufacturinglisted

Review production paths by treating the factory, delivery pipeline, operations process, or build system as the product. Use when the user says factory as product, throughput, bottleneck, supplier constraint, rework, CI as factory, deployment flow, fulfillment, or support pipeline. Do not use for pure product vision, pure hiring, or first-principles product design when production is not the constraint.
thepraggyverse/elon-musk · ★ 0 · AI & Automation · score 68
Install: claude install-skill thepraggyverse/elon-musk
# X Manufacturing Use when success depends on making the thing repeatedly, cheaply, quickly, and reliably. The real work is production, not only design. 1. Map inputs, parts, tools, people, queues, inspections, rework, and outputs. 2. Identify the single constraint that limits throughput (twice-speed capacity lens when useful). 3. Find supplier, dependency, setup, tolerance, or quality bottlenecks that set the whole rate. 4. Delete unnecessary parts, variants, steps, and checks. 5. Simplify the production path before automating. 6. Measure the next experiment against throughput, speed, quality, and cost. 7. Choose the next throughput experiment. 8. **Complete** only when end-to-end production path, active constraint, dependency risk, deletion candidates, quality/cost guardrails, and next throughput experiment are explicit. Domain anchors: without production, supply does not exist; manufacturing is the moat; compete through speed, quality, and cost. **Stop:** Do not optimize or automate a production path before the active constraint and deletion candidates are named. ```text Manufacturing Review: Production path: Constraint: Supplier/dependency risks: Delete candidates: Simplified path: Quality/cost guardrails: Throughput experiment: ``` **BAD:** "Redesign the product UI again; production will catch up later." **GOOD:** "Treat CI/review/deploy as the factory, name the bottleneck, delete waste steps, then run one throughput experiment."