@crewpilot/agent 1.0.0 → 2.0.0

package/prompts/skills/daily-digest/SKILL.md

@@ -1,167 +1,188 @@
-# Daily Digest
-
-> **Pillar**: Orchestrate | **ID**: `daily-digest`
-
-## Purpose
-
-Generate a comprehensive daily/weekly work summary by aggregating git activity, board changes, PR status, workflow completions, and knowledge entries — then deliver it via SMTP email or display in chat. Replaces manual status reporting entirely.
-
-## Activation Triggers
-
-- digest, daily report, daily summary, end of day, eod report, what did I do today, status report, send update, update PM, weekly summary, send email, standup report
-
-## Tools Required
-
-- `catalyst_git_log` — get commits for the time period
-- `catalyst_board_my_items` — get board items (opened, closed, in-progress)
-- `catalyst_worker_dashboard` — workflow completions and stats
-- `catalyst_knowledge_timeline` — decisions made in the period
-- `catalyst_exec` — run git/gh commands for additional data
-- `catalyst_notify_send` — deliver the report via email
-
-## Methodology
-
-### Process Flow
-
-```dot
-digraph daily_digest {
-    rankdir=LR;
-    node [shape=box];
-
-    collect [label="Phase 1\nData Collection\n(git, board, PRs,\nworkflows, knowledge)"];
-    generate [label="Phase 2\nReport Generation"];
-    deliver [label="Phase 3\nDelivery\n(email or chat)", shape=doublecircle];
-
-    collect -> generate;
-    generate -> deliver;
-}
-```
-
-### Phase 1 — Data Collection
-
-Gather from all sources for the requested time period (default: today):
-
-**Git Activity:**
-1. Call `catalyst_git_log` with `--since="today 00:00"` (or requested range)
-2. Extract: commit count, files changed, insertions/deletions, branches touched
-3. Group commits by scope/type (feat, fix, refactor, test, docs)
-
-**Board Activity:**
-1. Call `catalyst_exec` with `gh issue list --author=@me --state=all --json number,title,state,updatedAt,labels`
-2. Filter to items updated in the time period
-3. Categorize: created, moved to in-progress, closed/done, commented on
-
-**PR Activity:**
-1. Call `catalyst_exec` with `gh pr list --author=@me --state=all --json number,title,state,createdAt,mergedAt,reviewDecision`
-2. Filter to time period
-3. Categorize: opened, merged, review pending, changes requested
-
-**Workflow Activity:**
-1. Call `catalyst_worker_dashboard` for digital worker stats
-2. Filter completed/failed workflows in the period
-
-**Knowledge:**
-1. Call `catalyst_knowledge_timeline` for decisions and lessons stored today
-
-### Phase 2 — Report Generation
-
-Compose the report in this structure:
-
-```
-📊 Daily Digest — {date} — @{username}
-═══════════════════════════════════════
-
-📝 COMMITS ({count})
-  feat:     {count} — {summary of features}
-  fix:      {count} — {summary of fixes}
-  refactor: {count}
-  test:     {count}
-  other:    {count}
-  
-  Files changed: {N} | +{insertions} / -{deletions}
-
-📋 BOARD ACTIVITY
-  Created:     {N} items ({titles})
-  In Progress: {N} items ({titles})
-  Completed:   {N} items ({titles})
-  Blocked:     {N} items ({titles + reason})
-
-🔀 PULL REQUESTS
-  Opened:   {N} — {PR titles with numbers}
-  Merged:   {N} — {PR titles}
-  Pending:  {N} — {waiting on review / changes requested}
-
-🤖 DIGITAL WORKER
-  Workflows completed: {N}
-  Workflows in progress: {N}
-  Workflows failed: {N}
-
-💡 DECISIONS MADE
-  - {decision 1}
-  - {decision 2}
-
-───────────────────────────────────────
-Tomorrow's focus:
-  - {open items in-progress}
-  - {PRs waiting for review}
-  - {blockers to resolve}
-```
-
-### Phase 3 — Delivery
-
-Based on notification configuration:
-
-**Email (default when recipients configured):**
-1. Call `catalyst_notify_send` with subject: "Daily Digest — {date} — {project name}", body: full report
-2. Email sent automatically via SMTP (no manual interaction needed)
-3. Requires SMTP env vars or `catalyst_notify_configure` to be set up
-
-**Console (fallback when no recipients configured):**
-1. Just display the report in chat
-2. User can copy-paste to email manually
-
-### Phase 4 — Preview & Send
-
-**ALWAYS preview before sending:**
-
-```
-📊 Digest Preview:
-
-{full report}
-
-──────────────
-Send to: {recipient} via email?
-(yes / edit / just show)
-```
-
-- **yes** → send via email (opens mail client with pre-filled content)
-- **edit** → user modifies, re-preview
-- **just show** → output only, don't send (default if no recipients configured)
-
-## Weekly Summary Mode
-
-When triggered with "weekly summary" or "weekly digest":
-
-1. Aggregate across the full week (Mon-Fri)
-2. Add a "Week Highlights" section at the top
-3. Add trend comparison: "vs last week: +3 commits, +2 PRs, -1 blocker"
-4. Include sprint velocity trend chart (text-based)
-
-## Output Format
-
-- Use the structured template shown in Phase 2
-- Numbers first, details second
-- Emoji prefixes for quick scanning
-- Keep total report under 100 lines — summarize, don't enumerate every commit
-
-## Anti-Patterns
-
-- Do NOT send email without showing preview first
-- Do NOT include sensitive data (secrets, tokens, passwords found in code)
-- Do NOT fabricate activity — if nothing happened, say "quiet day"
-- Do NOT include full commit messages — summarize by category
-- Do NOT send to recipients not configured via catalyst_notify_configure
-
-## Chains To
-
-- `knowledge-base` — the digest itself can be stored as a daily record
+# Daily Digest
+
+> **Pillar**: Orchestrate | **ID**: `daily-digest`
+
+## Purpose
+
+Generate a comprehensive daily/weekly work summary by aggregating git activity, board changes, PR status, workflow completions, and knowledge entries — then deliver it via SMTP email or display in chat. Replaces manual status reporting entirely.
+
+## Activation Triggers
+
+- digest, daily report, daily summary, end of day, eod report, what did I do today, status report, send update, update PM, weekly summary, send email, standup report
+
+## Tools Required
+
+- `catalyst_git_log` — get commits for the time period
+- `catalyst_board_my_items` — get board items (opened, closed, in-progress)
+- `catalyst_worker_dashboard` — workflow completions and stats
+- `catalyst_knowledge_timeline` — decisions made in the period
+- `catalyst_exec` — run git/gh commands for additional data
+- `catalyst_notify_send` — deliver the report via email
+- `mcp_workiq_accept_eula` — (optional) accept Work IQ EULA before first query
+- `mcp_workiq_ask_work_iq` — (optional, requires Work IQ extension) fetch M365 activity (emails, meetings, docs, Teams) for a full work-surface report
+- `catalyst_artifact_write` — persist the digest as an artifact
+
+## Methodology
+
+### Process Flow
+
+```dot
+digraph daily_digest {
+    rankdir=LR;
+    node [shape=box];
+
+    collect [label="Phase 1\nData Collection\n(git, board, PRs,\nworkflows, knowledge)"];
+    generate [label="Phase 2\nReport Generation"];
+    deliver [label="Phase 3\nDelivery\n(email or chat)", shape=doublecircle];
+
+    collect -> generate;
+    generate -> deliver;
+}
+```
+
+### Phase 1 — Data Collection
+
+Gather from all sources for the requested time period (default: today):
+
+**Git Activity:**
+1. Call `catalyst_git_log` with `--since="today 00:00"` (or requested range)
+2. Extract: commit count, files changed, insertions/deletions, branches touched
+3. Group commits by scope/type (feat, fix, refactor, test, docs)
+
+**Board Activity:**
+1. Call `catalyst_exec` with `gh issue list --author=@me --state=all --json number,title,state,updatedAt,labels`
+2. Filter to items updated in the time period
+3. Categorize: created, moved to in-progress, closed/done, commented on
+
+**PR Activity:**
+1. Call `catalyst_exec` with `gh pr list --author=@me --state=all --json number,title,state,createdAt,mergedAt,reviewDecision`
+2. Filter to time period
+3. Categorize: opened, merged, review pending, changes requested
+
+**Workflow Activity:**
+1. Call `catalyst_worker_dashboard` for digital worker stats
+2. Filter completed/failed workflows in the period
+
+**Knowledge:**
+1. Call `catalyst_knowledge_timeline` for decisions and lessons stored today
+
+**M365 Activity (optional — requires Work IQ MCP server):**
+1. Call `mcp_workiq_accept_eula` with `eulaUrl: "https://github.com/microsoft/work-iq-mcp"` (idempotent — safe to call every time)
+2. Use **multiple focused queries** for comprehensive coverage (targeted queries return better results than one broad question):
+   - **Emails**: `mcp_workiq_ask_work_iq` → "What emails did I send and receive on {date}? Summarize key threads and any action items."
+   - **Meetings**: `mcp_workiq_ask_work_iq` → "What meetings did I attend on {date}? What decisions were made and what action items were assigned to me?"
+   - **Documents**: `mcp_workiq_ask_work_iq` → "What documents did I edit or view in SharePoint and OneDrive on {date}?"
+   - **Teams**: `mcp_workiq_ask_work_iq` → "What Teams channel messages and chats was I active in on {date}? What mentions did I receive?"
+   - **Tasks**: `mcp_workiq_ask_work_iq` → "What Planner or To-Do tasks did I complete or get assigned on {date}?"
+3. If Work IQ is available, parse all responses and include the full work surface:
+   - **Emails**: sent/received count, key threads, action items from emails
+   - **Meetings**: attended meetings, decisions made, action items assigned, linked documents
+   - **Documents**: files edited/viewed in SharePoint/OneDrive, co-authoring activity
+   - **Teams**: active channel conversations, 1:1 chats, mentions, and responses
+   - **Tasks**: Planner/To-Do items completed, created, or updated
+4. If `mcp_workiq_ask_work_iq` is unavailable or errors, skip this section — the digest works without it (git + board + PRs is the baseline)
+
+> **Query budget**: Work IQ queries have a ~30/session budget. The 5 queries above are a reasonable investment for a full daily digest. For weekly summaries, combine into broader date-range queries to conserve budget.
+
+### Phase 2 — Report Generation
+
+Compose the report in this structure:
+
+```
+📊 Daily Digest — {date} — @{username}
+═══════════════════════════════════════
+
+📝 COMMITS ({count})
+  feat:     {count} — {summary of features}
+  fix:      {count} — {summary of fixes}
+  refactor: {count}
+  test:     {count}
+  other:    {count}
+  
+  Files changed: {N} | +{insertions} / -{deletions}
+
+📋 BOARD ACTIVITY
+  Created:     {N} items ({titles})
+  In Progress: {N} items ({titles})
+  Completed:   {N} items ({titles})
+  Blocked:     {N} items ({titles + reason})
+
+🔀 PULL REQUESTS
+  Opened:   {N} — {PR titles with numbers}
+  Merged:   {N} — {PR titles}
+  Pending:  {N} — {waiting on review / changes requested}
+
+🤖 DIGITAL WORKER
+  Workflows completed: {N}
+  Workflows in progress: {N}
+  Workflows failed: {N}
+
+💡 DECISIONS MADE
+  - {decision 1}
+  - {decision 2}
+
+───────────────────────────────────────
+Tomorrow's focus:
+  - {open items in-progress}
+  - {PRs waiting for review}
+  - {blockers to resolve}
+```
+
+### Phase 3 — Delivery
+
+Based on notification configuration:
+
+**Email (default when recipients configured):**
+1. Call `catalyst_notify_send` with subject: "Daily Digest — {date} — {project name}", body: full report
+2. Email sent automatically via SMTP (no manual interaction needed)
+3. Requires SMTP env vars or `catalyst_notify_configure` to be set up
+
+**Console (fallback when no recipients configured):**
+1. Just display the report in chat
+2. User can copy-paste to email manually
+
+### Phase 4 — Preview & Send
+
+**ALWAYS preview before sending:**
+
+```
+📊 Digest Preview:
+
+{full report}
+
+──────────────
+Send to: {recipient} via email?
+(yes / edit / just show)
+```
+
+- **yes** → send via email (opens mail client with pre-filled content)
+- **edit** → user modifies, re-preview
+- **just show** → output only, don't send (default if no recipients configured)
+
+## Weekly Summary Mode
+
+When triggered with "weekly summary" or "weekly digest":
+
+1. Aggregate across the full week (Mon-Fri)
+2. Add a "Week Highlights" section at the top
+3. Add trend comparison: "vs last week: +3 commits, +2 PRs, -1 blocker"
+4. Include sprint velocity trend chart (text-based)
+
+## Output Format
+
+- Use the structured template shown in Phase 2
+- Numbers first, details second
+- Emoji prefixes for quick scanning
+- Keep total report under 100 lines — summarize, don't enumerate every commit
+
+## Anti-Patterns
+
+- Do NOT send email without showing preview first
+- Do NOT include sensitive data (secrets, tokens, passwords found in code)
+- Do NOT fabricate activity — if nothing happened, say "quiet day"
+- Do NOT include full commit messages — summarize by category
+- Do NOT send to recipients not configured via catalyst_notify_configure
+
+## Chains To
+
+- `knowledge-base` — the digest itself can be stored as a daily record

