cli-forge Design

Use this stage when the workflow needs one authoritative description contract for a generated Rust CLI Skill before later stages proceed.

Purpose

Define the skill's high-level identity: what it is, who it serves, and how it is positioned. Produce a single approved description contract that all downstream surfaces must reuse instead of inventing competing wording.

This stage answers the question "What is this skill?" The detailed CLI contract (commands, flags, formats) belongs to the Plan stage downstream.

Canonical References

• ./instructions/design-contract.md
• ./planning-brief.md
• ./contracts/design-contract.yml.tpl