pricing-playbook
Standardized pricing methodology and process guide
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- pricing-playbook
- owner
- pricing-strategist
- scope
- co-price
- inputs
- [ "elasticity-reading", "price-corridor" ]
- status
- active
- outputs
- [ "pricing-policy-set", "scenario-snapshots" ]
- version
- 1.0.0
- relates_to
- [ { "type": "enables", "skill": "scenario-comparison" } ]
- description
- Standardized pricing methodology and process guide
- last_reviewed
- 1787616000000
- prerequisites
- biz_logic.md §9; PricingPolicy persistence; snapshot comparison actions
03 SKILL.md 正文
Pricing Strategy Playbook Skill
Purpose
Turn commercial objectives into an explicit, testable two-layer policy set
(biz_logic.md §9) and quantify each option against a frozen baseline through
the snapshot comparison engine.
Layer Model
| Layer | Audience | Instruments | Price path affected |
|---|---|---|---|
| Wholesale (B2B) | trade lines / channels | quantity tiers · revenue rebates · promotion allowances (+deferred IS/CF timing) | realized supply price P_S,c |
| Consumer (B2C) | channels × products | EDLP · High-Low cycles · lifecycle Markdown · rule-based Dynamic | consumer MSRP monthly path |
Procedure
- Frame — confirm objective KPIs with the client (margin floor, volume target, cash timing) and the channel/trade-line scope for each candidate policy.
- Author policies — express as
PricingPolicyrows (layer,kind, JSONscope/params,effectiveFrom,recognitionLagMonths). Validate through the Zod schemas insrc/lib/engine/pricing-policy.ts. - Simulate — freeze baseline into
ScenarioSnapshot; freeze policy variant; runcompareSnapshotsActionfor the yearly revenue/margin/units tri-view. - Read results — realization shift (§6.2), promo-month margin erosion, wholesale stack cap hits (GUA-PW2), dynamic clamp ceiling/floor touches.
- Recommend — ledger-cited findings only; hand to
engagement-directorfor the deliverable gate.
Boundaries
- Every figure cites a computation-ledger id; no invented numbers.
- Wholesale stack is hard-capped at 40% (GUA-PW2) — proposals above it are invalid.
- Conflicting consumer scopes are configuration errors, not features to average.
Context
See docs/co-price.context.md for project context and the consulting engagement lifecycle.
When to Use
- When a co-price task requires Standardized pricing methodology and process guide within the engagement lifecycle.
Execution Steps
- Receive dispatch from PM with task parameters and document anchors.
- Execute the skill procedure against the artifacts named in the task scope.
- Report results to the dispatching agent with evidence links.
Output Format
Structured markdown report delivered to the dispatching agent, citing document anchors (for example [Ref: biz_logic.*]) where applicable.
Related Skills
- Owner agent:
pricing-strategist. Seevariant.jsonskills registry for the full co-price skill set.
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.