cli-forge-intake
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesecli-forge Intake
cli-forge 准入分流阶段
Use this stage when the current request needs routing or when you want to
resume the cli-forge workflow from the earliest safe phase.
当当前请求需要路由,或者你希望从最早的安全阶段恢复cli-forge工作流时,使用此阶段。
Stage Goal
阶段目标
Finish this stage with:
- the work classified as ,
scaffold,extend, orvalidatepublish - the work classified as ,
description,scaffold,extend, orvalidatepublish - the required user inputs identified and, when available, assembled
- the shared constraints loaded from the planning brief and the relevant instruction document
- an explicit handoff to the next stage skill
完成此阶段后需达成以下结果:
- 工作任务被分类为 、
scaffold、extend或validatepublish - 工作任务被分类为 、
description、scaffold、extend或validatepublish - 识别出所需的用户输入,在可用时完成汇总
- 从规划概要和相关说明文档中加载共享约束
- 明确移交到下一阶段的skill
Canonical References
标准参考
./planning-brief.md./instructions/new.md./instructions/add-feature.md./instructions/validate.md../cli-forge-publish/SKILL.md../cli-forge-publish/planning-brief.md../cli-forge-publish/instructions/release/skill-release-runbook.md../cli-forge-publish/templates/README.md
./planning-brief.md./instructions/new.md./instructions/add-feature.md./instructions/validate.md../cli-forge-publish/SKILL.md../cli-forge-publish/planning-brief.md../cli-forge-publish/instructions/release/skill-release-runbook.md../cli-forge-publish/templates/README.md
When To Use This Stage
适用场景
- The user asks for cli-forge help in a high-level way and the correct phase is not obvious yet.
- The user wants to create a new project but has not clearly supplied a valid skill name.
- The user wants to create a new project and the generated skill's description contract has not been approved yet.
- The user wants to add or
stream, but the project path or feature is still unclear.repl - The user wants to update an existing generated skill's purpose, positioning, or other user-facing contract.
- The user wants validation, but the target project path still needs to be resolved.
- The user wants to publish, do a release dry run, rehearse the destination mirror, check destination configuration, or adopt the release automation asset pack into a target CLI skill project.
- 用户以较高层级的方式寻求cli-forge帮助,且暂不明确对应哪个正确阶段
- 用户想要创建新项目,但尚未清晰提供有效的skill名称
- 用户想要创建新项目,且生成的skill描述约定尚未获批
- 用户想要添加 或
stream功能,但项目路径或功能需求仍不明确repl - 用户想要更新现有已生成skill的用途、定位或其他面向用户的约定
- 用户想要进行验证,但目标项目路径仍需确认
- 用户想要发布、执行发布dry run、演练目标镜像、检查目标配置,或是将发布自动化资产包导入到目标CLI skill项目中
Required Inputs By Outcome
不同结果对应的必填输入
- : the classified intent, generated skill scope, and the next stage that will consume the approved description contract
description - :
scaffold, plus optionalskill_name,author, andversionrust_edition - :
extendandproject_pathwherefeatureisfeatureorstreamrepl - :
validateproject_path - : release mode (
publish,report_only,dry_run, orrehearsal), current validation status, and any required destination configuration or credential contextlive_release
- :已分类的意图、生成的skill范围,以及将使用获批描述约定的下一阶段
description - :
scaffold,以及可选的skill_name、author和versionrust_edition - :
extend和project_path,其中feature为feature或streamrepl - :
validateproject_path - :发布模式(
publish、report_only、dry_run或rehearsal)、当前验证状态,以及任何所需的目标配置或凭证上下文live_release
Workflow
工作流程
- Read the user request and classify the intent as ,
description,scaffold,extend, orvalidate.publish - Load before choosing a downstream phase so the runtime contract and compliance posture stay in scope.
./planning-brief.md - Open the matching local instruction document for the likely next stage and use it as the detailed source of truth.
- Confirm the required inputs for that path:
- For , verify the work creates a new generated skill or changes the generated skill's user-facing contract.
description - For , verify the name is present, the approved description contract exists, and the work is intended to become a Rust CLI Skill project.
scaffold - For , verify both
extendandproject_path.feature - For , verify
validate.project_path - For , load
publish, verify whether the user wants../cli-forge-publish/planning-brief.md,report_only,dry_run, orrehearsal, and whether the work should start with validation or can proceed directly to the publish stage.live_release
- For
- Inspect the filesystem when it helps disambiguate the stage:
- missing target directory usually means followed by
descriptionscaffold - existing scaffolded project plus feature request means
extend - existing generated skill plus description-impacting request means
followed by
descriptionorextendvalidate - explicit audit or post-change verification means
validate - release, dry-run, rehearsal, destination-config work, or final
post-validation closure means
publish
- missing target directory usually means
- Route to the next stage skill and carry forward the resolved inputs.
- 读取用户请求,将意图分类为 、
description、scaffold、extend或validate。publish - 在选择下游阶段前先加载 ,确保运行时约定和合规要求在考虑范围内。
./planning-brief.md - 打开对应下一阶段的本地说明文档,将其作为详细的事实依据。
- 确认该路径所需的输入:
- 对于 ,确认该工作是创建新的生成skill,或是修改已生成skill的面向用户的约定。
description - 对于 ,确认名称已提供、获批的描述约定已存在,且该工作的目标是生成Rust CLI Skill项目。
scaffold - 对于 ,确认
extend和project_path均已提供。feature - 对于 ,确认
validate已提供。project_path - 对于 ,加载
publish,确认用户想要的是../cli-forge-publish/planning-brief.md、report_only、dry_run还是rehearsal,以及工作应该先进行验证还是可以直接进入发布阶段。live_release
- 对于
- 必要时检查文件系统以明确阶段:
- 缺少目标目录通常意味着先执行,再执行
descriptionscaffold - 已存在的脚手架项目加上功能请求意味着
extend - 已存在的生成skill加上影响描述的请求意味着先执行,再执行
description或extendvalidate - 明确的审计或变更后验证需求意味着
validate - 发布、dry-run、演练、目标配置工作,或是验证后的最终收尾意味着
publish
- 缺少目标目录通常意味着先执行
- 路由到下一阶段的skill,并携带已确认的输入。
Classification Examples
分类示例
- Create request with no project directory yet -> route to .
description - Existing generated skill plus purpose/positioning change -> route to
.
description - Existing scaffolded project plus or
streamrequest -> route torepl.extend - Audit or post-change verification request -> route to .
validate - Successful validation with no explicit release action -> route to in
publishmode.report_only - Mixed implementation and release request with unresolved project state ->
return to the earliest incomplete stage instead of skipping ahead to
.
publish
- 尚无项目目录的创建请求 -> 路由到 。
description - 已存在的生成skill加上用途/定位变更请求 -> 路由到 。
description - 已存在的脚手架项目加上或
stream请求 -> 路由到repl。extend - 审计或变更后验证请求 -> 路由到 。
validate - 验证成功且无明确发布操作 -> 以模式路由到
report_only。publish - 混合了实现和发布请求,且项目状态未明确 -> 返回最早的未完成阶段,而非直接跳到。
publish
Done Condition
完成条件
This stage is complete only when one downstream phase is clearly selected and
the next stage has the inputs it needs.
仅当明确选定了一个下游阶段,且下一阶段已获得所需的输入时,此阶段才算完成。
Next Step
后续步骤
- Route to whenever the description contract must be created or refreshed.
../cli-forge-description/SKILL.md - Route to for new project creation after
../cli-forge-scaffold/SKILL.md.description - Route to for
../cli-forge-extend/SKILL.mdorstreamwork.repl - Route to for compliance checking.
../cli-forge-validate/SKILL.md - Route to for release, dry-run, rehearsal, or destination-config work.
../cli-forge-publish/SKILL.md
- 当需要创建或更新描述约定时,路由到
../cli-forge-description/SKILL.md - 阶段完成后,如需创建新项目,路由到
description../cli-forge-scaffold/SKILL.md - 如需进行或
stream相关工作,路由到repl../cli-forge-extend/SKILL.md - 如需进行合规检查,路由到
../cli-forge-validate/SKILL.md - 如需进行发布、dry-run、演练或目标配置相关工作,路由到
../cli-forge-publish/SKILL.md