Individual skill
ccf-pipeline-orchestrator
Plan or coordinate CCF research stages, goals, gates, artifacts, and ccfa.yaml state. Use for 任务拆解, 流程规划, project status, end-to-end coordination, and explicitly requested autonomous research, autoresearch, or 自主科研迭代. Coordinate hypotheses, engineering, experiments, and feedback within the task budget; research engineer owns code and training.
ccf-pipeline-orchestrator/SKILL.md
Source commit 91ca9e2801698466f934b557a75ce46db8ba46b5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,490
- Repository last updated
- Oct 31, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
- finance Derived category
- research Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,774 bytesSKILL.mdcore · 7,774 bytesagents/openai.yamlasset · 776 bytesreferences/autonomous-research.mddoc · 38,349 bytesreferences/workflow-planning/approach-options.mddoc · 2,816 bytesreferences/workflow-planning/design-brief-template.mddoc · 2,004 bytesreferences/workflow-planning/intake-protocol.mddoc · 2,313 bytesscripts/campaign_budget.pyruns · 16,320 bytesscripts/research_loop.pyruns · 77,005 bytesscripts/test_research_loop.pyruns · 72,519 bytes
Read excerpt
# CCF Pipeline Orchestrator
## Family File Contract
Before file work, reuse canonical paths and one task/artifact working directory; default to project-root `ccfa-workfiles/<purpose>/<artifact-id>/`. Update in place, preserve inputs, and use UTF-8 with Chinese-text checks. Apply [artifact-contracts.md](../ccf-common/references/artifact-contracts.md) for naming, ownership, and task-created cleanup; handoffs inherit these paths.
## Collaboration Contract
Before specialist execution, read and apply [ccf-humanization](../ccf-humanization/SKILL.md) first, then [ccf-common](../ccf-common/SKILL.md). At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Integrate necessary specialist contributions under one owner; reuse valid prerequisites and verify affected results. Follow the [cooperation routes](../ccf-common/references/routing.md) without duplicate reports.
## Core Rule