| name | manufacturing-industrial |
| description | Use when a proposal concerns manufacturing, production planning, warehousing, inventory, facilities, material handling, ERP, MES, WMS, TMS, or green production; use agriculture when primary production and farm value chains dominate. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Manufacturing and Industrial Operations
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- Use when the proposal concerns manufacturing, processing, warehousing, inventory, logistics, factory operations, industrial digital transformation, ERP, MES, WMS, TMS, facilities layout, or material handling.
- Load it when proposal sections need operational terminology, methodology cues, risk logic, deliverable options, or evaluator-aware industrial framing.
Do Not Use When
- The assignment is purely policy, governance, finance, or training with no material operating-system component.
- Another sector skill is a closer fit and manufacturing/inventory depth would distract.
Required Inputs
| Artefact | Source/provider | Required? | Missing-input behaviour |
|---|
| The ToR or RFP. | Buyer solicitation, ToR, or approved brief | Required | Stop the affected claim, request or verify the input, and label the resulting gap. |
| Product or process type, facility context, inventory scope, systems environment, and expected assignment outputs. | Buyer, verified sector source, or discovery | Required | Stop the affected claim, request or verify the input, and label the resulting gap. |
| Any client data constraints: stock ledgers, production records, BOMs, warehouse maps, utility bills, or system access. | Buyer, verified sector source, or discovery | Conditional | Stop the affected claim, request or verify the input, and label the resulting gap. |
Workflow
- Identify whether the assignment is an insight, planning, implementation, or systems-advisory engagement.
- Load
../../consulting-frameworks/references/industrial-operations-diagnostics.md.
- Select only the diagnostic domains relevant to the ToR: materials, MRP, capacity, warehouse, facilities, quality, sustainability, or systems.
- Carry sector language into methodology, work plan, staffing, risks, and deliverables.
- Check that promised outputs match available data, site access, timeline, and budget.
Stop condition: Stop when proposer identity, controlling framework, mandatory form, sector fit, current rule, or load-bearing evidence remains unresolved.
Recovery: Record the gap and owner, seek clarification or current evidence, and return only the separable proposal content that remains supportable.
Sector Cues
- Strong proposals separate planning problems from execution problems.
- Do not recommend automation before testing process, master data, stock accuracy, and decision rules.
- Use MRP, capacity, warehouse, quality, and resource-efficiency language only where the ToR supports it.
- For ERP/MES/WMS/TMS assignments, show how operational diagnostics inform requirements and configuration.
Typical Deliverables
- Current-state industrial operations diagnostic
- Inventory and MRP policy review
- Capacity and scheduling model
- Warehouse layout, slotting, and material-flow assessment
- Quality and traceability controls matrix
- Green production resource-efficiency roadmap
- ERP/MES/WMS/TMS requirements and implementation roadmap
Quality Standards
- Use only sector or procurement detail that changes a proposal decision, method, risk, form, or acceptance condition.
- Verify current rules and figures at source; distinguish solicitation text from contextual guidance.
- Keep identity, methodology, work plan, staffing, risk, and price assumptions aligned.
Anti-Patterns
- Treating a neighbouring sector or framework as interchangeable. Fix: identify the controlling rule and primary outcome.
- Adding jargon without changing a delivery choice. Fix: connect each term to method, risk, or output.
- Presenting an unverified current rule as settled. Fix: cite the source and verification date or mark it unassessed.
- Ignoring a missing mandatory input. Fix: stop the affected claim and assign an evidence owner.
- Letting sector framing contradict the work plan or team. Fix: reconcile scope, roles, schedule, and acceptance.
- Treating a neighbouring sector or framework as interchangeable. Fix: identify the controlling rule and primary outcome.
- Adding terminology without changing a delivery choice. Fix: link each term to method, risk, output, or evaluation criterion.
- Presenting an unverified current rule or statistic as settled. Fix: cite and date the source or mark it not assessed.
- Ignoring a missing mandatory input. Fix: stop the affected claim and assign an evidence owner.
- Letting sector or identity framing contradict methodology, staffing, schedule, or price. Fix: reconcile all affected sections before release.
Outputs
| Artefact | Consumer | Acceptance condition |
|---|
| manufacturing industrial proposal guidance | Proposal lead, section writer, and evaluator-readiness reviewer | Applied consistently, traceable to the selected source, and free of unsupported identity, framework, or sector claims. |
Evidence Produced
| Evidence | Consumer | Acceptance condition |
|---|
| Routing and source record | Proposal lead and reviewer | Selected identity, framework, sector, source, date, and material gaps are recorded. |
| Decision record | Section writer and delivery lead | Each material choice has rationale, owner, evidence, and a review or stop condition. |
| Conformance check | Release reviewer | Mandatory forms, identity rules, sector logic, and unresolved checks are explicitly assessed. |
Capability Contract
This skill may read supplied profiles, solicitations, ToRs, approved references, and proposal drafts and may prepare routing guidance or draft content within the authorised workspace. Review is read-only by default. It must not invent credentials, certify compliance, submit a bid, accept terms, publish, disclose confidential information, or change source records without explicit authority.
Degraded Mode
If the solicitation, profile, current procurement source, sector evidence, network, or reviewer is unavailable, provide the narrowest useful qualified routing or draft. Mark the missing check not assessed, omit unsupported credentials, thresholds, dates, or compliance claims, and identify the evidence owner. An unassessed requirement is never a pass.
Decision Rules
| Decision | Action | Failure/risk avoided |
|---|
| Operational constraint | Test process, master data, inventory accuracy, capacity, quality, and decision rules before recommending automation. | Automation of unstable or unmeasured operations |
| Conflicting solicitation and background guidance | Follow the solicitation while recording the conflict for formal clarification. | Non-responsive interpretation |
| Missing mandatory evidence | Stop the affected claim or form, record the owner and deadline, and continue only with independent supported content. | Fabricated evidence or silent omission |
| Submission, certification, or contractual commitment | Obtain explicit authority and preserve approval evidence before acting. | Unauthorised external commitment |
Worked Example
A solicitation requires operational constraint, but one controlling input is missing. The proposal team applies this rule: Test process, master data, inventory accuracy, capacity, quality, and decision rules before recommending automation. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids automation of unstable or unmeasured operations.
References
