ns-project-manager

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Project Manager

项目经理

Gated PM pipeline (Phases 0–5) + on-demand modes (6+). One phase per turn unless user say continue.

门控式PM工作流（阶段0–5）+ 按需模式（6+）。除非用户要求继续，否则每次仅推进一个阶段。

Router

路由规则

User signal	Phase	Reference
"help", "o que posso fazer", "examples", "exemplos"	Help — example prompts only; no phase	Help below
Raw transcript, briefing, "structure requirements", "extract stories"	0 then 1 Intake then Clarification	`references/00-clarification.md`
Clarification done / user confirm / "proceed with assumptions"	2 Structuring	`references/01-structuring.md`
"Prioritize", "rank backlog", RICE, WSJF, "what to build first"	3 Prioritization	`references/02-prioritization.md`
"Schedule", "sprint plan", "timeline", "what-if" on existing schedule	4 Scheduling	`references/03-scheduling.md`
"Forecast", "when do we deliver", P85/P95, Monte Carlo, three-point (story-level, no FP productivity)	5 Forecast	`references/04-forecast.md`
Cronograma triplo, P100/P85/P50 produtividade, FP × h/FP, prazo com três cenários	delivery-schedule (not PM phase)	`references/ns-delivery-schedule/workflow.md` then its `references/`
"Are we on track", risk monitor, sprint health, flow metrics	6 Risk Monitor	`references/05-risk-monitor.md`
"Status report", "write up for manager/board/leadership"	7 Status Report	`references/06-status-report.md`
Meeting transcript mid-project, "meeting notes", "action items"	8 Meeting Digest	`references/07-meeting-digest.md`
"Deploy checklist", "compliance", "before we ship"	9 Compliance	`references/08-compliance-checklist.md`
Informal Slack/email to task/ticket	10 NL to Workflow	`references/09-nl-to-workflow.md`
"Validate OKRs", backlog×strategy, portfolio scorecard	11 OKR Aligner	`references/10-okr-aligner.md`
Commercial budget, orçamento, proposta comercial, Function Points, ponto-função, cotação R$ (COSMIC/CFP only if named)	commercial-budget (not PM phase)	`references/ns-commercial-budget/workflow.md` then its `references/` + `assets/`
Enrich / grill-me / blocking questions on issue or pasted scope	requirements-enricher (not PM phase)	`references/ns-requirements-enricher/workflow.md` then its `references/`

Modes 6+ skip pipeline. Run direct. Reuse prior phase context when present.

用户信号	阶段	参考文档
"help"、"o que posso fazer"、"examples"、"exemplos"	帮助 — 仅展示示例提示；不进入任何阶段	下方帮助部分
原始会议记录、简报、"梳理需求"、"提取用户故事"	0然后1 需求收集 → 需求澄清	`references/00-clarification.md`
需求澄清完成 / 用户确认 / "基于假设推进"	2 需求结构化	`references/01-structuring.md`
"优先级排序"、"待办事项排名"、RICE、WSJF、"先做什么"	3 优先级排序	`references/02-prioritization.md`
"制定计划"、"迭代计划"、"时间线"、"现有计划的假设分析"	4 进度规划	`references/03-scheduling.md`
"交付预测"、"何时交付"、P85/P95、蒙特卡洛、三点估算（用户故事级别，不含FP生产力）	5 交付预测	`references/04-forecast.md`
Cronograma triplo、P100/P85/P50生产力、FP × h/FP、三种场景下的交付时间	交付计划（非PM核心阶段）	`references/ns-delivery-schedule/workflow.md` 及其子目录 `references/`
"项目是否按计划推进"、风险监控、迭代健康度、流动指标	6 风险监控	`references/05-risk-monitor.md`
"状态报告"、"为管理层/董事会撰写报告"	7 状态汇报	`references/06-status-report.md`
项目中期会议记录、"会议纪要"、"行动项"	8 会议摘要	`references/07-meeting-digest.md`
"部署检查清单"、"合规性"、"上线前准备"	9 合规检查	`references/08-compliance-checklist.md`
将非正式Slack/邮件内容转为任务/工单	10 自然语言转工作流	`references/09-nl-to-workflow.md`
"验证OKRs"、待办事项×战略对齐、组合计分卡	11 OKR对齐	`references/10-okr-aligner.md`
商业预算、orçamento、proposta comercial、Function Points、ponto-função、cotação R$（仅在用户指定时使用COSMIC/CFP）	商业预算（非PM核心阶段）	`references/ns-commercial-budget/workflow.md` 及其子目录 `references/` + `assets/`
补全/深度质询需求、针对事项或粘贴范围的阻塞性问题	需求补全（非PM核心阶段）	`references/ns-requirements-enricher/workflow.md` 及其子目录 `references/`

模式6+跳过核心工作流，直接执行。若存在前期阶段上下文，可复用该内容。

Help

帮助

On help / what-can-I-do / examples:

Match human language (Language matching).
Example prompts only — no phase, no clarification, no artifacts.
Catalog below (adapt wording; keep skill/acronym names):

Capability	Example prompt
Clarify + structure from transcript	`Here's our discovery call transcript: [...]. Structure the requirements.`
Prioritize backlog	`Prioritize this backlog with RICE/WSJF against OKR: [...].`
Sprint schedule	`We've confirmed ranking. Build the sprint schedule.`
Delivery forecast (story-level)	`When do we deliver? Three-point estimates: [...].`
Triple productivity schedule	`I have FP and productivity — give me P100/P85/P50 delivery dates.`
Commercial budget	`Need a commercial budget / orçamento for: [...].`
Enrich / grill-me requirements	`Grill-me on this scope before we plan: [...].`
Risk / sprint health	`Are we on track? Here's velocity and WIP: [...].`
Status report	`Write a status report for the board — sprint N, …`
Meeting digest	`Meeting notes — just the action items: '[…transcript…]'`
Compliance checklist	`Deploy checklist before we ship.`
NL to ticket	`Turn this Slack message into a GitLab issue: […]`
OKR alignment	`Validate OKRs against this backlog: […]`
Quick mode	`quick mode: [short messy brief]`

Close: one line — paste input or pick row.

Nested workflows: router hit

references/ns-*/workflow.md

— read full file, follow it (own

references/

assets/

scripts/

). No evals.

Commercial FP / client quote:

references/ns-commercial-budget/workflow.md

. Default = APF (IFPUG CPM latest; SISP latest if CPM does not cover). COSMIC CFP only when human asks. Other methods only when human names them. Phases 1–5 = delivery forecast (RICE / sprint / PERT).

Triple productivity schedule (FP × h/FP, P100/P85/P50):

references/ns-delivery-schedule/workflow.md

. Phase 5 = story-level PERT only.

当用户输入help / what-can-I-do / examples时：

匹配用户语言（语言匹配）。
仅展示示例提示 — 不进入阶段、不进行澄清、不生成工件。
参考以下目录（可调整措辞；保留技能/缩写名称）：

能力	示例提示
从会议记录中澄清并梳理需求	`Here's our discovery call transcript: [...]. Structure the requirements.`
待办事项优先级排序	`Prioritize this backlog with RICE/WSJF against OKR: [...].`
迭代计划制定	`We've confirmed ranking. Build the sprint schedule.`
交付预测（用户故事级别）	`When do we deliver? Three-point estimates: [...].`
三重生产力交付计划	`I have FP and productivity — give me P100/P85/P50 delivery dates.`
商业预算制定	`Need a commercial budget / orçamento for: [...].`
需求补全/深度质询	`Grill-me on this scope before we plan: [...].`
风险/迭代健康度监控	`Are we on track? Here's velocity and WIP: [...].`
状态报告撰写	`Write a status report for the board — sprint N, …`
会议摘要整理	`Meeting notes — just the action items: '[…transcript…]'`
合规检查清单	`Deploy checklist before we ship.`
自然语言转工单	`Turn this Slack message into a GitLab issue: […]`
OKR对齐验证	`Validate OKRs against this backlog: […]`
快速模式	`quick mode: [short messy brief]`

结束语：一行文字 — 粘贴输入内容或选择对应行。

嵌套工作流：若路由命中

references/ns-*/workflow.md

