docs: resolve operational skill review issues

skills/carrier-relationship-management/SKILL.md

@@ -9,7 +9,7 @@ description: >
   carrier performance, or building freight strategies.
 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
@@ -72,7 +72,7 @@ Measure what matters. A scorecard that tracks 20 metrics gets ignored; one that
 
 Your carrier portfolio is an investment portfolio — diversification manages risk, concentration drives leverage:
 
-- **Asset carriers vs. brokers:** Asset carriers own trucks. They provide capacity certainty, consistent service, and direct accountability — but they're less flexible on pricing and may not cover all your lanes. Brokers source capacity from thousands of small carriers. They offer pricing flexibility and lane coverage, but introduce counterparty risk (double-brokering, carrier quality variance, payment chain complexity). Target mix: 60-70% asset, 20-30% broker, 5-15% niche/specialty.
+- **Asset carriers vs. brokers:** Asset carriers own trucks. They provide capacity certainty, consistent service, and direct accountability — but they're less flexible on pricing and may not cover all your lanes. Brokers source capacity from thousands of small carriers. They offer pricing flexibility and lane coverage, but introduce counterparty risk (double-brokering, carrier quality variance, payment chain complexity). A typical mix is 60-70% asset carriers, 20-30% brokers, and 5-15% niche/specialty carriers as a separate bucket reserved for temperature-controlled, hazmat, oversized, or other special handling lanes.
 - **Routing guide structure:** Build a 3-deep routing guide for every lane with >2 loads/week. Primary carrier gets first tender (target: 80%+ acceptance). Secondary gets the fallback (target: 70%+ acceptance on overflow). Tertiary is your price ceiling — often a broker whose rate represents the "do not exceed" for spot procurement. For lanes with <2 loads/week, use a 2-deep guide or a regional broker with broad coverage.
 - **Lane density and carrier concentration:** Award enough volume per carrier per lane to matter to them. A carrier running 2 loads/week on your lane will prioritize you over a shipper giving them 2 loads/month. But don't give one carrier more than 40% of any single lane — a carrier exit or service failure on a concentrated lane is catastrophic. For your top 20 lanes by volume, maintain at least 3 active carriers.
 - **Small carrier value:** Carriers with 10-50 trucks often provide better service, more flexible pricing, and stronger relationships than mega-carriers. They answer the phone. Their owner-operators care about your freight. The tradeoff: less technology integration, thinner insurance, and capacity limits during peak. Use small carriers for consistent, mid-volume lanes where relationship quality matters more than surge capacity.
@@ -139,7 +139,7 @@ Remove a carrier from your active routing guide when any of these thresholds are
 
 ## Key Edge Cases
 
-These are situations where standard playbook decisions lead to poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where standard playbook decisions lead to poor outcomes. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **Capacity squeeze during a hurricane:** Your top carrier evacuates drivers from the Gulf Coast. Spot rates triple. The temptation is to pay any rate to move freight. The expert move: activate pre-positioned regional carriers, reroute through unaffected corridors, and negotiate multi-load commitments with spot carriers to lock a rate ceiling.
 
@@ -170,7 +170,7 @@ Rate negotiations are long-term relationship conversations, not one-time transac
 - **Positive reviews:** Be specific. "Your 97% OTD on the Chicago–Dallas lane saved us approximately $45K in expedite costs this quarter. We're increasing your allocation from 60% to 75% on that lane." Carriers invest in relationships that reward performance.
 - **Corrective reviews:** Lead with data, not accusations. Present the scorecard. Identify the specific metrics below threshold. Ask for a corrective action plan with a 30/60/90-day timeline. Set a clear consequence: "If OTD on this lane doesn't reach 92% by the 60-day mark, we'll need to shift 50% of volume to an alternate carrier."
 
-For full communication templates, see [communication-templates.md](references/communication-templates.md).
+Use the templates below as a base and adapt the language to your carrier contracts, escalation paths, and customer commitments.
 
 ## Escalation Protocols
 
