Section Plan Draft Critique Pipeline

Optional inputs:

• terminology_registry (optional): Canonical terms, symbols, and disallowed variants for consistency control.
• current_draft_context (optional): Existing local draft text or outline to revise, compress, or audit.
• venue_constraints (optional): Page limit, formatting rules, length pressure, or author preference on tone.
• submission_state (optional): Current version status, remaining time, unresolved blockers, and target delivery scope.

Output Contract

• Output format: section draft
• Required sections: pipeline_plan, execution_order, risk_flags, handoff_notes
• Tone and language: reviewer-friendly / English
• Length guidance: Produce one section-sized draft block unless the user explicitly asks for longer.

Workflow

1. Treat the provided inputs as the only source of truth.
2. Produce only the bounded artifact for this skill, not a whole-paper rewrite.
3. Preserve contribution names, terminology, and claim boundaries from the shared inputs.
4. Make gaps explicit instead of guessing, especially when evidence is incomplete.
5. Before finalizing, run the section checks and self-checklist below.
6. If you need the full original schema or prompt template, read references/spec.yaml.

Guardrails

Core hard rules:

• Do not invent experiments, results, contributions, baselines, theoretical conclusions, or citations.
• Maintain factual faithfulness, claim-evidence alignment, terminology consistency, overclaim suppression, and reviewer-friendly clarity.
• If evidence is missing, weak, or indirect, say so explicitly and reduce claim strength rather than filling gaps.
• Prefer bounded, reviewer-safe wording over broad or triumphalist phrasing.

Section-specific checks:

• Output stays within the scope of Pipeline Orchestration and does not leak unsupported content from other sections.
• Contribution names, task setting, and method references match the global blueprint.
• Claims are phrased at the strength justified by the supplied evidence.
• Pipeline outputs should distinguish ordering advice from true scientific dependencies.
• Submission-stage decisions must preserve the paper's core evidence chain and not only optimize surface polish.

Revision policy:

• Missing required input: Return a gap-marked scaffold and list exactly which missing inputs block a stronger output.
• Unsupported claim: Downgrade or remove the claim, explain the evidence gap, and never patch the gap with invented detail.
• Multiple valid options: Provide 2-3 bounded options with tradeoffs, but keep all options faithful to the same verified facts.

Coordination

Reasoning focus:

• logical coherence.
• evidence grounding.
• novelty positioning.
• wording restraint.
• editing efficiency.

Self-checklist:

• Every main statement is supported by provided facts or explicitly labeled as a gap.
• No wording overstates novelty, empirical coverage, causality, or theory scope.
• Terminology, symbols, and contribution labels match the shared registry and blueprint.
• The output does not conflict with neighboring sections such as abstract, method, experiments, or conclusion.
• Pipeline recommendations distinguish must-have scientific fixes from optional presentation improvements.

Upstream skills:

• 00_01_paper_blueprint_skill
• 00_03_contribution_extractor_skill
• 00_04_claim_evidence_alignment_skill
• 00_06_terminology_notation_registry_skill
• 00_10_paper_readiness_check_skill
• 05_11_method_draft_skill
• 07_14_experiment_draft_skill
• 10_06_conclusion_draft_skill

Downstream handoff:

• 14_02_full_paper_assembly_skill