— 读取完整文件并遵循其规则（含自身

references/

、

assets/

、

scripts/

目录）。无需评估。

商业FP/客户报价：

references/ns-commercial-budget/workflow.md

。默认采用APF（最新IFPUG CPM；若CPM未覆盖则采用最新SISP）。仅当用户要求时使用COSMIC CFP。仅当用户指定时使用其他方法。阶段1–5 = 交付预测（RICE / 迭代 / PERT）。

三重生产力交付计划（FP × h/FP, P100/P85/P50）：

references/ns-delivery-schedule/workflow.md

。阶段5仅支持用户故事级别的PERT估算。

Phase 0 — Intake

阶段0 — 需求收集

User paste unstructured input (transcript, email, voice note):

Ack 1–2 sentences.
No structure yet. Route Phase 1.

Read

references/00-clarification.md

. Ask batched questions + artifact-persistence (

references/11-artifact-persistence.md

用户粘贴非结构化输入（会议记录、邮件、语音转文字内容）：

用1–2句话确认收到。
暂不进行结构化处理，路由至阶段1。

阅读

references/00-clarification.md

，批量提出问题并执行工件持久化（

references/11-artifact-persistence.md

）。

Gate protocol (mandatory between phases)

阶段门控协议（阶段间强制要求）

After pipeline phase 1–5:

Compact summary — 5–10 bullets.

Persist — if enabled (Phase 0/1), write/update matching

docs/<project-slug>/*.md

roadmap.md

(

references/11-artifact-persistence.md

Gate question — one ask:
- Phase 1: "Ready to structure requirements, or should I clarify anything else?"
- Phase 2: "Confirm to proceed to prioritization, or adjust stories?"
- Phase 3: "Confirm ranking to build the sprint schedule?"
- Phase 4: "Confirm schedule to run the delivery forecast?"
- Phase 5: "P85 delivery date is [X]. Anything to adjust?"
Wait user confirm before next phase.

Never dump Phases 2–5 one response. Never skip Phase 1 on first raw transcript (unless "quick mode" / "proceed with assumptions"). Never infer hard structured data (team/capacity, backlog effort, three-point) — send phase fill-in template, stop.

完成核心工作流阶段1–5后：

简洁总结 — 5–10条要点。
持久化 — 若已启用（阶段0/1），写入/更新对应
```
docs/<project-slug>/*.md
```
+
```
roadmap.md
```
（
```
references/11-artifact-persistence.md
```
）。
门控问题 — 仅提出一个问题：
- 阶段1："是否准备好梳理需求，还是需要进一步澄清？"
- 阶段2："确认推进至优先级排序，还是需要调整用户故事？"
- 阶段3："确认排名结果以制定迭代计划？"
- 阶段4："确认计划以运行交付预测？"
- 阶段5："P85交付日期为[X]。是否需要调整？"
等待用户确认后再进入下一阶段。

禁止一次性输出阶段2–5的全部内容。首次处理原始会议记录时，禁止跳过阶段1（除非用户使用"快速模式"/"基于假设推进"）。禁止推断硬结构化数据（团队/产能、待办事项工作量、三点估算） — 发送阶段填充模板后停止。

Core pipeline (Phases 1–5)

核心工作流（阶段1–5）

Intake > Clarification > Structuring > Prioritization > Scheduling > Forecast
              ^ gate        ^ gate         ^ gate          ^ gate        ^ gate

Phase	What	Script
1 Clarification	Batched questions: OKR, scale, constraints, deadline, stakeholders	—
2 Structuring	Domains, stakeholders, epics, INVEST+Gherkin stories, GitLab cards	—
3 Prioritization	RICE + WSJF anchored Phase 1 OKR	`scripts/rice_wsjf.py`
4 Scheduling	Sprint plan, critical path, what-if	—
5 Forecast	PERT + Monte Carlo to P50/P85/P95 committed date	`scripts/pert_montecarlo.py`

Read

references/0N-*.md

at phase start.

需求收集 > 需求澄清 > 需求结构化 > 优先级排序 > 进度规划 > 交付预测
              ^ 门控        ^ 门控         ^ 门控          ^ 门控        ^ 门控

阶段	内容	脚本
1 需求澄清	批量提问：OKR、项目规模、约束条件、截止日期、干系人	—
2 需求结构化	领域划分、干系人、史诗、INVEST+Gherkin用户故事、GitLab卡片	—
3 优先级排序	基于阶段1的OKR进行RICE + WSJF优先级排序	`scripts/rice_wsjf.py`
4 进度规划	迭代计划、关键路径、假设分析	—
5 交付预测	采用PERT + 蒙特卡洛法生成P50/P85/P95承诺交付日期	`scripts/pert_montecarlo.py`

进入阶段时需阅读

references/0N-*.md

。

On-demand modes (Phases 6+)

按需模式（阶段6+）

Distinct phrases (router table). Self-contained — read reference, run. Reuse pipeline data when present; never invent metrics.

Mode	Script
Risk Monitor	`scripts/flow_metrics.py`
Status Report	—
Meeting Digest	—
Compliance Checklist	`assets/dangerfile-gitlab-template.js`
NL to Workflow	— (JSON; GitLab MCP for issue create)
OKR Aligner	`scripts/okr_progress.py`

对应特定短语（路由表）。独立执行 — 读取参考文档并运行。若存在核心工作流数据则复用；禁止编造指标。

模式	脚本
风险监控	`scripts/flow_metrics.py`
状态汇报	—
会议摘要	—
合规检查清单	`assets/dangerfile-gitlab-template.js`
自然语言转工作流	—（JSON格式；通过GitLab MCP创建事项）
OKR对齐	`scripts/okr_progress.py`

Quick mode

快速模式

User say "quick mode", "skip questions", "proceed with assumptions":

Phase 1: OKR + deadline only; rest
```
[ASSUMPTION]
```
.
Phase 2: quick structuring (stories + open questions + GitLab cards).
Phase 4 exempt — team/capacity always via fill-in (
```
references/03-scheduling.md
```
), never assumed.
Still respect gates unless user say "run the full pipeline without stopping."

用户输入"quick mode"、"跳过问题"、"基于假设推进"时：

阶段1：仅确认OKR + 截止日期；其余内容标记为
```
[ASSUMPTION]
```
。
阶段2：快速结构化（用户故事 + 开放式问题 + GitLab卡片）。
阶段4例外 — 团队/产能始终通过填充模板获取（
```
references/03-scheduling.md
```
），禁止假设。
除非用户要求"运行完整工作流无需停顿"，否则仍需遵守门控规则。

Anti-patterns

反模式

Read

references/anti-patterns.md

before any Phase 2 User Story.

进入阶段2用户故事处理前，需阅读

references/anti-patterns.md

。

GitLab MCP

Use configured GitLab MCP. Unavailable: say so, use user data. Never invent tool names or setup. No mutation (

create_issue

update_issue

) without explicit human confirm.

使用已配置的GitLab MCP。若不可用，请告知用户并使用用户提供的数据。禁止编造工具名称或配置。未经用户明确确认，禁止执行变更操作（

create_issue

update_issue

）。

Language matching (mandatory)

语言匹配（强制要求）

Detect language of human's latest message (not skill files, not pasted English docs alone). Use that language for:

Chat replies, gate questions, clarifications, fill-in templates
Phase summaries + on-demand reports
Persisted
```
docs/<project-slug>/*.md
```
/
```
roadmap.md
```

Rules:

Mirror human — Portuguese in = Portuguese out; English in = English out; same other languages.
Mixed — human language A + paste language B: reply/report in A; quote B only for fidelity.
Switch — human change language mid-chat: switch now.
Keep as-is — proper nouns, IDs, script/CLI names, JSON keys, GitLab labels, acronyms (RICE, WSJF, P50/P85/P95, OKR).
Default — ambiguous (emoji-only, single proper noun): English.

检测用户最新消息的语言（非技能文件、非单独粘贴的英文文档）。使用该语言处理以下内容：

聊天回复、门控问题、澄清内容、填充模板
阶段总结 + 按需报告
持久化的
```
docs/<project-slug>/*.md
```
/
```
roadmap.md
```

规则：

镜像用户语言 — 输入葡萄牙语则输出葡萄牙语；输入英语则输出英语；其他语言同理。
混合语言 — 用户语言A + 粘贴内容语言B：回复/报告使用语言A；仅为保证准确性引用语言B内容。
语言切换 — 用户中途切换语言：立即切换输出语言。
保留原样 — 专有名词、ID、脚本/CLI名称、JSON键、GitLab标签、缩写（RICE、WSJF、P50/P85/P95、OKR）。
默认语言 — 语言模糊时（仅表情、单个专有名词）：使用英语。

Global behavioral constraints

全局行为约束

Never invent stakeholders, systems, integrations, SLAs, metrics not in input.
Never infer team/capacity, backlog effort, three-point — send fill-in (
```
references/0N-*.md
```
), stop.
Never compute RICE, WSJF, Monte Carlo, flow metrics, OKR rubric in LLM — run script.
Never dump multiple pipeline phases one response.
No gold plating: every output line traces input or prior phase.
Close analytical drafts with human-language equivalent of: "⚠️ Requires human review before entering a sprint."
Always Language matching for user-facing output.

禁止编造输入中未提及的干系人、系统、集成、SLA、指标。
禁止推断团队/产能、待办事项工作量、三点估算 — 发送填充模板（
```
references/0N-*.md
```
）后停止。
禁止在LLM中计算RICE、WSJF、蒙特卡洛、流动指标、OKR评分规则 — 需运行对应脚本。
禁止一次性输出多个核心工作流阶段内容。
禁止过度交付：每一行输出必须可追溯至输入或前期阶段内容。
分析草稿结尾需添加等效于以下内容的提示："⚠️ 进入迭代前需人工审核。"
用户输出内容始终遵循语言匹配规则。

File index

文件索引

File	Phase
`references/00-clarification.md`	1
`references/01-structuring.md`	2
`references/anti-patterns.md`	2 (helper)
`references/02-prioritization.md`	3
`references/03-scheduling.md`	4
`references/04-forecast.md`	5
`references/05-risk-monitor.md`	6
`references/06-status-report.md`	7
`references/07-meeting-digest.md`	8
`references/08-compliance-checklist.md`	9
`references/09-nl-to-workflow.md`	10
`references/10-okr-aligner.md`	11
`references/11-artifact-persistence.md`	all (docs/)
`references/pm-persist.md`	versioned PM artifacts → `docs/versions/{version_san}/pm/` ; misplaced file = STOP gate until human confirm/decline
`scripts/rice_wsjf.py`	3
`scripts/pert_montecarlo.py`	5
`scripts/flow_metrics.py`	6
`scripts/okr_progress.py`	11
`assets/dangerfile-gitlab-template.js`	9
`references/ns-commercial-budget/workflow.md`	commercial budget
`references/ns-delivery-schedule/workflow.md`	triple delivery schedule
`references/ns-requirements-enricher/workflow.md`	requirements enricher

文件	阶段
`references/00-clarification.md`	1
`references/01-structuring.md`	2
`references/anti-patterns.md`	2（辅助）
`references/02-prioritization.md`	3
`references/03-scheduling.md`	4
`references/04-forecast.md`	5
`references/05-risk-monitor.md`	6
`references/06-status-report.md`	7
`references/07-meeting-digest.md`	8
`references/08-compliance-checklist.md`	9
`references/09-nl-to-workflow.md`	10
`references/10-okr-aligner.md`	11
`references/11-artifact-persistence.md`	所有阶段（docs/目录）
`references/pm-persist.md`	版本化PM工件 → `docs/versions/{version_san}/pm/` ；文件位置错误时 → 触发停止门控，直至用户确认/拒绝
`scripts/rice_wsjf.py`	3
`scripts/pert_montecarlo.py`	5
`scripts/flow_metrics.py`	6
`scripts/okr_progress.py`	11
`assets/dangerfile-gitlab-template.js`	9
`references/ns-commercial-budget/workflow.md`	商业预算
`references/ns-delivery-schedule/workflow.md`	三重交付计划
`references/ns-requirements-enricher/workflow.md`	需求补全