package/prompts/skills/deliver-change-management/SKILL.md

@@ -1,132 +1,132 @@
-# Change Management
-
-> **Pillar**: Deliver | **ID**: `deliver-change-management`
-
-## Purpose
-
-Structured commit and release workflow. Enforces conventional commits, generates changelogs, manages semantic versioning, and ensures every change is traceable.
-
-## Activation Triggers
-
-- "commit this", "write a commit message", "what should the commit be"
-- "changelog", "release notes", "version bump"
-- Automatically chained after any skill that modifies code
-
-## Methodology
-
-### Process Flow
-
-```dot
-digraph change_management {
-    rankdir=TB;
-    node [shape=box];
-
-    analyze [label="Phase 1\nChange Analysis"];
-    message [label="Phase 2\nCommit Message Generation"];
-    group [label="Phase 3\nCommit Grouping", shape=diamond];
-    release [label="Phase 4\nRelease Notes", style=dashed];
-    done [label="Committed", shape=doublecircle];
-
-    analyze -> message;
-    message -> group;
-    group -> message [label="split into\nseparate commits"];
-    group -> done [label="single commit"];
-    done -> release [label="release requested"];
-}
-```
-
-### Phase 1 — Change Analysis
-1. Run `git status` and `git diff --staged` to understand what's changed
-2. If nothing is staged, analyze the working tree diff
-3. Categorize changes:
-   - **feat**: New functionality
-   - **fix**: Bug fix
-   - **refactor**: Code restructuring (no behavior change)
-   - **test**: Adding/modifying tests
-   - **docs**: Documentation only
-   - **perf**: Performance improvement
-   - **chore**: Build, CI, dependencies
-   - **security**: Security fix
-
-### Phase 2 — Commit Message Generation
-Follow the conventional commit format configured in `commit_format`:
-
-```
-{type}({scope}): {description}
-
-{body — what and why, not how}
-
-{footer — breaking changes, issue references}
-```
-
-Rules:
-- Subject line ≤ 72 characters
-- Scope is the affected module/component (inferred from file paths)
-- Body explains motivation if the change isn't obvious
-- `BREAKING CHANGE:` footer for breaking changes
-- Reference issues: `Closes #123`, `Fixes #456`
-
-### Phase 3 — Commit Grouping
-If multiple logical changes are staged:
-1. Suggest splitting into separate commits
-2. Provide the staging commands (`git add -p` guidance)
-3. Generate a commit message for each logical unit
-
-### Phase 4 — Release Notes (when requested)
-1. Parse commits since last tag
-2. Group by type (Features, Fixes, Breaking Changes, etc.)
-3. Generate human-readable release notes
-4. Suggest version bump based on commit types:
-   - `BREAKING CHANGE` → major
-   - `feat` → minor
-   - `fix`, `perf` → patch
-
-## Tools Required
-
-- `terminal` — Run git commands
-- `catalyst_git_status` — Get current state
-- `catalyst_git_diff` — Get detailed diff
-- `catalyst_git_log` — Parse commit history
-- `catalyst_git_stage` — Stage files
-- `catalyst_git_commit` — Execute commit
-
-## Output Format
-
-```
-## [Catalyst → Change Management]
-
-### Changes Detected
-| Type | Scope | Files |
-|---|---|---|
-| {type} | {scope} | {file list} |
-
-### Suggested Commit
-\`\`\`
-{type}({scope}): {description}
-
-{body}
-
-{footer}
-\`\`\`
-
-### Release Notes (if requested)
-## v{X.Y.Z}
-### Features
-- {description} ({hash})
-### Fixes
-- {description} ({hash})
-### Breaking Changes
-- {description} ({hash})
-```
-
-## Chains To
-
-- `doc-governance` — Check if changed code needs doc updates
-- `deploy-guard` — Pre-deployment safety after committing
-
-## Anti-Patterns
-
-- Do NOT write generic commit messages ("update code", "fix things")
-- Do NOT combine unrelated changes in one commit
-- Do NOT skip the body for non-obvious changes
-- Do NOT version bump without analyzing the commit history
+# Change Management
+
+> **Pillar**: Deliver | **ID**: `deliver-change-management`
+
+## Purpose
+
+Structured commit and release workflow. Enforces conventional commits, generates changelogs, manages semantic versioning, and ensures every change is traceable.
+
+## Activation Triggers
+
+- "commit this", "write a commit message", "what should the commit be"
+- "changelog", "release notes", "version bump"
+- Automatically chained after any skill that modifies code
+
+## Methodology
+
+### Process Flow
+
+```dot
+digraph change_management {
+    rankdir=TB;
+    node [shape=box];
+
+    analyze [label="Phase 1\nChange Analysis"];
+    message [label="Phase 2\nCommit Message Generation"];
+    group [label="Phase 3\nCommit Grouping", shape=diamond];
+    release [label="Phase 4\nRelease Notes", style=dashed];
+    done [label="Committed", shape=doublecircle];
+
+    analyze -> message;
+    message -> group;
+    group -> message [label="split into\nseparate commits"];
+    group -> done [label="single commit"];
+    done -> release [label="release requested"];
+}
+```
+
+### Phase 1 — Change Analysis
+1. Run `git status` and `git diff --staged` to understand what's changed
+2. If nothing is staged, analyze the working tree diff
+3. Categorize changes:
+   - **feat**: New functionality
+   - **fix**: Bug fix
+   - **refactor**: Code restructuring (no behavior change)
+   - **test**: Adding/modifying tests
+   - **docs**: Documentation only
+   - **perf**: Performance improvement
+   - **chore**: Build, CI, dependencies
+   - **security**: Security fix
+
+### Phase 2 — Commit Message Generation
+Follow the conventional commit format configured in `commit_format`:
+
+```
+{type}({scope}): {description}
+
+{body — what and why, not how}
+
+{footer — breaking changes, issue references}
+```
+
+Rules:
+- Subject line ≤ 72 characters
+- Scope is the affected module/component (inferred from file paths)
+- Body explains motivation if the change isn't obvious
+- `BREAKING CHANGE:` footer for breaking changes
+- Reference issues: `Closes #123`, `Fixes #456`
+
+### Phase 3 — Commit Grouping
+If multiple logical changes are staged:
+1. Suggest splitting into separate commits
+2. Provide the staging commands (`git add -p` guidance)
+3. Generate a commit message for each logical unit
+
+### Phase 4 — Release Notes (when requested)
+1. Parse commits since last tag
+2. Group by type (Features, Fixes, Breaking Changes, etc.)
+3. Generate human-readable release notes
+4. Suggest version bump based on commit types:
+   - `BREAKING CHANGE` → major
+   - `feat` → minor
+   - `fix`, `perf` → patch
+
+## Tools Required
+
+- `terminal` — Run git commands
+- `catalyst_git_status` — Get current state
+- `catalyst_git_diff` — Get detailed diff
+- `catalyst_git_log` — Parse commit history
+- `catalyst_git_stage` — Stage files
+- `catalyst_git_commit` — Execute commit
+
+## Output Format
+
+```
+## [Catalyst → Change Management]
+
+### Changes Detected
+| Type | Scope | Files |
+|---|---|---|
+| {type} | {scope} | {file list} |
+
+### Suggested Commit
+\`\`\`
+{type}({scope}): {description}
+
+{body}
+
+{footer}
+\`\`\`
+
+### Release Notes (if requested)
+## v{X.Y.Z}
+### Features
+- {description} ({hash})
+### Fixes
+- {description} ({hash})
+### Breaking Changes
+- {description} ({hash})
+```
+
+## Chains To
+
+- `doc-governance` — Check if changed code needs doc updates
+- `deploy-guard` — Pre-deployment safety after committing
+
+## Anti-Patterns
+
+- Do NOT write generic commit messages ("update code", "fix things")
+- Do NOT combine unrelated changes in one commit
+- Do NOT skip the body for non-obvious changes
+- Do NOT version bump without analyzing the commit history