菜单
Design stage for the cli-forge skill family: define or refresh the generated skill's high-level identity, purpose, positioning, and description contract before downstream stages proceed.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | cli-forge-design |
| description | Design stage for the cli-forge skill family: define or refresh the generated skill's high-level identity, purpose, positioning, and description contract before downstream stages proceed. |
Use this stage when the workflow needs one authoritative description contract for a generated Rust CLI Skill before later stages proceed.
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.
| # | Check | Source |
|---|---|---|
| 1 | handoff.yml exists with classification: design | Router |
| 2 | Skill scope is at least partially known | User request or handoff |
./planning-brief.md to load the shared
constraints.Cargo.toml package.descriptionSKILL.md purpose sectionREADME.md header and description--help, and
structured help--help renders man-like human-readable helphelp returns structured outputNAME -> SYNOPSIS -> DESCRIPTION -> OPTIONS -> FORMATS -> EXAMPLES -> EXIT CODES.cli-forge/design-contract.yml using the format defined in
./contracts/design-contract.yml.tpl.AskUserQuestion) with the options approve and continue, request changes, or stop for now when it is available. If no dialog-based chooser
is available, use a numbered text menu with the same three options and add
Other: <custom response> as the fallback escape hatch. Accept exact replies
1, 2, or 3, or Other: .... If a numeric reply includes additional
text, ask for clarification before proceeding. Do not require the user to
type the full option label..cli-forge/design-contract.yml — approved description contract| # | Check |
|---|---|
| 1 | Single-line purpose summary is approved |
| 2 | Positioning statement is approved |
| 3 | Sync surfaces list is complete |
| 4 | Help contract is recorded |
| 5 | Publish contract is recorded |
| 6 | design-contract.yml is generated and approved |
design-contract.yml. Do NOT proceed to the Plan or Scaffold stage autonomously. Call the runtime's dialog-based chooser (e.g., AskUserQuestion) for approval when it is available, or use the standardized numbered text fallback with 1. approve and continue, 2. request changes, 3. stop for now, and Other: <custom response>.Continue with ../cli-forge-plan/SKILL.md to
define the detailed CLI contract.
Scaffold stage for the cli-forge skill family: create a new Rust CLI Skill project from the authoritative templates and prepare it for validation.
Plan stage for the cli-forge skill family: define the detailed CLI contract including commands, flags, output formats, stream/repl/daemon capability scope, the daemon app-server contract, and runtime behavior before scaffold or extend stages proceed.
Publish stage for the cli-forge skill family: manage the GitHub Release and multi-package npm publication automation for a generated skill.
Router for the cli-forge skill family: classify the request, detect missing contract baselines, check filesystem state, and route to the earliest incomplete or takeover stage.
Validate stage for the cli-forge skill family: run the 47-check compliance ruleset against a scaffolded, takeover-adopted, or extended skill project and compare any daemon surface against the declared CLI plan.
Extend stage for the cli-forge skill family: add stream or repl features to an existing scaffolded skill project or to a takeover-adopted project that already matches the scaffold-compatible layout.