forge:chat

Route user intents to FORGE pipeline stages with gate approvals.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Chulf58/FORGE --skill forge-chat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge:chat
Source: https://github.com/Chulf58/FORGE/tree/main/skills/chat
Command: npx skills add https://github.com/Chulf58/FORGE --skill forge-chat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FORGE conversation orchestration solves the challenge of guiding user intent through complex multi-agent pipelines, making planning, reviewing, implementing, and applying steps transparent and controllable in real time.

Core Features & Use Cases

  • Routes user intents to the correct FORGE pipeline stage (plan, implement, apply) with supervisor oversight and automated gates.
  • Maintains a live, glass-wall style workflow where planners, researchers, reviewers, coders, and documenters can observe progress and interleave as needed.
  • Supports supervised and autonomous modes to fit active user involvement and background automation.

Quick Start

Initiate routing of a user request to the correct FORGE pipeline stage and await gate approvals.

Frequently Asked Questions about forge:chat

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

FAQPage Schema
How do I orchestrate multi-agent conversations across planning and review pipelines?

Multi-agent conversation orchestration routes user intents to correct pipeline stages with supervisor oversight and automated gates. It coordinates planning, reviewing, implementing, and applying steps transparently in real time across supervised or autonomous execution modes.

How do I route user intents to the correct pipeline stage automatically?

Route user intents to the correct pipeline stage by utilizing intent detection to direct requests to plan, implement, or apply phases. The workflow applies gate-based approvals to ensure supervised oversight before progressing through the pipeline.

Can I run conversation routing workflows in both supervised and autonomous modes?

Conversation routing workflows support both supervised and autonomous modes to fit active user involvement and background automation. Supervised mode requires gate-based approvals, while autonomous mode enables background pipeline execution.

What is the best way to manage gate-based approvals in a multi-agent pipeline?

Managing gate-based approvals in a multi-agent pipeline requires clear role-aware prompts and supervisor oversight to validate stage transitions. This approach maintains a glass-wall style workflow where agents observe progress and interleave as needed.

When should I not use autonomous conversation orchestration for pipeline execution?

You should avoid autonomous conversation orchestration when explicit user involvement is required for critical planning or reviewing decisions. Complex multi-agent pipelines needing manual gate approvals are better suited for supervised execution modes.