All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Retail Ops Fulfillment Change Impact TraceUse when a version, rule, source, or stakeholder change may affect order and fulfillment exception management to produce a before/after change record and impact map for the fulfillment exception handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Closeout Handoff LedgerUse when a order and fulfillment exception management work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the fulfillment exception handoff with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Completeness ReconciliationUse when the order and fulfillment exception management workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the fulfillment exception handoff with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured searc...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Exception Triage QueueUse when the order and fulfillment exception management workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the fulfillment exception handoff with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Recovery Readiness DrillUse when the order and fulfillment exception management workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the fulfillment exception handoff with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search,...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Scenario Sensitivity MatrixUse when the order and fulfillment exception management team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the fulfillment exception handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Scope Intake GateUse when a new order and fulfillment exception management request needs a bounded work scope to produce a scoped intake card for the fulfillment exception handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidenc...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Source Provenance LedgerUse when a decision about order and fulfillment exception management depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the fulfillment exception handoff. Success means each material claim has a source, version/date, location, and confidence note; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant an...Votes: 0GitHub stars: 2
- Retail Ops Fulfillment Threshold Rule CheckUse when a order and fulfillment exception management decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the fulfillment exception handoff showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each exception has a source timestamp and an owner; no shipment or customer message is initiated. Use configured...Votes: 0GitHub stars: 2
- Retail Ops Inventory Approval Evidence PacketUse when a retail inventory and replenishment planning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the replenishment exception queue containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Retail Ops Inventory Change Impact TraceUse when a version, rule, source, or stakeholder change may affect retail inventory and replenishment planning to produce a before/after change record and impact map for the replenishment exception queue. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, and write capabilities only wh...Votes: 0GitHub stars: 2
- Retail Ops Inventory Closeout Handoff LedgerUse when a retail inventory and replenishment planning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the replenishment exception queue with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Retail Ops Inventory Completeness ReconciliationUse when the retail inventory and replenishment planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the replenishment exception queue with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, bro...Votes: 0GitHub stars: 2
- Retail Ops Inventory Exception Triage QueueUse when the retail inventory and replenishment planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the replenishment exception queue with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, a...Votes: 0GitHub stars: 2
- Retail Ops Inventory Recovery Readiness DrillUse when the retail inventory and replenishment planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the replenishment exception queue with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Retail Ops Inventory Scenario Sensitivity MatrixUse when the retail inventory and replenishment planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the replenishment exception queue with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Retail Ops Inventory Scope Intake GateUse when a new retail inventory and replenishment planning request needs a bounded work scope to produce a scoped intake card for the replenishment exception queue. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement...Votes: 0GitHub stars: 2
- Retail Ops Inventory Source Provenance LedgerUse when a decision about retail inventory and replenishment planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the replenishment exception queue. Success means each material claim has a source, version/date, location, and confidence note; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Recor...Votes: 0GitHub stars: 2
- Retail Ops Inventory Threshold Rule CheckUse when a retail inventory and replenishment planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the replenishment exception queue showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; quantities reconcile by location and no purchase order or transfer is placed. Use configured search, fetch, rea...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Approval Evidence PacketUse when a retail loyalty-program operations result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the loyalty program reconciliation brief containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use con...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Change Impact TraceUse when a version, rule, source, or stakeholder change may affect retail loyalty-program operations to produce a before/after change record and impact map for the loyalty program reconciliation brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Closeout Handoff LedgerUse when a retail loyalty-program operations work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the loyalty program reconciliation brief with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch, ...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Completeness ReconciliationUse when the retail loyalty-program operations workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the loyalty program reconciliation brief with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured s...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Exception Triage QueueUse when the retail loyalty-program operations workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the loyalty program reconciliation brief with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch,...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Recovery Readiness DrillUse when the retail loyalty-program operations workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the loyalty program reconciliation brief with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured sea...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Scenario Sensitivity MatrixUse when the retail loyalty-program operations team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the loyalty program reconciliation brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Scope Intake GateUse when a new retail loyalty-program operations request needs a bounded work scope to produce a scoped intake card for the loyalty program reconciliation brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evi...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Source Provenance LedgerUse when a decision about retail loyalty-program operations depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the loyalty program reconciliation brief. Success means each material claim has a source, version/date, location, and confidence note; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use configured search, fetch, read, browser, test, and write capabilities only when relevan...Votes: 0GitHub stars: 2
- Retail Ops Loyalty Threshold Rule CheckUse when a retail loyalty-program operations decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the loyalty program reconciliation brief showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; member and reward counts reconcile, personal data is minimized, and rule changes remain approval-gated. Use config...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Approval Evidence PacketUse when a marketplace policy and listing compliance result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the marketplace requirement map containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured ...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Change Impact TraceUse when a version, rule, source, or stakeholder change may affect marketplace policy and listing compliance to produce a before/after change record and impact map for the marketplace requirement map. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Closeout Handoff LedgerUse when a marketplace policy and listing compliance work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the marketplace requirement map with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, br...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Completeness ReconciliationUse when the marketplace policy and listing compliance workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the marketplace requirement map with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, f...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Exception Triage QueueUse when the marketplace policy and listing compliance workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the marketplace requirement map with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Recovery Readiness DrillUse when the marketplace policy and listing compliance workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the marketplace requirement map with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fet...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Scenario Sensitivity MatrixUse when the marketplace policy and listing compliance team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the marketplace requirement map with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Scope Intake GateUse when a new marketplace policy and listing compliance request needs a bounded work scope to produce a scoped intake card for the marketplace requirement map. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, l...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Source Provenance LedgerUse when a decision about marketplace policy and listing compliance depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the marketplace requirement map. Success means each material claim has a source, version/date, location, and confidence note; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2
- Retail Ops Marketplace Threshold Rule CheckUse when a marketplace policy and listing compliance decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the marketplace requirement map showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; each requirement links to the applicable channel and region; uncertain enforcement is escalated. Use configured sea...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Approval Evidence PacketUse when a assortment and merchandising review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the assortment decision evidence brief containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configure...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Change Impact TraceUse when a version, rule, source, or stakeholder change may affect assortment and merchandising review to produce a before/after change record and impact map for the assortment decision evidence brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Closeout Handoff LedgerUse when a assortment and merchandising review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the assortment decision evidence brief with status, evidence, owner, and retention state. Success means all deliverables, unresolved items, approvals, and next owners are recorded, and the stop reason is explicit; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read, ...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Completeness ReconciliationUse when the assortment and merchandising review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the assortment decision evidence brief with matched, unmatched, and unresolved rows. Success means counts and key fields reconcile or every variance is quantified, sourced, and left unresolved for an owner; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search,...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Exception Triage QueueUse when the assortment and merchandising review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the assortment decision evidence brief with evidence, owner, and next action. Success means every exception has a severity rationale, source, owner or explicit unassigned state, and a bounded next step; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read,...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Recovery Readiness DrillUse when the assortment and merchandising review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the assortment decision evidence brief with starting state, test, and observed outcome. Success means the dry-run or approved non-production drill meets the predeclared recovery target and leaves the baseline intact; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, f...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Scenario Sensitivity MatrixUse when the assortment and merchandising review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the assortment decision evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read, brows...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Scope Intake GateUse when a new assortment and merchandising review request needs a bounded work scope to produce a scoped intake card for the assortment decision evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence,...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Source Provenance LedgerUse when a decision about assortment and merchandising review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the assortment decision evidence brief. Success means each material claim has a source, version/date, location, and confidence note; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and ...Votes: 0GitHub stars: 2
- Retail Ops Merchandising Threshold Rule CheckUse when a assortment and merchandising review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the assortment decision evidence brief showing source, units, boundary case, and outcome. Success means the rule source and effective date are verified, units and scope match, and borderline cases are flagged rather than auto-approved; comparisons use consistent periods and no SKU is added or removed without merchandising approval. Use configured s...Votes: 0GitHub stars: 2
- Retail Ops Pricing Approval Evidence PacketUse when a pricing and promotion setup review result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the promotion QA worksheet containing options, evidence, risks, and open questions. Success means the decision owner, requested decision, source evidence, alternatives, uncertainty, and consequence of no action are all visible; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, r...Votes: 0GitHub stars: 2