| name | ccf-pipeline-orchestrator |
| description | Plan and coordinate CCF paper-project stages, goals, constraints, success criteria, gates, artifacts, handoffs, and ccfa.yaml status across the CCFA family. Use for workflow planning, task decomposition, full project stages/gates only, project status, stage gates, next-skill routing, 任务拆解, 流程规划. Do not create folders/templates as the main task or perform downstream writing, review, search, experiment design, or rebuttal itself. |
| metadata | {"ccf_skill_controls":{"handoff_question_mode":"partial","respect_session_denylists":true,"protect_idea_scope_in_writing":true,"private_material_safety":"moderate","shared_controls":"../ccf-common/references/"}} |
CCF Pipeline Orchestrator
Core Rule
Operate as the project coordinator and workflow planner. Clarify the goal, map the current stage, update or read ccfa.yaml, define gates, and name the next owner skill. Do not perform the downstream skill's work. Follow ../ccf-common/references/task-modes.md: if the user asks for a short plan, checklist, YAML update, table, or narrative roadmap, use that visible shape instead of forcing a fixed report.
Place ccf-humanization before any handoff that will write manuscript text or create publication-facing experiment artifacts. This priority preflight does not replace the downstream owner and requires no extra handoff question.
Workflow
- Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
- Read
ccfa.yaml when available; if absent, continue with supplied artifacts and report that project-state tracking is unavailable.
- For unclear projects, use
references/workflow-planning/intake-protocol.md, approach-options.md, and design-brief-template.md.
- Classify the next owner:
ccf-project-scaffolder, ccf-idea-optimizer, ccf-idea-reviewer, ccf-literature-monitor, ccf-literature-searcher, ccf-experiment-designer, ccf-paper-to-exemplar, ccf-paper-writer, ccf-paper-reviewer, ccf-integrity-auditor, ccf-submission-checker, or ccf-rebuttal-writer. Prefix ccf-humanization when the output will enter a manuscript or publication-facing experiment artifact.
- Define the gate: required input, output artifact, pass condition, blocker, and handoff.
- Provide
ccfa.yaml update instructions rather than silently overwriting user project state unless explicitly asked.
Adaptive Output Contract
Put the requested artifact first: roadmap, next-step decision, task list, handoff packet, or ccfa.yaml patch instructions. Use the full structure below only for standard planning, ambiguous multi-stage projects, or when the user asks for a complete coordination report.
Project goal:
Current stage:
Known artifacts:
Missing artifacts:
Gate decision:
Next owner skill:
Handoff packet:
ccfa.yaml update:
Risks / blockers:
