cli-forge-takeover

Reconstruct design-contract.yml and cli-plan.yml for pre-existing Rust CLI projects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables adopting pre-existing Rust CLI projects into the cli-forge pipeline by reconstructing missing design and plan contracts and recording a takeover receipt, ensuring a transparent, auditable transition path.

Core Features & Use Cases

  • Reconstruct design-contract.yml and cli-plan.yml from observed implementation, docs, and tests.
  • Generate takeover receipt and record evidence sources to govern downstream stages.
  • Hand off to Validate, Publish, or Extend based on the recorded post-adoption objective.

Quick Start

Follow the takeover planning brief and the observed project surfaces to begin the reconstruction.

Frequently Asked Questions about cli-forge-takeover

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

FAQPage Schema
How do I adopt a pre-existing Rust CLI into a pipeline when missing design contracts?

Adopt a pre-existing Rust CLI by reconstructing missing design-contract.yml and cli-plan.yml files from observed implementation, docs, and tests. This generates a takeover receipt to record evidence sources, ensuring a transparent and auditable transition path into the pipeline.

What is a takeover receipt in Rust CLI pipeline adoption?

A takeover receipt is an artifact generated during CLI pipeline adoption that records evidence sources used to reconstruct missing design and plan contracts. It governs downstream stages by establishing a transparent, auditable baseline from the observed project implementation.

What files do I need to reconstruct design contracts for a Rust CLI?

Reconstructing design contracts requires a Rust CLI project containing Cargo.toml, README.md, src/, and tests. These surfaces provide the evidence needed to generate design-contract.yml, cli-plan.yml, and takeover receipts when approved contracts are missing.

Can I validate or publish a Rust CLI after reconstructing its contracts?

Yes, after reconstructing contracts and recording a takeover receipt, you can hand off the Rust CLI project to downstream stages. The recorded post-adoption objective enables Validate, Publish, or Extend actions based on the generated baseline artifacts.

When should I use contract reconstruction for a Rust CLI project?

Use contract reconstruction when a Rust CLI project has Cargo.toml, README.md, src/, and tests but lacks approved cli-forge contracts. It satisfies requirements for design and plan reconstruction, evidence recording, and baseline takeover artifacts.

How does evidence-based reconstruction work for missing CLI plan files?

Evidence-based reconstruction analyzes observed implementation, documentation, and tests from a Rust CLI project to reverse-engineer missing cli-plan.yml and design-contract.yml files. It creates baseline takeover artifacts required to enable downstream pipeline stages.