project-intake-and-charter
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseProject Intake & Charter (Initiation Phase)
项目立项与章程(启动阶段)
Purpose
- Transform an ambiguous project request into a clear, structured project foundation that the PM Core Agent and downstream skills can rely on.
- This skill does NOT plan, estimate in detail, or make final decisions. Its job is to make implicit information explicit.
Scope: What this skill does and does not do
-
This skill WILL:
- Clarify the real problem being solved
- Identify business objectives (distinct from solutions)
- Define measurable success criteria
- Explicitly state in-scope and out-of-scope items
- Surface assumptions and constraints
- Identify key stakeholders
- Identify initial project risks
- Detect critical information gaps and create clarifying questions
-
This skill WILL NOT:
- Produce detailed plans
- Provide fine-grained estimates
- Make final business decisions or negotiate with stakeholders
- Send formal external communications
Inputs
- project_state.md: A Markdown document following the template in .
project-state.md - user_input: Fragmented or ambiguous project request.
Notes
- may be incomplete or partially populated.
project-state.md - may be informal, fragmented, or ambiguous.
user_input - The skill must tolerate ambiguity and avoid inventing facts.
Outputs (contract)
- New File: (The human-readable Project Definition).
project-charter.md - Updated File: (The operational context).
project-state.md
目的
- 将模糊的项目请求转化为清晰、结构化的项目基础,供PM Core Agent及后续技能依赖使用。
- 本技能不负责制定计划、进行详细估算或做出最终决策,其核心职责是将隐性信息显性化。
范围:本技能的职责边界
-
本技能将:
- 明确待解决的核心问题
- 识别业务目标(与解决方案区分开)
- 定义可衡量的成功标准
- 明确列出项目包含与不包含的内容
- 梳理假设条件与约束因素
- 识别关键相关方
- 识别项目初始风险
- 发现关键信息缺口并提出待澄清问题
-
本技能不会:
- 制定详细计划
- 提供细粒度估算
- 做出最终业务决策或与相关方谈判
- 发送正式外部沟通信息
输入
- project-state.md:遵循模板的Markdown文档。
project-state.md - user_input:碎片化或模糊的项目请求。
注意事项
- 可能不完整或仅部分填充内容。
project-state.md - 可能是非正式、碎片化或模糊的。
user_input - 本技能必须能够容忍模糊性,不得编造信息。
输出(交付内容)
- 新增文件:(供人阅读的项目定义文档)。
project-charter.md - 更新文件:(项目执行上下文文档)。
project-state.md
Output 1: Project Charter (project-charter.md
)
project-charter.md输出1:项目章程(project-charter.md
)
project-charter.mdFollows standard Project Charter format:
- Project Name & Metadata
- Problem Statement & Business Objectives
- Scope (In/Out)
- Key Stakeholders
- High-Level Risks
- Approval Sign-off Section
遵循标准项目章程格式:
- 项目名称及元数据
- 问题陈述与业务目标
- 范围(包含/不包含)
- 关键相关方
- 高层级风险
- 审批签字栏
Output 2: Updated Project State (project-state.md
)
project-state.md输出2:更新后的项目状态(project-state.md
)
project-state.mdUpdates specific sections of the state to reflect the new definition:
- (Synced from Charter)
## Objectives - (Synced from Charter)
## Scope - :
## Execution Log- : Added "Project Charter created."
history_summary - : "Reviewing Charter with stakeholders."
current_action - : "Obtain approval", "Initiate High-Level Planning."
next_actions
- : (If any)
## active_questions
Guardrails (must follow)
- Charter != Plan: The Charter defines what and why. It does NOT define how (detailed plan) or when (schedule).
- State = Brain: Do not put the full narrative in the state. Put the structural facts needed for decision making.
- If information is missing for the Charter, ask Clarifying Questions instead of inventing it.
Skill prompt (use this prompt when invoking the skill)
You are a Project Intake & Charter skill.
Task:
1. Analyze `project_state.md` and `user_input`.
2. Generate a valid `project-charter.md` file content defined as the Project Definition (Not a Plan).
3. Generate the update for `project-state.md` populating Objectives, Scope, and the Execution Log.
Input Constraints:
- Do NOT create a detailed WBS or Schedule yet. Focus on alignment and definition.
Output Format:
Provide the content for the two files clearly separated.Example execution (realistic)
Output
File: (excerpts)
project-charter.mdProject Charter: Data Migration
Problem
Reporting is slow...Scope
...
File: (updates)
project-state.mdObjectives
...Execution Log
- last_action: created project-charter.md
- current_action: waiting for user approval of charter
undefined更新状态文档的特定部分以反映新的项目定义:
- (与章程同步)
## 目标 - (与章程同步)
## 范围 - :
## 执行日志- :添加“已创建项目章程。”
history_summary - :“与相关方评审章程。”
current_action - :“获取审批”、“启动高层级规划。”
next_actions
- :(如有)
## active_questions
约束规则(必须遵守)
- 章程≠计划:章程定义项目的是什么和为什么,不定义如何做(详细计划)或何时做(进度安排)。
- 状态文档=核心信息库:不得在状态文档中放入完整叙述性内容,仅保留决策所需的结构化事实。
- 若章程制定缺少必要信息,应提出澄清问题而非编造内容。
技能调用提示(调用本技能时使用此提示)
You are a Project Intake & Charter skill.
Task:
1. Analyze `project_state.md` and `user_input`.
2. Generate a valid `project-charter.md` file content defined as the Project Definition (Not a Plan).
3. Generate the update for `project-state.md` populating Objectives, Scope, and the Execution Log.
Input Constraints:
- Do NOT create a detailed WBS or Schedule yet. Focus on alignment and definition.
Output Format:
Provide the content for the two files clearly separated.执行示例(真实场景)
输出
File: (excerpts)
project-charter.mdProject Charter: Data Migration
Problem
Reporting is slow...Scope
...
File: (updates)
project-state.mdObjectives
...Execution Log
- last_action: created project-charter.md
- current_action: waiting for user approval of charter
undefined