icaire-white-paper-review-content

Review ICAIRE white-paper content for grounding, completeness, legitimacy, evidence quality, scope, citations, grammar, Arabic-language needs, and readiness for formatting. Use when checking a draft b

SKILL.md

GitHub

ICAIRE White Paper: Review Content

Review an ICAIRE white-paper draft before it moves to expert review, approval, or design and formatting.

Contract

  • Keep scope to ICAIRE white papers. Scientific-paper review, academic peer review, journal compliance, and research-integrity review are out of scope unless separately requested under a scientific-paper workflow.
  • Use the proposal, approval notes, source set, and ICAIRE context as the review baseline.
  • Check whether the draft is grounded, complete, legitimate, coherent, and ready for the next phase.
  • Treat missing criteria, templates, citation rules, Arabic support, grammar checks, and design standards as explicit review gaps.
  • Separate blockers from minor edits and optional improvements.

Workflow

  1. Establish the review baseline.
    • Read the draft, proposal, approval notes, source material, and any supplied criteria or templates.
    • Retrieve ICAIRE context when internal claims, stakeholder language, or prior decisions need checking.
  2. Check scope and structure.
    • Confirm the draft matches the approved white-paper purpose, audience, outline, and out-of-scope boundaries.
    • Flag scientific-paper drift such as journal framing, unapproved academic claims, or formal hypothesis language.
  3. Check evidence and legitimacy.
    • Map major claims to sources.
    • Flag unsupported claims, weak sources, missing citations, overclaims, sensitive stakeholder language, and claims needing expert review.
  4. Check readability and language.
    • Review grammar, sentence clarity, terminology, abstract structure, translation or Arabic-language needs, and duplicated content.
  5. Check readiness for formatting.
    • Identify missing figures, diagrams, tables, image permissions, citation style decisions, template needs, and design-standard gaps.
  6. Produce a decision.
    • Mark the draft as ready for next phase, ready with minor edits, needs major revision, or blocked.

Output

Default to:

  • Review Decision
  • Major Blockers
  • Evidence And Citation Issues
  • Scope Issues
  • Structure And Argument Issues
  • Grammar And Language Issues
  • Arabic Support Needs
  • Design And Formatting Readiness
  • Recommended Edits
  • Questions For Israa Or Leadership

Guardrails

  • Do not rewrite the whole paper unless the user asks for a revision pass.
  • Do not approve unsupported claims because the prose sounds polished.
  • Do not invent missing source details, citation metadata, approval criteria, or design standards.
  • Do not apply scientific-paper review criteria to a white paper by default.