跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
效率与协作

business-docs-sync

Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.

Ibrahim-3d · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add Ibrahim-3d/orchestrator-supaconductor --skill business-docs-sync

技能说明


name: business-docs-sync description: Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.

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:

DocumentLocationContainsUpdate When
product.mdconductor/product.mdPRD, deliverables, pricing tiers, personas, user storiesAny product feature/pricing change
business-strategy.mdconductor/business-strategy.mdGTM, revenue projections, break-even, moat, risk registerPricing, cost structure, or competitive position changes
tech-stack.mdconductor/tech-stack.mdArchitecture, model strategy, API integrations, cost projectionsTechnology decisions, model changes, new integrations
Data filessrc/data/pricing.json (or equivalent)UI pricing tiers, features, comparison dataAny 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:

DocumentLocationDerives FromUpdate When
product-roadmap.mdconductor/product-roadmap.mdproduct.md, business-strategy.mdRoadmap phases, pricing evolution, or track structure changes
product-guidelines.mdconductor/product-guidelines.mdproduct.mdUI copy, paywall text, pricing display rules
prompts.mdconductor/prompts.mdproduct.md, tech-stack.mdAsset changes, model changes, prompt strategy
screen-map.mdconductor/screen-map.mdproduct.mdNew 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:

SkillLocationReflectsUpdate When
Product knowledge skill${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.mdproduct.md, pricing model, personasProduct rules, pricing tiers, personas change
Integration skills${CLAUDE_PLUGIN_ROOT}/skills/*/SKILL.mdtech-stack.md, API docsSDK 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)

EventWhat TriggersSync Action
Track CompletionAny track marked COMPLETERun Business Doc Sync Checklist (Step 5.5)
Evaluation CompleteAny evaluation with product decisionsRun Business Doc Sync Checklist (Step 5.5)
Pricing ChangePrice point, tier, or feature list changesUpdate Tier 1-3 pricing sections
Model Strategy ChangeAI model, SDK, or cost structure changesUpdate tech-stack.md, skills, cost projections
New Package/Tier AddedNew pricing tier or product bundleUpdate ALL Tier 1-3 pricing sections

Manual Triggers

TriggerWhen
/conductor sync-docsUser explicitly requests doc sync
Discovered during planningAgent 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
阅读完整来源 ↗