CCF Pipeline Orchestrator

Family File Contract

Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root

ccfa-workfiles///

, with

source/

,

assets/

,

cache/

, and

build/

only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply

artifact-contracts.md

and reuse the same paths across skill transitions.

Collaboration Contract

Before specialist execution, read and apply

ccf-humanization

first, then

ccf-common

. 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.

Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional

cooperation routes

; avoid unrelated stages and duplicate reports.

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. Ensure Humanization and Common are active before planning and every contributing skill. Reuse their applicable rules at handoffs. Apply Humanization's detailed prose modes within authorized writing stages; raw planning and rendering still receive its baseline without a manuscript-edit workflow. 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. Show more Installs 1.1K Repository mikubaka88/ccfa-skills GitHub Stars 2.7K First Seen Jun 10, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass