daily-meeting-update

原文涵盖的主题

• Daily Meeting Update
• Workflow
• Phase 1: Detect & Offer Integrations
• Step 1: Silent Detection
• Step 2: Offer GitHub/Jira Integrations (if available)
• Step 3: Pull GitHub/Jira Data (if approved)
• Step 4: Offer Claude Code History
• Phase 2: Interview (with insights)

Generate a daily standup/meeting update through an interactive interview. Never assume tools are configured—ask first. -- -- Check for available integrations silently (suppress errors, don't show to user): | Integration | Detection | |-------------|-----------| | Claude Code History | /.claude/projects directory exists with .jsonl files | | GitHub CLI | gh auth status succeeds | | Jira CLI | jira command exists | | Atlassian MCP | mcpatlassian tools available | | Git | Inside a git repository | Claude Code users: Use AskUserQuestionTool tool for all questions in this phase. GitHub/Git: If HASGH or HASGIT: If yes: Jira: If HASJIRACLI or HASATLASSIANMCP: GitHub/Git — For each approved repo: Commits by user since yesterday PRs opened/merged by user Reviews done by user Jira — Tickets assigned to user, updated in last 24h Key insight: Store results to use as context in Phase 2 interview. This integration captures everything you worked on with Claude Code — useful for recalling work that isn't in git or Jira. Detection: If Claude Code history exists, ask: If yes, run the digest script: Then present sessions with multiSelect: Use AskUserQuestionTool with multiSelect: true to let user pic

这里只展示节选，请以完整原文和当前要求为准。