Cli Forge Scaffold

Entry Gate

Required Inputs

• skill_name
• Approved cli-plan.yml
• Optional author, version, rust_edition

Workflow

1. Run the pre-checks from ./instructions/new.md: require the skill name, verify cli-plan.yml, and refuse to overwrite an existing directory.
2. Create the directory structure.
3. Expand the templates from ./templates/ EXACTLY as defined by cli-plan.yml and the instruction file, restoring any install-safe dot-* resource alias to its intended dot-prefixed output path.
4. Verify that no {{token}} placeholders remain unresolved.
5. Run the required verification commands from the generated project root:
   • cargo build
   • cargo clippy -- -D warnings
   • cargo fmt --check
   • cargo test
6. Confirm the generated package layout stays within the documented boundary: baseline generated files plus feature-local support files. Repository-owned CI workflows and release scripts stay outside the generated project until Publish.
7. Generate .cli-forge/scaffold-receipt.yml using the template at ./contracts/scaffold-receipt.yml.tpl.

Outputs

• A new Rust CLI package directory
• .cli-forge/scaffold-receipt.yml

Exit Gate

Guardrails

• Use templates EXCLUSIVELY from the bundled ./templates/ directory for this stage. Do not reach outside this skill package for scaffold templates.
• Treat dot-* resource names inside ./templates/ as install-safe aliases only. Generated outputs must restore the intended dot-prefixed filename.
• Do not improvise project structure or dependencies. Everything must be tied back to the cli-plan.yml.
• The current scaffold baseline does not implement the planned daemon app-server capability. If cli-plan.yml marks daemon in_scope, stop and report that scaffold support for daemon must be implemented before generation can proceed.
• If any Cargo verification step fails, block the workflow and fix the scaffolded files before handing the work forward.

Next Step

Continue with ../cli-forge-validate/SKILL.md to run the full compliance rule set.