skills.rest
AhmedElhadarey
AhmedElhadareyCOMMUNITY
Explore all skills by this author →
GitHub

business-docs-sync

Synchronize stale business documentation when track decisions change.

2|Updated Feb 25, 2026
Search Tags:#documentation#strategy#sync#knowledge-management#product-management#version-control#business-docs
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill business-docs-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: business-docs-sync
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/business-docs-sync
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill business-docs-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronize stale business documentation when track decisions change. This ensures all stakeholders work from a single source of truth.

Core Features & Use Cases

  • Centralized updates: propagate changes to conductor/product.md, conductor/business-strategy.md, and related data.
  • Consistency checks: verify derived documents match Tier 1 updates and prevent staleness across tracks.
  • Manual & automatic triggers: supports automatic sync after track/evaluation events or manual /conductor sync-docs invocations.

Quick Start

Run the sync command to align all business documents with the latest decisions.

Frequently Asked Questions about business-docs-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I synchronize business documentation when track decisions change?▼

Synchronize business documentation by triggering a sync workflow that updates Tier 1 sources first, cascades changes to derived documents, and verifies consistency to prevent staleness across tracks.

What is the best way to keep product management docs consistent across strategy updates?▼

Keeping product management docs consistent requires a defined sync workflow that propagates changes to product and business-strategy files, then performs consistency checks to verify derived documents match Tier 1 updates.

How does automatic business docs sync work after evaluation outcomes?▼

Automatic business docs sync works by triggering after track completion or evaluation events, applying product decisions to update Tier 1 sources and cascading those changes to all related derived documents.

Can I manually sync stale business documents without waiting for track events?▼

Yes, you can manually sync stale business documents by invoking the sync command, which aligns all business documents with the latest decisions and verifies consistency across the track.

Why does business documentation become stale across product management tracks?▼

Business documentation becomes stale when track decisions change but derived documents are not updated, which this sync workflow solves by cascading Tier 1 source updates and running consistency checks.

Do I need version control to update derived business strategy documents?▼

Version control supports the sync workflow by tracking updates to business strategy documents, ensuring that changes to Tier 1 sources cascade correctly and derived documents remain consistent.

Related Skills

Explore More Product & Management Skills→
blackwell-systemsblackwell-systems
102

lsp-docs

Orchestrates three tiers of symbol documentation: live hover, offline toolchain, and source navigation.

Community
Advanced
fgrehmfgrehm

blog-fact-checking

Verify blog claims against official documentation using web_fetch.

Community
Basic
rodmena-limitedrodmena-limited
3

moai-foundation-claude

Create, configure, and manage Claude Code Skills with templates and tools.

Official
Advanced
Harshal1841AHarshal1841A

tech-debt-tracker

Detect, analyze, and track technical debt across codebases.

Community
Intermediate