zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-03-30 13:43:26 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: resolve operational skill review issues

Browse Source
This commit is contained in:
Affaan Mustafa
2026-03-10 21:07:36 -07:00
parent 22816651c2
commit 6c8f425ae2
8 changed files with 45 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
skills/production-scheduling/SKILL.md
View File

@@ -10,7 +10,7 @@ description: >
or balancing manufacturing lines.
license: Apache-2.0
version: 1.0.0
homepage: https://github.com/ai-evos/agent-skills
homepage: https://github.com/affaan-m/everything-claude-code
origin: ECC
metadata:
author: evos
@@ -167,7 +167,7 @@ When a disruption invalidates the current schedule:
## Key Edge Cases
Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md).
Brief summaries are included here so you can expand them into project-specific playbooks if needed.
1. **Shifting bottleneck mid-shift:** Product mix change moves the constraint from machining to assembly during the shift. The schedule that was optimal at 6:00 AM is wrong by 10:00 AM. Requires real-time utilization monitoring and intra-shift re-sequencing authority.
@@ -196,7 +196,7 @@ Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md)
- **Customer delivery impact notice:** Never surprise the customer. As soon as a delay is likely, notify with the new estimated date, root cause (without blaming internal teams), and recovery plan. "Due to an equipment issue, order #12345 will ship [new date] vs. the original [old date]. We are running overtime to minimize the delay."
- **Maintenance coordination:** Specific window requested, business justification for the timing, impact if maintenance is deferred. "Requesting PM window on Line 3, Tuesday 06:00–10:00. This avoids the Thursday changeover peak. Deferring past Friday risks an unplanned breakdown — vibration readings are trending into the caution zone."
Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
Brief templates appear above. Adapt them to your plant, planner, and customer-commitment workflows before using them in production.
## Escalation Protocols
@@ -234,6 +234,5 @@ Track per shift and trend weekly:
## Additional Resources
- For detailed decision frameworks, scheduling algorithms, and optimization methodologies, see [decision-frameworks.md](references/decision-frameworks.md)
- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)
- Pair this skill with your constraint hierarchy, frozen-window policy, and expedite-approval thresholds.
- Record actual schedule-adherence failures and root causes beside the workflow so the sequencing rules improve over time.