Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/business-document-sync-strategy
Ensures all business strategy, pricing, and product documents stay synchronized when product decisions change during any track execution or evaluation.
Passed 15 of 20 test cases with the skill, and 5 of 20 without it.
and 12 more in the full report
13 fixed4 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
A decision was made to change the paywall text copy and pricing display formatting rules across our client applications. Which Tier 2 document in conductor/ derives from conductor/product.md and handles paywall copy rules?
| Checked | Without skill | With skill |
|---|---|---|
| The response designates conductor/product-guidelines.md as the file to update. | Missed | Passed |
The instructions your model reads when the skill loads.
Ensures all business strategy, pricing, and product documents stay synchronized when product decisions change during any track execution or evaluation.
loop-executor Step 3 when a task modifies business-impacting logicloop-execution-evaluator Step 4 as part of the structural checksProjects accumulate business strategy documents across multiple locations:
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.
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) |
These documents derive from Tier 1 and must stay consistent:
test cases passed, vs 5 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.