Skip to content

fix: add YAML frontmatter to business-docs-sync skill #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
xiaolai wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix: add YAML frontmatter to business-docs-sync skill #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions skills/business-docs-sync/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,8 @@
---
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.

@gemini-code-assist gemini-code-assist Bot Apr 30, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To maintain consistency with other skills in the Evaluate-Loop (such as loop-executor and loop-execution-evaluator), the description should include the step designation and explicit trigger keywords. This ensures the Skill tool and agents can accurately identify and invoke the skill based on the defined workflow.

Suggested change
description: Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
description: "Evaluate-Loop Step 5.5: BUSINESS DOC SYNC. Use when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers. Triggered by: track completion, evaluation complete, or '/conductor sync-docs'."

---

# Business Document Sync Strategy

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