icaire-white-paper-coordinate-approval
Coordinate ICAIRE white-paper leadership approval. Use when preparing approval packs, decision notes, review questions, stakeholder routing, follow-up requests, or approval-status summaries for a prop
SKILL.mdskills/icaire-white-paper-coordinate-approval/SKILL.md
GitHubICAIRE White Paper: Coordinate Approval
Prepare the human approval step for an ICAIRE white paper so leadership can make a clear decision before drafting continues.
Contract
- Keep scope to ICAIRE white papers. Scientific papers and academic publication approval workflows are out of scope until separately defined.
- Treat approval as human-owned. The skill prepares the package, questions, options, and follow-up record; it does not approve on leadership's behalf.
- Use BigBrain or the ICAIRE MCP connector for current stakeholders, prior decisions, meeting context, relevant initiatives, and known sensitivities.
- Keep criteria, approval template, required approvers, citation standards, Arabic review requirements, grammar checks, and design standards as explicit placeholders when not supplied.
- Separate confirmed facts, proposed positioning, missing inputs, and decision requests.
Workflow
- Identify the approval moment.
- Record the proposal, requester, expected approvers, deadline, meeting or review channel, and decision required.
- Gather context.
- Read the proposal, source material, relevant meeting notes, initiative pages, and stakeholder context.
- Retrieve ICAIRE context when approver roles, sensitivities, or prior decisions are unclear.
- Build the approval package.
- Summarize the proposed white paper, rationale, scope, out-of-scope items, audience, expected output, resource needs, risks, and unresolved questions.
- Include placeholders for Israa's criteria, template checks, citation style, Arabic support, grammar review, and design standards.
- Prepare decision options.
- Offer practical options such as approve, approve with conditions, revise and resubmit, defer, or reject.
- State the implication of each option and what follow-up work it triggers.
- Capture next actions.
- Draft follow-up notes, owner assignments, open questions, and timeline entries for the brain when the user asks for persistence.
Output
Default to:
Approval SummaryDecision NeededRecommended OptionDecision OptionsApproval Criteria PlaceholderRisks And SensitivitiesOpen QuestionsFollow-Up ActionsStatus Note
Guardrails
- Do not mark a paper approved unless leadership approval is explicit in source material or the user states it.
- Do not invent approvers, authority, dates, conditions, or decision outcomes.
- Do not route scientific-paper publication decisions through this white-paper approval skill.
- Do not hide missing criteria; make them visible in the approval package.