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. Specialist skills own downstream outputs. For a plan-only request, return the plan. For explicitly requested end-to-end execution, coordinate the authorized owners through completion rather than stopping after naming the next skill. 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.
Follow ../ccf-common/references/handoff-modes.md and ../ccf-common/references/artifact-contracts.md. Later user corrections normally steer the active project: preserve valid completed work, update affected requirements, and continue. Do not invent completed stages or automatic background jobs.
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-visual-composer, 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.
- Resolve canonical input/output and working paths before each file-producing handoff. Reuse the current artifact and hand off changed requirements plus source locations, not duplicated full reports. Keep independent owners from writing the same file concurrently. Update existing
ccfa.yaml stage/gate fields when project-state maintenance is authorized; preserve unrelated fields and the existing contract. For a planning-only request, propose the update without writing. Reuse existing artifact/state fields for the current goal, evidence locations, completed work, and next step when continuation needs it.
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:
1---2name: ccf-pipeline-orchestrator3description: Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state. Use for 任务拆解, 流程规划, project status, and explicitly requested end-to-end coordination. Specialist skills own research outputs; ccf-project-scaffolder owns folder/template creation.4---5
6# CCF Pipeline Orchestrator
7
8## Core Rule
9
10Operate 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. Specialist skills own downstream outputs. For a plan-only request, return the plan. For explicitly requested end-to-end execution, coordinate the authorized owners through completion rather than stopping after naming the next skill. 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.
11
12Place `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.
13
14Follow `../ccf-common/references/handoff-modes.md` and `../ccf-common/references/artifact-contracts.md`. Later user corrections normally steer the active project: preserve valid completed work, update affected requirements, and continue. Do not invent completed stages or automatic background jobs.
15
16## Workflow
17
181. Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
192. Read `ccfa.yaml` when available; if absent, continue with supplied artifacts and report that project-state tracking is unavailable.
203. For unclear projects, use `references/workflow-planning/intake-protocol.md`, `approach-options.md`, and `design-brief-template.md`.
214. Classify the next owner: `ccf-project-scaffolder`, `ccf-idea-optimizer`, `ccf-idea-reviewer`, `ccf-literature-monitor`, `ccf-literature-searcher`, `ccf-experiment-designer`, `ccf-visual-composer`, `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.
225. Define the gate: required input, output artifact, pass condition, blocker, and handoff.
236. Resolve canonical input/output and working paths before each file-producing handoff. Reuse the current artifact and hand off changed requirements plus source locations, not duplicated full reports. Keep independent owners from writing the same file concurrently. Update existing `ccfa.yaml` stage/gate fields when project-state maintenance is authorized; preserve unrelated fields and the existing contract. For a planning-only request, propose the update without writing. Reuse existing artifact/state fields for the current goal, evidence locations, completed work, and next step when continuation needs it.
24
25## Adaptive Output Contract
26
27Put 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.
28
29```text
30Project goal:
31Current stage:
32Known artifacts:
33Missing artifacts:
34Gate decision:
35Next owner skill:
36Handoff packet:
37ccfa.yaml update:
38Risks / blockers:
39```
mikubaka88