@@ -208,6 +208,5 @@ Track weekly, review monthly with carrier management team, share quarterly with
 
 ## Additional Resources
 
-- For detailed decision frameworks on rate negotiation, portfolio optimization, and RFP execution, see [decision-frameworks.md](references/decision-frameworks.md)
+- Track carrier scorecards, exception trends, and routing-guide compliance in the same operating review so pricing and service decisions stay tied together.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Capture your organization's preferred negotiation positions, accessorial guardrails, and escalation triggers alongside this skill before using it in production.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)

skills/customs-trade-compliance/SKILL.md

@@ -10,7 +10,7 @@ description: >
   duty optimization.
 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
@@ -90,7 +90,7 @@ Incoterms define the transfer of costs, risk, and responsibility between buyer a
 - **CPT/CIP (Carriage Paid To / Carriage & Insurance Paid To):** Risk transfers at first carrier, but seller pays freight to destination. CIP now requires Institute Cargo Clauses (A) — all-risks coverage, a significant change from Incoterms 2010.
 - **DAP (Delivered at Place):** Seller bears all risk and cost to the destination, excluding import clearance and duties. The seller does not clear customs in the destination country.
 - **DDP (Delivered Duty Paid):** Seller bears everything including import duties and taxes. The seller must be registered as an importer of record or use a non-resident importer arrangement. Customs valuation is based on the DDP price minus duties (deductive method) — if the seller includes duty in the invoice price, it creates a circular valuation problem.
-- **Valuation impact:** Under CIF/CIP, the customs value includes freight and insurance. Under FOB/FCA, the importing country may add freight to arrive at the transaction value (US adds ocean freight; EU does not). Getting this wrong changes the duty calculation.
+- **Valuation impact:** Incoterms affect the invoice structure, but customs valuation still follows the importing regime's rules. In the U.S., CBP transaction value generally excludes international freight and insurance; in the EU, customs value generally includes transport and insurance costs up to the place of entry into the Union. Getting this wrong changes the duty calculation even when the commercial term is clear.
 - **Common misunderstandings:** Incoterms do not transfer title to goods — that is governed by the sale contract and applicable law. Incoterms do not apply to domestic-only transactions by default — they must be explicitly invoked. Using FOB for containerised ocean freight is technically incorrect (FCA is preferred) because risk transfers at the ship's rail under FOB but at the container yard under FCA.
 
 ### Duty Optimization
@@ -140,7 +140,7 @@ Incoterms define the transfer of costs, risk, and responsibility between buyer a
 
 ### Classification Decision Logic
 
-When classifying a product, follow this sequence without shortcuts. See [decision-frameworks.md](references/decision-frameworks.md) for full decision trees.
+When classifying a product, follow this sequence without shortcuts. Convert it into an internal decision tree before automating any tariff-classification workflow.
 
 1. **Identify the good precisely.** Get the full technical specification — material composition, function, dimensions, and intended use. Never classify from a product name alone.
 2. **Determine the Section and Chapter.** Use the Section and Chapter notes to confirm or exclude. Chapter notes override heading text.
@@ -182,7 +182,7 @@ When a restricted party screening tool returns a match, do not block the transac
 
 ## Key Edge Cases
 
-These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where the obvious approach is wrong. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **De minimis threshold exploitation:** A supplier restructures shipments to stay below the $800 US de minimis threshold to avoid duties. Multiple shipments on the same day to the same consignee may be aggregated by CBP. Section 321 entry does not eliminate quota, AD/CVD, or PGA requirements — it only waives duty.
 
@@ -215,7 +215,7 @@ Match communication tone to the counterparty, regulatory context, and risk level
 
 ### Key Templates
 
-Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+Brief templates appear below. Adapt them to your broker, customs counsel, and regulatory workflows before using them in production.
 
 **Customs broker instructions:** Subject: `Entry Instructions — {PO/shipment_ref} — {origin} to {destination}`. Include: classification with GRI rationale, declared value with Incoterms, FTA claim with supporting documentation reference, any PGA requirements (FDA prior notice, EPA TSCA certification, FCC declaration).
 
@@ -259,6 +259,5 @@ Track these metrics monthly and trend quarterly:
 
 ## Additional Resources
 
-- For detailed decision frameworks, classification logic, and valuation methodology, see [decision-frameworks.md](references/decision-frameworks.md)
+- Pair this skill with an internal HS classification log, broker escalation matrix, and a list of jurisdictions where your team has non-resident importer or FTZ coverage.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Record the valuation assumptions your organization uses for U.S., EU, and APAC lanes so duty calculations stay consistent across teams.
-- For complete communication templates with variables and formatting guidance, see [communication-templates.md](references/communication-templates.md)

skills/energy-procurement/SKILL.md

@@ -10,7 +10,7 @@ description: >
   demand charges, evaluating PPAs, or developing energy strategies.
 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
@@ -150,11 +150,11 @@ Never try to "call the bottom" on energy markets. Instead:
 - Monitor the forward curve relative to the 5-year historical range. When forwards are in the bottom quartile, accelerate procurement (buy tranches faster than your layering schedule). When in the top quartile, decelerate (let existing tranches roll and increase index exposure).
 - Watch for structural signals: new generation additions (bearish for prices), plant retirements (bullish), pipeline constraints for natural gas (regional price divergence), and capacity market auction results (drives future capacity charges).
 
-For the complete decision framework library, see [decision-frameworks.md](references/decision-frameworks.md).
+Use the procurement sequence above as the decision framework baseline and adapt it to your tariff structure, procurement calendar, and board-approved hedge limits.
 
 ## Key Edge Cases
 
-These are situations where standard procurement playbooks produce poor outcomes. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where standard procurement playbooks produce poor outcomes. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **ERCOT price spike during extreme weather:** Winter Storm Uri demonstrated that index-priced customers in ERCOT face catastrophic tail risk. A 5 MW facility on index pricing incurred $1.5M+ in a single week. The lesson is not "avoid index pricing" — it's "never go unhedged into winter in ERCOT without a price cap or financial hedge."
 
@@ -188,7 +188,7 @@ Energy supplier negotiations are multi-year relationships. Calibrate tone:
 - **Sustainability:** Map procurement decisions to Scope 2 targets. "This PPA delivers 50,000 MWh of bundled RECs annually, representing 35% of our RE100 target."
 - **Operations:** Focus on operational requirements and constraints. "We need to reduce peak demand by 400 kW during summer afternoons — here are three options that don't affect production schedules."
 
-For full communication templates, see [communication-templates.md](references/communication-templates.md).
+Use the communication examples here as starting points and adapt them to your supplier, utility, and executive stakeholder workflows.
 
 ## Escalation Protocols
 
@@ -224,6 +224,5 @@ Track monthly, review quarterly with finance and sustainability:
 
 ## Additional Resources
 
-- For detailed decision frameworks on procurement strategy, PPA evaluation, hedging, and multi-facility optimization, see [decision-frameworks.md](references/decision-frameworks.md)
+- Maintain an internal hedge policy, approved counterparty list, and tariff-change calendar alongside this skill.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Keep facility-specific load shapes and utility contract metadata close to the planning workflow so recommendations stay grounded in real demand patterns.
-- For communication templates covering RFPs, PPA negotiations, rate cases, and internal reporting, see [communication-templates.md](references/communication-templates.md)

skills/inventory-demand-planning/SKILL.md

@@ -10,7 +10,7 @@ description: >
   managing promotions, or optimizing inventory levels.
 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
@@ -176,7 +176,7 @@ If flagged, initiate markdown at 30% off for 4 weeks. If still not moving, escal
 
 ## 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. **New product launch with zero history:** Analogous item profiling is your only tool. Select analogs carefully — match on price point, category, brand tier, and target demographic, not just product type. Commit a conservative initial buy (60% of analog-based forecast) and build in weekly auto-replenishment triggers.
 
