sync

/sync — Publish sprint artifacts to external platforms

You are publishing the current Wheat sprint's artifacts to external platforms. Read CLAUDE.md for sprint context and claims.json for the current state.

Process

1. Compile first: Run wheat compile --summary to ensure compilation is fresh. If compilation is blocked, stop and tell the user to fix issues first.

2. Detect available targets: Check which MCP servers are available:

   • Confluence (via Atlassian MCP): Push the compiled brief as a Confluence page. Use mcp__atlassian__confluence_create_page or mcp__atlassian__confluence_update_page.
   • Slack (via Slack MCP): Post a sprint summary to a channel. Use mcp__slack__send_message.
   • Notion (via Notion MCP): Create a page with the brief content.
   • Local file export: Always available — write to output/ directory.

3. Confluence publish (primary target):

   • Read compilation.json for the certified output
   • Read output/brief.html if it exists, otherwise generate the brief first via /brief
   • Convert the brief to Confluence Storage Format (XHTML subset):
     • Strip <script> and <style> tags
     • Convert inline styles to Confluence macros where possible
     • Wrap code blocks in <ac:structured-macro ac:name="code">
     • Preserve tables, headings, lists as-is (Confluence supports standard HTML)
   • Create or update the page:
     • Page title: [Sprint] <question summary> (truncated to 255 chars)
     • Space key: from user argument or CLAUDE.md connector config
     • Add labels: wheat-sprint, <phase>, claim type tags
   • Add a comment with sync metadata: timestamp, claims hash from compilation certificate, claim count

4. Build sync manifest: After publishing, append a sync record to output/sync-log.json:

   {
     "timestamp": "<ISO>",
     "target": "confluence|slack|notion|file",
     "url": "<published URL or file path>",
     "claims_hash": "<from compilation.json>",
     "claims_count": <number>,
     "phase": "<current phase>"
   }