agentleFS
peterbamuhigirepeterbamuhigire/proposal-skills/skills/domain-delivery/retail-transformation-proposal/SKILL.md

retail-transformation-proposal

Skill11 starsChanged 16 days agoMITView on GitHub

Use when drafting a consulting proposal, EOI, bid, or methodology for retail, omnichannel, e-commerce, POS, merchandising, pricing, promotions, markdowns, loyalty, CRM, fulfilment, returns, store operations, shrink, vendor terms, private label, planogram, new-store opening, or retail KPI/WBR work.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Stop or block the workflow when a required input, permission, or acceptance basis is missing.

    line 37
  2. Distinctive:

    Keep finance doctrine, operational design, technology, and change dependencies visible.

    line 49
  3. Distinctive:

    Read and search are required.

    line 73
  4. Distinctive:

    Before writing the methodology, classify the assignment into one or more modules:

    line 95
  5. Distinctive:

    Use this phase structure unless the tender mandates a different format:

    line 120
  6. Very specific:

    Pilot and capability transfer: test in selected stores/categories/channels, tune process and systems, train owners, and prepare adoption …

    line 127
  7. Distinctive:

    If the proposal touches inventory value, refunds, markdowns, discounts, vendor funding, loyalty liabilities, gift cards, POS settlement, …

    line 161
  8. Distinctive:

    Do not promise accounting treatment, tax treatment, statutory filing, or audit sign-off without the finance doctrine route and human …

    line 167

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Retail Transformation Proposal

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

<!-- dual-compat-start -->

Use When

  • The assignment is for a retailer, distributor with retail branches, supermarket chain, pharmacy chain, fashion/apparel retailer, fuel/convenience network, direct-to-consumer brand, marketplace operator, or omnichannel commerce business.
  • The scope includes retail strategy, diagnostic, transformation, software implementation, e-commerce improvement, POS/inventory rollout, store operations, customer lifecycle, pricing, promotion, markdown, vendor funding, private label, shrink, planogram, or performance management.
  • The proposal must prove retail-specific delivery credibility through workstreams, data asks, deliverables, risks, governance, and acceptance evidence.

Do Not Use When

  • The task is only a generic corporate strategy proposal with no retail operating model.
  • The work is only a static website with no commerce, fulfilment, inventory, or customer lifecycle scope. Use the website proposal strategy instead.
  • The proposal makes accounting, tax, statutory, inventory valuation, or reconciliation commitments without also routing to the finance doctrine engine.

Required Inputs

ArtefactSourceRequired?If absent
Brief, channels, stores, categories, geography, systems, and target outputClient or tender packrequiredStop module selection and request retail scope.
POS, order, SKU, inventory, returns, CRM, vendor, labour, and finance evidenceClient systems and authorised recordsconditionalLabel value cases and diagnostics provisional.

Workflow

Stop or block the workflow when a required input, permission, or acceptance basis is missing. Recover by revising the scope, obtaining evidence, or returning the narrowest qualified draft before proceeding.

  1. Classify the capability modules and exclude adjacent retail topics not in scope.
  2. Build a source-data request and mark unavailable evidence before making performance claims.
  3. Route all money, stock, settlement, tax, and finance-system elements through the external finance doctrine and its quality gate.
  4. Design diagnostic, target operating model, business-case, implementation, pilot, transfer, and performance phases proportionately.
  5. Reconcile deliverables, team, work plan, acceptance, and price; stop if a finance or data dependency remains hidden.

Quality Standards

  • Name the retail modules, channels, data, owners, decisions, and acceptance evidence in scope.
  • Separate verified client performance from assumptions and benchmarks.
  • Keep finance doctrine, operational design, technology, and change dependencies visible.

Anti-Patterns

  • Treating “retail transformation” as all retail topics. Fix: select modules from the actual brief and evidence.
  • Promising margin or sales uplift without client baselines. Fix: define the hypothesis, formula, source, and validation period.
  • Designing from interviews alone. Fix: request transaction, inventory, customer, vendor, labour, and control evidence.
  • Adding finance review after design. Fix: route money and stock flows through doctrine during diagnosis.
  • Ending at recommendations. Fix: include pilot, owner, training, decision gates, rollout, and WBR evidence.

Outputs

ArtefactConsumerAcceptance condition
Retail transformation methodology and deliverable packEvaluator, retail executive, delivery leadsMaps scoped modules to evidence, decisions, controls, pilot, rollout, KPIs, finance gate, and acceptance.

Evidence Produced

EvidenceConsumerAcceptance condition
Retail capability, data, value, and finance traceLinked registersEach claim is sourced or labelled; every money/stock flow names its finance-doctrine route.

Capability and Permission Boundaries

Read and search are required; any edit or external action remains within the explicit authority and permission boundary stated below.

Review defaults to read-only. Client data access must be least-privilege. Price, promotion, assortment, customer communication, vendor claim, system, store, or finance changes require explicit authorised-owner approval.

Degraded Mode

Without retail data, store/channel access, system evidence, or finance doctrine, return a scoped diagnostic and evidence request. Do not claim uplift, compliance, reconciliation, or implementation readiness.

Decision Rules

ConditionActionRisk avoided
Scope spans many capabilitiesPrioritise by binding constraint and evidence“Everything retail” programme
Value case lacks a baselineUse a hypothesis and measurement planInvented ROI
Money, tax, settlement, or stock value is involvedApply external finance doctrine gateIncorrect accounting promise

Worked Example

For a supermarket shrink assignment, reconcile POS, stock counts, adjustments, returns, and settlement evidence; pilot controls in representative stores; measure exceptions; and obtain finance-owner approval before rollout.

Retail Capability Diagnostic

Before writing the methodology, classify the assignment into one or more modules:

ModuleProposal triggerTypical buyer concern
Omnichannel merchandisingstores + web/app/marketplace, channel assortment, product contentinconsistent customer promise and fragmented execution
Assortment and SKU rationalisationrange review, slow-moving SKUs, category rolesexcess complexity, weak availability, poor margin mix
Merchandising calendar and line reviewseasonal campaigns, launches, resetslate decisions and cross-functional congestion
Pricing architectureprice zones, ladders, KVIs, competitor responsemargin leakage and inconsistent price logic
Promotion planningpromotion calendar, funding, campaign mechanicsdiscounting without measured incrementality
Markdown optimisationclearance, aged stock, exit rulesstock value erosion and delayed decisions
Loyalty and CRMretention, tiers, lifecycle journeys, offersunmeasured customer economics and weak repeat purchase
E-commerce CROPDP, cart, checkout, payments, speed, accessibilitytraffic not converting into profitable orders
Search and navigationtaxonomy, attributes, filters, relevancecustomers cannot find or compare products
Fulfilmentinventory availability, routing, pickup, ship-from-storepromise failures and high fulfilment cost
Returnsreturn rate, reverse logistics, disposition, fraudmargin loss and customer friction
Labour and store operationsscheduling, tasking, SOPs, auditsvariable execution and productivity loss
Shrink and loss preventionstock loss, fraud, controls, investigationsunexplained losses and weak accountability
Space and planogramcategory space, facings, compliancepoor space productivity and rollout drift
Vendor terms and trade spendrebates, allowances, co-op, claimsmissed funding and weak commercial governance
Private labelbrand role, sourcing, cost, launchmargin opportunity with quality and cost risk
New-store openingsite readiness, systems, staffing, launchopening delays and avoidable first-month failures
KPI dashboard and WBRdashboards, metrics, cadence, actionsmeetings without source-backed decisions

Methodology Pattern

Use this phase structure unless the tender mandates a different format:

  1. Mobilise and evidence request: confirm scope, stakeholders, workplan, data room, confidentiality, and decision cadence.
  2. Current-state diagnostic: review data, systems, stores/channels, workflows, controls, customer journey, and management reports.
  3. Retail operating-model design: define target capabilities, processes, roles, decision rights, data model, controls, KPIs, and governance cadence.
  4. Business case and prioritisation: quantify or qualify value drivers without inventing market or financial figures; separate verified client data from assumptions.
  5. Implementation roadmap: sequence workstreams, quick wins, dependencies, technology changes, training, pilots, rollout, and change management.
  6. Pilot and capability transfer: test in selected stores/categories/channels, tune process and systems, train owners, and prepare adoption evidence.
  7. Performance management: establish dashboards, weekly business review actions, benefits tracking, and post-implementation improvement loop.

Deliverables Menu

Select only deliverables that match the assignment:

  • Retail diagnostic report with capability scorecard and binding constraints.
  • SKU/category/price/promotion/markdown opportunity register.
  • Customer journey and omnichannel service blueprint.
  • Product data, taxonomy, search, PDP, checkout, fulfilment, and returns requirement pack.
  • Store SOP, labour, audit, and tasking improvement pack.
  • Shrink/loss-prevention control matrix and investigation workflow.
  • Vendor funding and trade-spend recovery framework.
  • Private-label launch and landed-cost readiness checklist.
  • Planogram and space productivity governance pack.
  • Retail KPI dictionary, dashboard specification, and weekly business review cadence.
  • Implementation roadmap with owners, dependencies, risks, milestones, and acceptance evidence.
  • Training, handover, and capability-transfer materials.

Data Ask

A credible retail proposal asks for the source evidence required to deliver the work:

  • SKU master, category hierarchy, product attributes, product content, prices, promotions, markdowns.
  • Sales, margin, inventory, stock count, returns, refunds, shrink, vendor funding, and fulfilment data.
  • Store list, store formats, labour schedules, task lists, SOPs, audit results, new-store opening checklists.
  • Web analytics, search logs, zero-result queries, product page events, cart and checkout events, payment failures.
  • Loyalty/CRM segments, campaign results, opt-in records, voucher/reward issuance and redemption.
  • Vendor agreements, rebate/allowance rules, claim evidence, recovery and dispute reports.
  • Existing dashboard packs, weekly trading review decks, action logs, and finance reconciliations.

Finance and Accounting Route

If the proposal touches inventory value, refunds, markdowns, discounts, vendor funding, loyalty liabilities, gift cards, POS settlement, mobile money, card settlement, cash drawer, shrink, or management reporting, also load:

  • skills/domain-delivery/accounting-finance-advisory/SKILL.md
  • skills/strategy-positioning/embedded-accounting-engine-proposal/SKILL.md where a system replaces bookkeeping/ERP workflows
  • finance doctrine engine skill retail-and-pos-accounting-pack, resolved through the cross-engine route in AGENTS.md

Do not promise accounting treatment, tax treatment, statutory filing, or audit sign-off without the finance doctrine route and human reviewer caveat.

Risk Register Starters

RiskProposal mitigation
Weak data qualityBegin with data inventory, quality checks, source reconciliation, and explicit assumption log.
Scope becomes "everything retail"Use capability modules, phase gates, and a prioritised backlog.
Store teams reject head-office processPilot in representative stores, co-design SOPs, and include field feedback loops.
Finance controls are added lateRoute finance/control review during diagnostic and design, not after implementation.
Technology work outruns operating designDefine process, roles, data, controls, and acceptance tests before build or configuration.
Vendor funding claims lack evidenceRequire agreement register, claim basis, source transaction linkage, and dispute workflow.
Dashboards do not drive actionInclude metric owners, WBR cadence, action log, and decision rights.

Output Checks

  • Does the proposal name the exact retail capability modules in scope?
  • Does the methodology ask for the right source data instead of relying on interviews only?
  • Are deliverables concrete enough for the evaluator to see what will be produced?
  • Are store, digital, fulfilment, finance, and executive stakeholders represented where relevant?
  • Are finance/control gates visible for inventory, refunds, markdowns, discounts, vendor funding, shrink, POS, and dashboards?
  • Does the workplan include pilot, rollout, training, and performance review instead of ending at recommendations?
  • Are claims about value, market size, ROI, and benchmarks sourced or explicitly framed as assumptions?

Evidence Basis

This skill is based on the internal digital-research-engine project umbrex-retail-playbooks-engine-enhancement, which extracted the public Umbrex retail playbook corpus on 2026-06-25. Umbrex is used as source evidence for retail project taxonomy and topic coverage, not as proof of client-specific facts, financial benchmarks, or legal/accounting treatment.

<!-- dual-compat-end -->

References

  • Proposal skills router for repository-wide routing and mandatory quality gates.
  • ../accounting-finance-advisory/SKILL.md for the local proposal handoff to external finance doctrine.
  • ../data-management/SKILL.md for retail-data lifecycle and control design.
  • ../change-management/SKILL.md for store, head-office, and digital-channel adoption.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.