@@ -205,7 +205,7 @@ Brief summaries here. Full analysis in [edge-cases.md](references/edge-cases.md)
 - **Promotional forecast submission:** Structured, with baseline, lift, and post-promo dip called out separately. Include assumptions and confidence range. "Baseline: 500 units/week. Promotional lift estimate: 180% (900 incremental). Post-promo dip: −35% for 2 weeks. Confidence: ±25%."
 - **New product forecast assumptions:** Document every assumption explicitly so it can be audited at post-mortem. "Based on analogs [list], we project 200 units/week in weeks 1–4, declining to 120 units/week by week 8. Assumptions: price point $X, distribution to 80 doors, no competitive launch in window."
 
-Brief templates above. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+Brief templates appear above. Adapt them to your supplier, sales, and operations planning workflows before using them in production.
 
 ## Escalation Protocols
 
@@ -243,6 +243,5 @@ Track weekly and trend monthly:
 
 ## Additional Resources
 
-- For detailed decision frameworks, optimization models, and method selection trees, see [decision-frameworks.md](references/decision-frameworks.md)
+- Pair this skill with your SKU segmentation model, service-level policy, and planner override audit log.
-- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- Store post-mortems for promotion misses, vendor delays, and forecast overrides next to the planning workflow so the edge cases stay actionable.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)

skills/logistics-exception-management/SKILL.md

@@ -9,7 +9,7 @@ description: >
   or carrier disputes.
 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
@@ -142,7 +142,7 @@ When multiple exceptions are active simultaneously (common during peak season or
 
 ## Key Edge Cases
 
-These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where the obvious approach is wrong. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **Pharma reefer failure with disputed temps:** Carrier shows correct set-point; your Sensitech data shows excursion. The dispute is about sensor placement and pre-cooling. Never accept carrier's single-point reading — demand continuous data logger download.
 
@@ -174,7 +174,7 @@ Match communication tone to situation severity and relationship:
 
 ### Key Templates
 
-Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+Brief templates appear below. Adapt them to your carrier, customer, and insurance workflows before using them in production.
 
 **Initial carrier inquiry:** Subject: `Exception Notice — PRO# {pro} / BOL# {bol}`. State: what happened, what you need (ETA update, inspection, OS&D report), and by when.
 
@@ -218,6 +218,5 @@ Track these metrics weekly and trend monthly:
 
 ## Additional Resources
 
-- For detailed decision frameworks, escalation matrices, and mode-specific workflows, see [decision-frameworks.md](references/decision-frameworks.md)
+- Pair this skill with your internal claims deadlines, mode-specific escalation matrix, and insurer notice requirements.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Keep carrier-specific proof-of-delivery rules and OS&D checklists near the team that will execute the playbooks.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)

skills/production-scheduling/SKILL.md

@@ -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)
+- Pair this skill with your constraint hierarchy, frozen-window policy, and expedite-approval thresholds.
-- For the comprehensive edge case library with full resolution playbooks, see [edge-cases.md](references/edge-cases.md)
+- Record actual schedule-adherence failures and root causes beside the workflow so the sequencing rules improve over time.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)

skills/quality-nonconformance/SKILL.md

@@ -10,7 +10,7 @@ description: >
   managing CAPAs, interpreting SPC data, or handling supplier quality issues.
 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
@@ -45,7 +45,7 @@ You are a senior quality engineer with 15+ years in regulated manufacturing envi
 ## Examples
 
 - **Incoming inspection failure**: A lot of 10,000 molded components fails AQL sampling at Level II. Defect is a dimensional deviation of +0.15mm on a critical-to-function feature. Walk through containment, supplier notification, root cause investigation (tooling wear), skip-lot suspension, and SCAR issuance.
-- **SPC signal interpretation**: X-bar chart on a filling line shows 7 consecutive points above the center line (Western Electric Rule 3). Process is still within specification limits. Determine whether to stop the line (assignable cause investigation) or continue production (and why "in spec" is not the same as "in control").
+- **SPC signal interpretation**: X-bar chart on a filling line shows 9 consecutive points above the center line (Western Electric Rule 2). Process is still within specification limits. Determine whether to stop the line (assignable cause investigation) or continue production (and why "in spec" is not the same as "in control").
 - **Customer complaint CAPA**: Automotive OEM customer reports 3 field failures in 500 units, all with the same failure mode. Build the 8D response, perform fault tree analysis, identify the escape point in final test, and design verification testing for the corrective action.
 
 ## Core Knowledge
@@ -180,7 +180,7 @@ Before closing any CAPA, verify:
 
 ## Key Edge Cases
 
-These are situations where the obvious approach is wrong. Brief summaries here — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where the obvious approach is wrong. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **Customer-reported field failure with no internal detection:** Your inspection and testing passed this lot, but customer field data shows failures. The instinct is to question the customer's data — resist it. Check whether your inspection plan covers the actual failure mode. Often, field failures expose gaps in test coverage rather than test execution errors.
 
@@ -212,7 +212,7 @@ Match communication tone to situation severity and audience:
 
 ### Key Templates
 
-Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+Brief templates appear below. Adapt them to your MRB, supplier quality, and CAPA workflows before using them in production.
 
 **NCR Notification (internal):** Subject: `NCR-{number}: {part_number} — {defect_summary}`. State: what was found, specification violated, quantity affected, current containment status, and initial assessment of scope.
 
@@ -256,6 +256,5 @@ Track these metrics weekly and trend monthly:
 
 ## Additional Resources
 
-- For detailed decision frameworks, MRB processes, and SPC decision logic, see [decision-frameworks.md](references/decision-frameworks.md)
+- Pair this skill with your NCR template, disposition authority matrix, and SPC rule set so investigators use the same definitions every time.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Keep CAPA closure criteria and effectiveness-check evidence requirements beside the workflow before using it in production.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)

skills/returns-reverse-logistics/SKILL.md

@@ -10,7 +10,7 @@ description: >
   detection, or warranty claims.
 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
@@ -164,7 +164,7 @@ When a return falls outside standard policy, evaluate in this order:
 
 ## Key Edge Cases
 
-These are situations where standard workflows fail. Brief summaries — see [edge-cases.md](references/edge-cases.md) for full analysis.
+These are situations where standard workflows fail. Brief summaries are included here so you can expand them into project-specific playbooks if needed.
 
 1. **High-value electronics with firmware wiped:** Customer returns a laptop claiming defect, but the unit has been factory-reset and shows 6 months of battery cycle count. The device was used extensively and is now being returned as "defective" — grading must look beyond the clean software state.
 
@@ -194,7 +194,7 @@ These are situations where standard workflows fail. Brief summaries — see [edg
 
 ### Key Templates
 
-Brief templates below. Full versions with variables in [communication-templates.md](references/communication-templates.md).
+Brief templates appear below. Adapt them to your fraud, CX, and reverse-logistics workflows before using them in production.
 
 **RMA approval:** Subject: `Return Approved — Order #{order_id}`. Provide: RMA number, return shipping instructions, expected refund timeline, condition requirements.
 
@@ -236,6 +236,5 @@ Level 1 (Returns Associate) → Level 2 (Team Lead, 2 hours) → Level 3 (Return
 
 ## Additional Resources
 
-- For detailed disposition trees, fraud scoring, vendor recovery frameworks, and grading standards, see [decision-frameworks.md](references/decision-frameworks.md)
+- Pair this skill with your grading rubric, fraud review thresholds, and refund authority matrix before using it in production.
-- For the comprehensive edge case library with full analysis, see [edge-cases.md](references/edge-cases.md)
+- Keep restocking standards, hazmat return handling, and liquidation rules near the operating team that will execute the decisions.
-- For complete communication templates with variables and tone guidance, see [communication-templates.md](references/communication-templates.md)