Workflow ppw

Skill awfaups/intake-governance/skills/workflow-ppw

Portable multi-agent governance skill for role-based planning, review, dispatch, and execution.

Install

npx -y skills add awfaups/intake-governance --skill workflow-ppw

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

PMW workflow detail layer for project inventory and process clarification after workflow selection is known. Use when the task is already confirmed as PMW, the user explicitly requests @PMW or legacy alias @PPW, or intake has classified the task as project inventory, asset mapping, current-state clarification, or process discovery. Produces dated and versioned workflow docs under the active project's root docs/YYYY_MM_DD_中文任务名_vN/ directory.

SKILL.md

1.8 KB, as published. Nobody here has run it

Workflow PMW

Use this skill only when the workflow type is already known to be PMW.

Treat this skill as a detail layer, not a public governance entry.

If the request still needs intake, routing, or cross-role governance, enter through @intake first.
Use this skill after workflow selection is settled.
Keep global handoff policy in intake-governance; keep PMW stage rules here and in references/ppw.md.

Activation response

✅ Project Mapping Workflow（PMW · 项目流程梳理工作流）已激活当前阶段：A1 – 项目资产盘点（Inventory）

Execution contract

This skill enforces:

inventory and process-clarification workflow only
required docs as mandatory deliverables
docs under docs/YYYY_MM_DD_中文任务名_vN/
A1 Inventory, A2 Goals, A3 Flows, A4 Contracts, A5 Risks, A6 Roadmap, and A7 Sign-off gates
fact-based output instead of speculative conclusions
explicit separation of verified facts, inferred facts, and unknowns
traceable evidence for important claims
no implementation inside PMW
later code-changing workflows must wait for explicit user confirmation of their documents before code generation
stop before deeper planning when critical repositories, configs, credentials, or provenance are missing

Gives 0 of the 12 instructions most automation workflows skills give

Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-06

write conventional commit messagesin 36 of 745, across 35 files
delete branches after mergein 30 of 745, across 21 files
make atomic commitsin 25 of 745, across 15 files
write minimal code to pass testsin 22 of 745, across 10 files
run tests before committingin 21 of 745, across 13 files
re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
use try-catch for error handlingin 20 of 745, across 6 files
write tests before implementationin 20 of 745, across 8 files
configure branch protection rulesin 19 of 745, across 5 files
explain the why in commit messagesin 19 of 745, across 9 files
refactor code while tests remain greenin 19 of 745, across 6 files
Interact with elements using refsin 19 of 745, across 11 files

Said here and by no other author read

use this skill only when workflow is known
enter through intake if routing is needed
produce the required mandatory deliverable documents
write docs under the dated versioned directory
complete all seven workflow gates
base output on facts instead of speculation

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.