Human Approval Skill

No code execution without explicit human approval.

When Required

Executor MUST wait for approval before implementation when:

• Task comes from webhook (Jira, Sentry, GitHub)
• Task is classified as COMPLEX
• PLAN.md modifies critical paths (auth, payments, data)

Approval Flow

Planning creates PLAN.md
       ↓
Draft PR created (github-operations skill)
       ↓
Slack notification sent (slack-operations skill)
       ↓
WAIT for approval signal:
  - GitHub PR comment: "@agent approve" or "LGTM"
  - Slack button click
  - Jira status transition
       ↓
On approval → Executor proceeds
On rejection → Brain re-delegates to planning

Creating Approval Request

1. Create Draft PR

Use github-operations skill:

.claude/skills/github-operations/scripts/create_draft_pr.sh

PR body must include:

• Summary of PLAN.md
• List of files to be modified
• Risk assessment
• Estimated changes

2. Send Slack Notification

Use slack-operations skill:

.claude/skills/slack-operations/scripts/notify_approval_needed.sh

Message includes:

• Ticket/issue reference
• Link to Draft PR
• Approve/Reject buttons

3. Update Jira (if applicable)

Post comment with:

• Link to Draft PR
• Summary of planned changes
• Request for approval

Approval Signals

Check Approval Status

Before executor starts, verify:

# Check if approval exists
gh pr view $PR_NUMBER --json comments,reviews | \
  jq '.reviews[].state == "APPROVED" or
      (.comments[].body | contains("@agent approve") or contains("LGTM"))'

Blocking Executor

If no approval found:

BLOCKED: Awaiting human approval

Draft PR: https://github.com/org/repo/pull/123
Slack notification sent to: #channel

To approve:
  - Comment "@agent approve" on PR
  - Click Approve button in Slack
  - Transition Jira to "Approved"

Timeout Handling

Safety

• Never bypass approval for webhook tasks
• Log all approval/rejection events
• Preserve audit trail in PR comments