{"id":76370,"plugin_id":"plugin_asdk_app_6ad3a430b30481919b3d089dabbc9b93","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-02T18:12:10.462Z","digest":"cdca09fb67a518e5e4d98d8321b815479238a1f242f0dd3b98393a0ead30be49","against":null,"payload":{"description":"Use when the user asks to run the OloLand ololand-dd-ic-approve-readiness workflow. Pre-flight check before IC package approval. Surfaces both blocker tiers (open critical assumptions AND unsupported high-priority assumptions) plus weak-evidence warnings that won't block but should be reviewed.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":447}],"name":"ololand-dd-ic-approve-readiness","skill_md_contents":"---\nname: ololand-dd-ic-approve-readiness\ndescription: Use when the user asks to run the OloLand ololand-dd-ic-approve-readiness\n  workflow. Pre-flight check before IC package approval. Surfaces both blocker tiers\n  (open critical assumptions AND unsupported high-priority assumptions) plus weak-evidence\n  warnings that won't block but should be reviewed.\n---\n\n\n# Workflow for ololand-dd-ic-approve-readiness\n\nFollow the OloLand command instructions below when the user asks for `ololand-dd-ic-approve-readiness` or the equivalent workflow.\n\n# IC Approve Readiness\n\nIC package approval is gated by two independent blocker tiers:\n\n1. **Open blocking assumptions** — high or critical tracked assumptions still in an unresolved state.\n2. **Unsupported high-priority assumptions** — high or critical tracked assumptions whose evidence_strength is `none` (no provenance attached at all).\n\nA separate **weak-evidence warning** surface flags high/critical assumptions whose evidence_strength is `weak` or `partial`. These do NOT block approval, but the IC viewer surfaces them so the analyst knows what to defend.\n\nThis command runs the pre-flight check before the analyst attempts to approve.\n\n## Usage\n\n```\nololand-dd-ic-approve-readiness <deal_id>\n```\n\n## Arguments\n\n- `deal_id` (required) — The deal whose IC package readiness to assess.\n\n## Execution\n\n1. Call `get_assumption_control_summary` with the `deal_id`.\n2. Call `get_assumption_evidence_pack` to retrieve `quality_flags` for the deal.\n3. Call `get_ic_package(deal_id)` to retrieve the latest IC package and its `approval_evidence_snapshot`. If the response has `package: null`, no IC package exists yet — note this and continue with just the assumption-level analysis.\n4. Categorize:\n   - **Tier-1 blockers** (resolution required): from `control_summary.blocking_assumptions` — high/critical, status not in {verified, mitigated, invalidated, accepted}.\n   - **Tier-2 blockers** (provenance required): from `quality_flags` — high/critical tracked assumptions with `evidence_strength == \"none\"`.\n   - **Warnings** (review recommended, not blocking): from `quality_flags` — high/critical tracked assumptions with `evidence_strength` in {weak, partial}. Cross-reference these against `approval_evidence_snapshot.warnings` if a package exists.\n5. Render:\n\n   - **Overall readiness**: READY / BLOCKED\n   - **Tier-1 blockers** (one row per blocker): `assumption_id`, `statement`, `status`, `priority`, recommended resolution\n   - **Tier-2 blockers** (unsupported high-priority): `assumption_id`, `statement`, `missing_links`, recommended source to attach\n   - **Warnings** (weak/partial evidence): `assumption_id`, `statement`, `evidence_strength`, why this is weak, what to add to strengthen it\n   - **Counts**: `total`, `open`, `blocking`, by `evidence_strength`\n   - **Package state** (if a package exists): `version`, `status`, `approved_at`, and `approval_evidence_snapshot.summary` — the snapshot that was captured at the last approval attempt or will be captured next.\n\n## Why two tiers\n\nThe first tier (open blocking assumptions) catches \"we still need to verify this.\" The second tier (unsupported high-priority) catches \"we marked this assumption critical but never attached an evidence link\" — a different failure mode where the workflow state is closed but the underlying provenance is empty. Both surface here so the analyst sees exactly what stands between the deal and an approved IC.\n\n## Example\n\n```\nololand-dd-ic-approve-readiness deal_acme_2026\n```\n\nReturns: \"BLOCKED. Tier-1 (2): 'FY27 22% growth requires geo expansion' (unverified, critical) — schedule commercial DD; 'WC normalization $4M' (unverified, high) — pull A/R aging. Tier-2 (1): 'Customer concentration <30% by closing' (status=unverified, evidence_strength=none) — no provenance attached; link the customer-revenue table or mark it accepted with a memo. Warnings (1): 'EBITDA margin sustainable at 22%' (status=verified, evidence_strength=partial) — only one quarter of margin data; consider strengthening with comparables or normalization analysis.\"\n\n## Related commands\n\n- `ololand-dd-assumption-controls` — interactive review and status transitions for assumption controls\n- `ololand-dd-dd-analyze` — populate bounded extraction, risk, and financial-snapshot inputs before IC synthesis; use a separate explicit reconciliation action when needed\n\n## Output URL Conventions (STRICT)\n\nDomain is `app.ololand.ai`. Surfaces:\n- IC package: `https://app.ololand.ai/deals/{deal_id}/ic-package`\n- Assumption controls: `https://app.ololand.ai/deals/{deal_id}/analysis/assumptions`\n\n\n## OpenAI execution requirements\n\nUse the connected MCP server's current tool schemas. Do not invent tool arguments, job-status endpoints, inputs, or outputs. If a referenced tool is unavailable, explain the limitation and request the needed connection or data. Invoke writes only when the user has requested the corresponding action. Do not initiate purchases or payments. An unrun, unsupported, or unavailable procedure is a gap, never a passing result.\n\n\nOpenAI cannot execute local lifecycle hooks. Use the packaged explicit setup/review workflow when requested. Server-side MCP auditing remains authoritative; preserve evidence blockers and human-only approval gates.\n\nClaim-correction submission is unsupported in this OpenAI upload because the current handler records surface=cowork. Do not invoke submit_agent_claim_correction from OpenAI. Explain the limitation and retain proposed correction text for human review without claiming submission. See unsupported-workflows.json for the excluded canonical workflow.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}