integrate

Route compound outputs to project targets using GSE configuration files.

4|1|Updated Apr 11, 2026

Search Tags:#automation #routing #governance #ticketing #compound #integrate

Ready to run

npx skills add https://github.com/nicolasguelfi/gensem --skill integrate-nicolasguelfi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: integrate
Source: https://github.com/nicolasguelfi/gensem/tree/main/gse-one/plugin/skills/integrate
Command: npx skills add https://github.com/nicolasguelfi/gensem --skill integrate-nicolasguelfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route capitalized solutions from the latest compound to the intended project targets, ensuring consistent governance and traceability across the GSE workflow.

Core Features & Use Cases

Routing outcomes from a completed compound into project configuration, tickets, and learning artifacts.
Supports Axe 1 (Project Integration), Axe 2 (Methodology Integration), and Axe 3 (Competency Integration) with optional dry-run mode for safe evaluation.
Provides clear prompts and validation gates to prevent unintended submissions and to confirm actions before changes are applied.

Quick Start

Invoke the integration after a compound with the command that triggers the /gse:integrate route to dispatch results to the appropriate targets.

Frequently Asked Questions about integrate

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

FAQPage Schema

How do I route capitalized solutions to project targets in a governance workflow?▼

You route capitalized solutions by invoking the integration command after a compound run, which dispatches results to the appropriate project targets. The process reads compound outputs and routes them into project configuration, tickets, and learning artifacts.

What configuration files are required to route governance workflow outputs?▼

Routing governance outputs requires three configuration files: .gse/status.yaml, .gse/config.yaml, and .gse/profile.yaml. These project and profile configuration files must exist before the integration routing can execute.

Can I test routing capitalized solutions without applying changes to project targets?▼

Yes, you can test routing without applying changes using the dry-run option. This safe evaluation mode provides validation gates and clear prompts to confirm actions before any modifications are submitted to project targets.

What types of integration axes are supported for ticketing and documentation routing?▼

The routing supports three integration axes: Axe 1 for Project Integration, Axe 2 for Methodology Integration, and Axe 3 for Competency Integration. Each axis routes learnings, debts, and competency signals to their respective targets.

How does axis filtering work when routing compound outputs to project targets?▼

Axis filtering allows you to selectively route compound outputs by specifying which integration axes to process. This ensures only the selected learnings, debts, and competency signals are dispatched to their corresponding project targets.