/business-docs-sync

Business Document Sync Strategy

Ensures all business strategy, pricing, and product documents stay synchronized when product decisions change during any track execution or evaluation.

When to Use This Skill

• After ANY track completion that changes pricing, model strategy, or business decisions
• After ANY evaluation that produces product decisions or action items
• During `loop-executor` Step 3 when a task modifies business-impacting logic
• During `loop-execution-evaluator` Step 4 as part of the structural checks
• When creating new tracks that depend on business context (pricing, GTM, personas, model strategy)

The Problem This Solves

Projects accumulate business strategy documents across multiple locations:

• Conductor root docs
• Strategy and planning tracks
• Agent skills
• JSON data files (pricing, config)
• Research tracks

When a product decision is made (e.g., adding a new pricing tier, changing the model strategy), these documents become stale unless explicitly synced. The next agent session reads outdated info and makes wrong decisions.

Business Document Registry

Tier 1: Source of Truth (MUST be updated first)

These are the canonical documents. When a decision changes, update these FIRST:

| Document | Location | Contains | Update When | |----------|----------|----------|-------------| | **product.md** | `conductor/product.md` | PRD, deliverables, pricing tiers, personas, user stories | Any product feature/pricing change | | **business-strategy.md** | `conductor/business-strategy.md` | GTM, revenue projections, break-even, moat, risk register | Pricing, cost structure, or competitive position changes | | **tech-stack.md** | `conductor/tech-stack.md` | Architecture, model strategy, API integrations, cost projections | Technology decisions, model changes, new integrations | | **Data files** | `src/data/pricing.json` (or equivalent) | UI pricing tiers, features, comparison data | Any pricing change (tiers, features, price points) |

Tier 2: Derived Documents (Update to match Tier 1)

These documents derive from Tier 1 and must stay consistent:

| Document | Location | Derives From | Update When | |----------|----------|--------------|-------------| | **product-roadmap.md** | `conductor/product-roadmap.md` | product.md, business-strategy.md | Roadmap phases, pricing evolution, or track structure changes | | **product-guidelines.md** | `conductor/product-guidelines.md` | product.md | UI copy, paywall text, pricing display rules | | **prompts.md** | `conductor/prompts.md` | product.md, tech-stack.md | Asset changes, model changes, prompt strategy | | **screen-map.md** | `conductor/screen-map.md` | product.md | New screens, changed user flows |

Tier 3: Skills (Update to match Tier 1 + Tier 2)

Agent skills must reflect current decisions so agents make correct choices:

| Skill | Location | Reflects | Update When | |-------|----------|----------|-------------| | **Product knowledge skill** | `${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.md` | product.md, pricing model, personas | Product rules, pricing tiers, personas change | | **Integration skills** | `${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.md` | tech-stack.md, API docs | SDK patterns, model strategy, cost data, API changes |

Tier 4: Strategy Archives (Reference only — do NOT update)

Historical research outputs capture decisions AT THE TIME they were made and should NOT be retroactively edited.

**Exception:** If a Tier 4 document is the ONLY place a specific decision is documented, add a "Superseded" note at the top pointing to the updated Tier 1 doc.

Sync Trigger Events

Automatic Triggers (Built into Evaluate-Loop)

| Event | What Triggers | Sync Action | |-------|---------------|-------------| | **Track Completion** | Any track marked COMPLETE | Run Business Doc Sync Checklist (Step 5.5) | | **Evaluation Complete** | Any evaluation with product decisions | Run Business Doc Sync Checklist (Step 5.5) | | **Pricing Change** | Price point, tier, or feature list changes | Update Tier 1-3 pricing sections | | **Model Strategy Change** | AI model, SDK, or cost structure changes | Update tech-stack.md, skills, cost projections | | **New Package/Tier Added** | New pricing tier or product bundle | Update ALL Tier 1-3 pricing sections |

Manual Triggers

| Trigger | When | |---------|------| | `/conductor sync-docs` | User explicitly requests doc sync | | Discovered during planning | Agent notices stale data while reading docs |

Business Doc Sync Checklist

Run this checklist whenever a sync trigger fires. Check each item and update if stale:

## Business Doc Sync Checklist

**Trigger:** [Describe what changed — e.g., "Added new pricing tier"]
**Date:** [YYYY-MM-DD]

### Tier 1: Source of Truth
- [ ] `conductor/product.md` — Pricing section reflects current tiers and features
- [ ] `conductor/business-strategy.md` — Revenue projections use current pricing; cost analysis uses current model costs
- [ ] `conductor/tech-stack.md` — Model strategy, SDK references, and cost projections are current
- [ ] Data files — UI pricing data matches product.md tiers

### Tier 2: Derived Documents
- [ ] `conductor/product-roadmap.md` — Phase pricing and track descriptions are current
- [ ] `conductor/product-guidelines.md` — Paywall copy, pricing display rules match current tiers
- [ ] `conductor/prompts.md` — Prompt strategy aligns with current model capabilities
- [ ] `conductor/screen-map.md` — Screen list includes any new tier-related screens

### Tier 3: Skills
- [ ] Product knowledge skill — Pricing model, tech stack table, personas current
- [ ] Integration skills — SDK patterns, model names, cost data current

### Verification
- [ ] No document references a price point that doesn't match `product.md`
- [ ] No document references a model name that doesn't match `tech-stack.md`
- [ ] No skill references an SDK pattern that doesn't match the actual codebase
- [ ] Data file tier count and features