Synchronize project documentation after track completion. Use when a track reaches completed status and product, tech-stack, or guidelines documents may need updates.
/plugin marketplace add vinothpandian/v-marketplace/plugin install claude-conductor@v-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides the protocol for synchronizing project-level documentation after completing a Conductor track.
Only execute this protocol when:
[x] status in the tracks file/claude-conductor:implement command has finished all tasksDo NOT execute for:
Inform the user:
"I am now synchronizing the project-level documentation with the completed track's specifications."
Read the completed track's conductor/tracks/<track_id>/spec.md into context.
Read the following files:
conductor/product.mdconductor/product-guidelines.mdconductor/tech-stack.mdconductor/product.mdCondition for Update: Determine if the completed feature or bug fix significantly impacts the description of the product itself.
Examples that warrant updates:
Examples that do NOT warrant updates:
Propose and Confirm: If an update is needed:
"Based on the completed track, I propose the following updates to
product.md:"[Proposed changes in diff format]"Do you approve these changes? (yes/no)"
Action: Only after explicit user confirmation, apply the edits. Record whether this file was changed.
conductor/tech-stack.mdCondition for Update: Determine if significant changes in the technology stack occurred.
Examples that warrant updates:
Examples that do NOT warrant updates:
Propose and Confirm: If an update is needed:
"Based on the completed track, I propose the following updates to
tech-stack.md:"[Proposed changes in diff format]"Do you approve these changes? (yes/no)"
Action: Only after explicit user confirmation, apply the edits. Record whether this file was changed.
conductor/product-guidelines.md (Strictly Controlled)CRITICAL WARNING: This file defines the core identity and communication style of the product. It should be modified with extreme caution and ONLY in cases of significant strategic shifts.
Valid reasons to update:
Invalid reasons (do NOT update):
Condition for Update:
You may ONLY propose an update if the track's spec.md explicitly describes a change that directly impacts branding, voice, tone, or other core product guidelines.
Propose and Confirm (with warning): If the strict conditions are met:
"WARNING: The completed track suggests a change to the core product guidelines. This is an unusual step. Please review carefully:"
[Proposed changes in diff format]"Do you approve these critical changes to
product-guidelines.md? (yes/no)"
Action: Only after explicit user confirmation, apply the edits. Record whether this file was changed.
Announce completion and provide a summary based on which files were changed.
Example (product.md changed):
"Documentation synchronization is complete.
- Changes made to
product.md: The user-facing description of the product was updated to include the new feature.- No changes needed for
tech-stack.md: The technology stack was not affected.- No changes needed for
product-guidelines.md: Core product guidelines remain unchanged."
Example (no changes):
"Documentation synchronization is complete. No updates were necessary for
product.md,tech-stack.md, orproduct-guidelines.mdbased on the completed track."
If any files were changed:
product.md, tech-stack.md, and/or product-guidelines.mddocs(conductor): Synchronize docs for track '<track_description>'When proposing changes, use diff format for clarity:
# Product Overview
- Our product helps users manage tasks efficiently.
+ Our product helps users manage tasks efficiently with real-time collaboration features.
## Key Features
- Task management
- Due date tracking
+ - Real-time collaboration
+ - Team workspaces
Always wait for explicit user response:
Approval patterns:
Rejection patterns:
If unclear, ask for clarification before proceeding.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.