cli-forge-distribute
cli-forge Distribute (Archived)
Do not use this stage for new work.
The npm publication contract now belongs to
../cli-forge-publish/SKILL.md. This
directory is retained only as historical reference for the older split-stage
model.
Purpose
Preserve historical guidance for the earlier split between repo-native release and npm distribution.
Canonical References
./instructions/release/npm-publish-runbook.md./planning-brief.md./shared-planning-brief.md./contracts/validation-report.yml.tpl
Entry Gate
| # | Check | Source |
|---|---|---|
| 1 | Caller understands this stage is archived | User / Router |
| 2 | New release work is being redirected to Publish | Router / User |
Required Inputs
- None for new workflows. Route new release work to Publish.
Workflow
- Tell the caller that npm publication is now owned by Publish.
- If historical context is needed, use the files in this directory as legacy background only; do not treat them as the active workflow contract.
- Route the user to
../cli-forge-publish/SKILL.md.
Outputs
- A redirection to Publish for any new release work
Exit Gate
| # | Check |
|---|---|
| 1 | Caller was redirected to Publish |
| 2 | No new workflow claims this stage is authoritative |
Guardrails
- Do not route new work here.
- Do not present this archived stage as the current source of truth for npm publication.
Next Step
Continue with ../cli-forge-publish/SKILL.md.
More from bytelandtechnology/cli-forge
cli-forge-scaffold
Scaffold stage for the cli-forge skill family: create a new Rust CLI Skill project from the authoritative templates and prepare it for validation.
33cli-forge-publish
Publish stage for the cli-forge skill family: manage the GitHub Release and multi-package npm publication automation for a generated skill.
33cli-forge-validate
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.
33cli-forge-design
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.
22cli-forge-plan
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.
22cli-forge-intake
Triage stage for the cli-forge skill family: classify the request as description, scaffold, extend, validate, or publish, confirm required inputs, load the shared rules, and hand off to the correct next phase.
13