cli-forge

Classify requests and route workflows to downstream cli-forge stages.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-forge
Source: https://github.com/ByteLandTechnology/cli-forge/tree/main/cli-forge
Command: npx skills add https://github.com/ByteLandTechnology/cli-forge --skill cli-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classify requests and route workflows within cli-forge to the appropriate downstream stage, ensuring the earliest incomplete phase is addressed and missing contract baselines are recovered.

Core Features & Use Cases

  • Classify requests into Design, Takeover, Plan, Scaffold, Extend, Validate, or Publish.
  • Inspect repository state to detect missing contracts and determine the correct routing path.
  • Generate the handoff contract at .cli-forge/handoff.yml and hand off to the appropriate downstream skill.
  • Resume interrupted workflows by rehydrating inputs from the repository state.

Quick Start

Provide a user request and target project path; the router will generate a handoff.yml and route you to the next required skill.

Frequently Asked Questions about cli-forge

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

FAQPage Schema
How do I route a Rust project to the correct workflow stage?

Routing involves classifying requests and inspecting the repository state to detect missing contracts, identifying the earliest incomplete phase like Design or Validate to ensure safe workflow takeover.

What is a handoff contract in CLI workflow routing?

A handoff contract is a generated file at .cli-forge/handoff.yml that captures the current repository state and routes the workflow to the appropriate downstream skill stage for safe recovery.

How do I resume an interrupted Rust project workflow?

Resume interrupted workflows by rehydrating inputs from the repository state, detecting missing baselines, and regenerating the handoff.yml to safely route to the next required downstream stage.

Does this workflow router work with any Rust project structure?

It applies specifically to Rust projects managed with cli-forge, requiring filesystem checks to detect missing contract baselines and determine the correct routing path for stages like Scaffold or Publish.

Why is my workflow not advancing to the next development stage?

Workflows stall when missing contract baselines are detected; the router inspects repository state, identifies the earliest incomplete phase, and generates a handoff contract to recover and continue.

What's the best way to classify development requests into stages like Scaffold or Extend?

Classify requests by inspecting the repository state to determine the correct routing path, generating a handoff.yml to safely hand off to Design, Takeover, Plan, Scaffold, Extend, Validate, or Publish stages.