All authors
Claude Skills by Manoj-11-Dahal
github.com/Manoj-11-Dahal15,860 skills0 installs0 views
- Retail Ops Pricing Change Impact TraceUse when a version, rule, source, or stakeholder change may affect pricing and promotion setup review to produce a before/after change record and impact map for the promotion QA worksheet. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Retail Ops Pricing Closeout Handoff LedgerUse when a pricing and promotion setup review work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the promotion QA worksheet 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; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Retail Ops Pricing Completeness ReconciliationUse when the pricing and promotion setup review workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the promotion QA worksheet 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; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, brow...Votes: 0GitHub stars: 2
- Retail Ops Pricing Exception Triage QueueUse when the pricing and promotion setup review workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the promotion QA worksheet 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; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browser, test, an...Votes: 0GitHub stars: 2
- Retail Ops Pricing Recovery Readiness DrillUse when the pricing and promotion setup review workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the promotion QA worksheet 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; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browse...Votes: 0GitHub stars: 2
- Retail Ops Pricing Scenario Sensitivity MatrixUse when the pricing and promotion setup review team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the promotion QA worksheet with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browser, test, and writ...Votes: 0GitHub stars: 2
- Retail Ops Pricing Scope Intake GateUse when a new pricing and promotion setup review request needs a bounded work scope to produce a scoped intake card for the promotion QA worksheet. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; all rules match the approved brief and changes stay in draft pending authorized publication. 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 Pricing Source Provenance LedgerUse when a decision about pricing and promotion setup review depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the promotion QA worksheet. Success means each material claim has a source, version/date, location, and confidence note; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Retail Ops Pricing Threshold Rule CheckUse when a pricing and promotion setup review decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the promotion QA worksheet 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; all rules match the approved brief and changes stay in draft pending authorized publication. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Retail Ops Returns Approval Evidence PacketUse when a returns and refund operations analysis result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use...Votes: 0GitHub stars: 2
- Retail Ops Returns Change Impact TraceUse when a version, rule, source, or stakeholder change may affect returns and refund operations analysis to produce a before/after change record and impact map for the returns disposition evidence brief. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fetch, read, browser, test, and...Votes: 0GitHub stars: 2
- Retail Ops Returns Closeout Handoff LedgerUse when a returns and refund operations analysis work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fet...Votes: 0GitHub stars: 2
- Retail Ops Returns Completeness ReconciliationUse when the returns and refund operations analysis workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configur...Votes: 0GitHub stars: 2
- Retail Ops Returns Exception Triage QueueUse when the returns and refund operations analysis workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fe...Votes: 0GitHub stars: 2
- Retail Ops Returns Recovery Readiness DrillUse when the returns and refund operations analysis workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured...Votes: 0GitHub stars: 2
- Retail Ops Returns Scenario Sensitivity MatrixUse when the returns and refund operations analysis team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the returns disposition evidence brief with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fetch, r...Votes: 0GitHub stars: 2
- Retail Ops Returns Scope Intake GateUse when a new returns and refund operations analysis request needs a bounded work scope to produce a scoped intake card for the returns disposition evidence brief. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record...Votes: 0GitHub stars: 2
- Retail Ops Returns Source Provenance LedgerUse when a decision about returns and refund operations analysis depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the returns disposition evidence brief. Success means each material claim has a source, version/date, location, and confidence note; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use configured search, fetch, read, browser, test, and write capabilities only when rel...Votes: 0GitHub stars: 2
- Retail Ops Returns Threshold Rule CheckUse when a returns and refund operations analysis decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the returns disposition 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; trends are aggregated, individual refund or fraud decisions remain human-reviewed, and counts reconcile. Use co...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Approval Evidence PacketUse when a store operations and labor readiness result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the store readiness handoff 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Change Impact TraceUse when a version, rule, source, or stakeholder change may affect store operations and labor readiness to produce a before/after change record and impact map for the store readiness handoff. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and write capabilities only when r...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Closeout Handoff LedgerUse when a store operations and labor readiness work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the store readiness 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and wr...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Completeness ReconciliationUse when the store operations and labor readiness workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the store readiness 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Exception Triage QueueUse when the store operations and labor readiness workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the store readiness 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and w...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Recovery Readiness DrillUse when the store operations and labor readiness workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the store readiness 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, ...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Scenario Sensitivity MatrixUse when the store operations and labor readiness team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the store readiness handoff with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and write c...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Scope Intake GateUse when a new store operations and labor readiness request needs a bounded work scope to produce a scoped intake card for the store readiness handoff. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to ...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Source Provenance LedgerUse when a decision about store operations and labor readiness depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the store readiness handoff. Success means each material claim has a source, version/date, location, and confidence note; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record ev...Votes: 0GitHub stars: 2
- Retail Ops Store Ops Threshold Rule CheckUse when a store operations and labor readiness decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the store readiness 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; readiness gaps are assigned without changing schedules or making employment decisions. Use configured search, fetch, read, b...Votes: 0GitHub stars: 2
- Supply Ops Demand Approval Evidence PacketUse when a demand planning result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabiliti...Votes: 0GitHub stars: 2
- Supply Ops Demand Change Impact TraceUse when a version, rule, source, or stakeholder change may affect demand planning to produce a before/after change record and impact map for the demand plan. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record eviden...Votes: 0GitHub stars: 2
- Supply Ops Demand Closeout Handoff LedgerUse when a demand planning work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant a...Votes: 0GitHub stars: 2
- Supply Ops Demand Completeness ReconciliationUse when the demand planning workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only w...Votes: 0GitHub stars: 2
- Supply Ops Demand Exception Triage QueueUse when the demand planning workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant ...Votes: 0GitHub stars: 2
- Supply Ops Demand Recovery Readiness DrillUse when the demand planning workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only whe...Votes: 0GitHub stars: 2
- Supply Ops Demand Scenario Sensitivity MatrixUse when the demand planning team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the demand plan with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and au...Votes: 0GitHub stars: 2
- Supply Ops Demand Scope Intake GateUse when a new demand planning request needs a bounded work scope to produce a scoped intake card for the demand plan. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes, and seek approv...Votes: 0GitHub stars: 2
- Supply Ops Demand Source Provenance LedgerUse when a decision about demand planning depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the demand plan. Success means each material claim has a source, version/date, location, and confidence note; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three foc...Votes: 0GitHub stars: 2
- Supply Ops Demand Threshold Rule CheckUse when a demand planning decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the demand plan 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; baseline and adjusted demand are separated and every manual override has evidence. Use configured search, fetch, read, browser, test, and write capabilities ...Votes: 0GitHub stars: 2
- Supply Ops Inventory Approval Evidence PacketUse when a inventory policy result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and ...Votes: 0GitHub stars: 2
- Supply Ops Inventory Change Impact TraceUse when a version, rule, source, or stakeholder change may affect inventory policy to produce a before/after change record and impact map for the inventory position. Success means each material difference is tied to affected dependencies, consumers, owners, and a test or explicitly unknown impact; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorize...Votes: 0GitHub stars: 2
- Supply Ops Inventory Closeout Handoff LedgerUse when a inventory policy work item is nearing completion, pause, or transfer to another owner to produce a closeout ledger for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities only...Votes: 0GitHub stars: 2
- Supply Ops Inventory Completeness ReconciliationUse when the inventory policy workflow receives records that must agree across sources, periods, or statuses to produce a reconciliation worksheet for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write cap...Votes: 0GitHub stars: 2
- Supply Ops Inventory Exception Triage QueueUse when the inventory policy workflow has exceptions, missing evidence, or competing priorities to produce a prioritized exception queue for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities onl...Votes: 0GitHub stars: 2
- Supply Ops Inventory Recovery Readiness DrillUse when the inventory policy workflow needs a safe recovery, rollback, replay, or continuity check to produce a recovery-drill record for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capab...Votes: 0GitHub stars: 2
- Supply Ops Inventory Scenario Sensitivity MatrixUse when the inventory policy team needs to compare options under changing assumptions to produce a baseline-plus-scenarios matrix for the inventory position with assumptions and ranges. Success means the baseline is reproducible, scenario inputs are explicit, comparable units are used, and conclusions state uncertainty; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities only when...Votes: 0GitHub stars: 2
- Supply Ops Inventory Scope Intake GateUse when a new inventory policy request needs a bounded work scope to produce a scoped intake card for the inventory position. Success means owner, objective, permitted sources, acceptance condition, exclusions, and deadline are explicit; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinement to three focused passes,...Votes: 0GitHub stars: 2
- Supply Ops Inventory Source Provenance LedgerUse when a decision about inventory policy depends on facts from several records or public sources to produce a source-to-claim provenance ledger for the inventory position. Success means each material claim has a source, version/date, location, and confidence note; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and write capabilities only when relevant and authorized. Record evidence, limit refinem...Votes: 0GitHub stars: 2
- Supply Ops Inventory Threshold Rule CheckUse when a inventory policy decision depends on a limit, eligibility rule, policy, or target to produce a rule-check record for the inventory position 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; available, committed, and in-transit quantities reconcile or remain explicitly unresolved. Use configured search, fetch, read, browser, test, and wri...Votes: 0GitHub stars: 2
- Supply Ops Procurement Approval Evidence PacketUse when a procurement intake result is ready for a human owner to approve, reject, or redirect to produce a decision packet for the purchase request 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; request, quote, budget, and approver align before any order is prepared. Use configured search, fetch, read, browser, test, and write capabilities...Votes: 0GitHub stars: 2