c-to-g

Convert cX.Y pipelines into gX.Y self-contained prompts for generic agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gapfDev/workflow --skill c-to-g
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: c-to-g
Source: https://github.com/gapfDev/workflow/tree/main/.claude/skills/c-to-g
Command: npx skills add https://github.com/gapfDev/workflow --skill c-to-g

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts cX.Y pipelines into gX.Y prompts for generic agents, enabling version-agnostic pipelines to be executed across different agent runtimes.

Core Features & Use Cases

  • Converts between pipeline representations (c to g) for multiple versions.
  • Discovers source pipelines from a given version and outputs ready-to-run prompts under the corresponding {VERSION}/prompts directory.
  • Supports discovery, mapping, and inline contracts/core protocol steps to ensure deterministic prompts.

Quick Start

Copy one of the generated g prompts and run it in a new agent session with a specified version.

Frequently Asked Questions about c-to-g

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a cX.Y pipeline into self-contained prompts for generic AI agents?▼

This framework converts cX.Y pipelines into gX.Y self-contained prompts for generic agents. It accepts a VERSION argument, reads the corresponding source, and outputs a complete prompts set ready for execution across different agent runtimes.

Does converting pipelines to generic agent prompts require managing external dependencies during execution?▼

No, converting pipelines to generic agent prompts requires no external dependencies during execution. The framework inlines shared rules and contracts directly, ensuring the generated gX.Y prompts are fully self-contained and deterministic for the target agent.

How do I run generated prompts after converting my automation pipeline?▼

To run generated prompts after converting your automation pipeline, copy one of the generated g prompts from the output directory. Execute it in a new agent session while specifying the target version to process the pipeline correctly.

What is the discovery-map-inline-contract framework used for in pipeline conversion?▼

The discovery-map-inline-contract framework is used to inline shared rules and contracts during pipeline conversion. It discovers source pipelines from a given version and maps them to ensure deterministic, self-contained gX.Y prompts for generic agents.

Can I use this pipeline conversion tool for version-agnostic automation workflows?▼

Yes, you can use this pipeline conversion tool for version-agnostic automation workflows. It converts cX.Y pipelines into gX.Y prompts, enabling version-agnostic pipelines to be executed across different agent runtimes without compatibility issues.