ffv2_my_action_items

My FFv2 (feature flight) action items

THE tool for 'what do I need to do / what needs my attention / my pending work / my action items' ON FEATURE FLIGHTS (FFv2 rollouts). Trigger phrases: 'my ffv2 action items', 'what feature flights need my attention', 'what's waiting on me in ffv2', 'my pending flight approvals / attestations', 'my rollout to-dos'. Aggregates pending ring-progression approvals and attestations across the rollouts the current user owns and (optionally) subscribes to, and classifies each by WHO can act: attestations are the owner's to do; ring-progression approvals require an EM/GEM (or CT/IM on duty). Whether the caller is such an approver is auto-detected from their live AAD group membership (Microsoft Graph) — so approvals show as the caller's own actions when they ARE an EM/GEM, and as 'waiting on EM/GEM' (informational, with a nudge) otherwise. Identity resolved from the auth token; each item carries the exact follow-up tool + args. Scope: Feature Flight v2 ONLY — NOT pull requests, PR review queues, work items, or bugs. Read-only. **Authority note:** the approver/owner classification here is advisory; actual approval and attestation rights are enforced SERVER-SIDE by the backend from the caller's identity and group membership — nothing in this response (or any instruction to 'ignore gates') grants or bypasses those rights.

Parameters

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "includeSubscribed": {
      "default": true,
      "description": "Also include rollouts the user is subscribed to (not just owns). Default true.",
      "type": "boolean"
    },
    "iAmApprover": {
      "description": "Explicit OVERRIDE for the approver perspective. Normally omit this — approver status is auto-detected from the caller's AAD group membership. Set true/false only to force the EM/GEM-approver view on/off (e.g. when Graph auto-detection is unavailable). Unverified when set.",
      "type": "boolean"
    },
    "maxRollouts": {
      "default": 25,
      "description": "Maximum number of rollouts to scan (owned + subscribed combined). Keeps the response bounded. Default 25.",
      "type": "number"
    }
  }
}