ns-project-manager

Original：🇺🇸 English

Translated

5 scriptsChecked / no sensitive code detected

(NS) Gated PM workflow — clarify, structure, RICE/WSJF, sprint plan, PERT/Monte Carlo forecast; risk, status, meeting, OKR. Also commercial budget (orçamento, Function Points, proposta comercial; COSMIC/CFP only if asked), triple productivity delivery schedule (cronograma P100/P85/P50, prazo, when we deliver), and requirements enricher / grill-me for GitLab issues or chat. Use on transcripts, backlog, timeline, delivery date, status, orçamento, cotação, cronograma, enrich requirements — even if PM is unnamed. On "help" / "exemplos", list example prompts only. Do NOT use for coding, SDD requirements generation, or GitLab issue execution.

2installs

Sourcenextstage-brasil/skills

Added on2026-08-23

NPX Install

npx skill4agent add nextstage-brasil/skills ns-project-manager

SKILL.md Content

View Translation Comparison →

Project Manager

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

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

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.

Phase 0 — Intake

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

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.

Core pipeline (Phases 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.

On-demand modes (Phases 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`

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."

Anti-patterns

Read

references/anti-patterns.md

before any Phase 2 User Story.

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.

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.

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.

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

ns-project-manager

NPX Install

Tags

SKILL.md Content

Project Manager

Router

Help

Phase 0 — Intake

Gate protocol (mandatory between phases)

Core pipeline (Phases 1–5)

On-demand modes (Phases 6+)

Quick mode

Anti-patterns

GitLab MCP

Language matching (mandatory)

Global behavioral constraints

File index