skills.rest
ByteLandTechnology
ByteLandTechnologyOFFICIAL
Explore all skills by this author →
WebsiteGitHub

cli-forge-plan

Define and lock a CLI contract for the cli-forge plan stage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and locking a CLI contract early prevents drift between requirements and implementation, giving teams a single source of truth for CLI behavior.

Core Features & Use Cases

  • Translates approved designs into a concrete, machine-checkable plan (commands, flags, formats, and help behavior)
  • Specifies runtime expectations, including daemon scope and Active Context interactions, to guide scaffold and extend stages
  • Serves as the planning contract for downstream validation and publishing steps, ensuring alignment across design, scaffold, and release

Quick Start

Review the design-contract.yml and planning-brief.md, then generate the .cli-forge/cli-plan.yml and present it for approval.

Frequently Asked Questions about cli-forge-plan

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

FAQPage Schema
How do I define a CLI contract to prevent drift between design and scaffold?▼

To define a CLI contract, translate approved designs into a machine-checkable plan specifying commands, flags, output formats, help behavior, and runtime directory behavior. This locks the CLI implementation details early, ensuring alignment across design, scaffold, and release stages.

What is a CLI plan file and when do I need it for command line application development?▼

A CLI plan file is a structured configuration that locks the precise command tree, flags, and runtime surfaces before implementation. You need it during design-to-scaffold workflows to serve as a single source of truth for CLI behavior and downstream validation.

How to generate a CLI plan from design requirements for scaffolding?▼

Generate a CLI plan by reviewing design-contract.yml and planning-brief.md inputs, then outputting a .cli-forge/cli-plan.yml file. This file specifies commands, daemon scope, approval workflows, and runtime directory behavior for the scaffold stage.

Does planning a CLI contract early help with downstream validation and publishing?▼

Planning a CLI contract early provides a concrete planning contract for downstream validation and publishing steps. It ensures the generated command tree, flags, and help behavior align across design, scaffold, and release to prevent implementation drift.

What should be specified in a CLI contract regarding runtime behavior and daemons?▼

A CLI contract should specify runtime expectations including daemon scope, Active Context interactions, and runtime directory behavior. These runtime surfaces guide the scaffold and extend stages during command line interface implementation.

Related Skills

Explore More Software Engineering Skills→
steadyfallsteadyfall

design-html

Convert approved mockups or planning inputs into production-ready HTML/CSS.

Community
Advanced
ByteLandTechnologyByteLandTechnology

cli-forge

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

Official
Advanced
michalvavramichalvavra
16

create-cli

Design CLI interfaces with arguments, flags, help text, and output modes.

Community
Advanced
metratonmetraton
3

agent-protocol

Enforce a standardized json:contract block with evidence and verification structures in agent responses.

Community
Advanced