OpenParable
Skip to content
← Back to skills

Ccf Pipeline Orchestrator

Productivity
ccf-pipeline-orchestrator

Ccf Pipeline Orchestrator is an Agent Skill for productivity published in the mikubaka88/CCFA-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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, project status, stage gates, next-skill routing, 任务拆解, 流程规划. Do not perform downstream writing, review, search, experiment design, or rebuttal itself.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/mikubaka88/CCFA-Skills/blob/HEAD/ccf-pipeline-orchestrator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/ccf-pipeline-orchestrator, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.

Workflow

  1. Identify target venue, current stage, available artifacts, constraints, deadline pressure, and the user's immediate goal.
  2. Read ccfa.yaml when available; if absent, continue with supplied artifacts and report that project-state tracking is unavailable.
  3. For unclear projects, use references/workflow-planning/intake-protocol.md, approach-options.md, and design-brief-template.md.
  4. 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.
  5. Define the gate: required input, output artifact, pass condition, blocker, and handoff.
  6. 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: