edda-workflowlisted

# Edda Workflow: Task Notification + Draft Approval After a coding agent completes work, use this skill to report results and handle pending draft approvals. **Context injection and session digests are handled automatically by the edda bridge plugin.** This skill only covers the notification and approval workflow. ## When to Use - A coding agent (Codex, Claude Code, Pi) finishes a task - User asks about pending drafts or approval status - User wants to approve or reject a draft ## 1. Post-Task Report After a coding agent completes, gather results and send a clear report. ### Gather info Run these commands in the project directory: ```bash # What changed git diff --stat HEAD~1 2>/dev/null || git diff --stat # Test results (if applicable) cargo test 2>&1 | tail -5 # Rust npm test 2>&1 | tail -10 # Node # Pending drafts edda draft inbox --json ``` ### Report format Send a single message with this structure: ``` Task completed: [brief description] Changes: - [file1]: [what changed] - [file2]: [what changed] (N files changed, +X insertions, -Y deletions) Tests: [passed/failed — one line summary] [If pending drafts exist:] Pending approval: - [draft_id]: [title] (stage: [stage_id], needs [N] approval(s)) Reply "approve [draft_id]" or "reject [draft_id]" to decide. ``` Keep it concise. The user is reading this on a phone. ### If task failed ``` Task failed: [brief description] Error: [error message — keep to 2-3 lines max] [If the error is actionable:]