create-pmos 0.1.0

package/payload/skills/prd.skill

@@ -0,0 +1,80 @@
+---
+name: prd
+description: Write a Product Requirements Document for an initiative. Use when an initiative has been chosen and needs a spec — the what and why — before any build or contract work begins.
+version: 1.0.0
+owner: wawan
+risk: low
+category: planning
+scope: read:okf, write:planning/prd
+---
+
+# prd — Write a Product Requirements Document
+
+This skill produces a PRD instance for one initiative. The PRD is the **spec** stage of the
+[SDLC loop](/okf/core/concepts/sdlc-loop.md): it says *what* to build and *why*, anchored to
+strategy, so a generator agent and the PM share one definition of the work before a contract is
+agreed.
+
+> **Format note:** this skill follows three-level progressive disclosure
+> ([SKILL-FORMAT](/skills/core/SKILL-FORMAT.md)). Level 1 above is the trigger; this body is Level 2;
+> rare variants are pushed to Level 3 sub-files referenced by name.
+
+## When to use vs. not
+
+- **Use** when an initiative is selected and needs a spec before build work.
+- **Do not use** to make the strategic case for *whether* to do the initiative — that is the
+  `strategic-brief` skill. The PRD assumes the initiative is already chosen.
+- **Do not use** to define how output is judged — that is the
+  [eval-rubric skill](/skills/core/eval-rubric.skill). PRD and rubric are authored together (see
+  [eval-driven-pm](/okf/core/concepts/eval-driven-pm.md)) but are separate artifacts.
+
+## Procedure
+
+1. **Anchor to strategy first.** Identify the parent KR in the
+   [OKR tree](/okf/core/concepts/okr-tree.md). If the initiative has no parent KR, stop — it is
+   unanchored work and the structural seed of [silent drift](/okf/core/concepts/watermelon-flag.md).
+   Resolve the anchor before writing the PRD.
+2. **Start from the template.** Use
+   [prd-template](/okf/core/templates/prd-template.md) as the scaffold. Do not invent a new
+   structure.
+3. **Write the problem before the solution.** State the user/PM problem and why it matters now.
+   A PRD that opens with a solution has skipped the only part the agent cannot reconstruct.
+4. **Make scope explicit on both sides.** In-scope *and* out-of-scope. The out-of-scope list is the
+   primary defense against agents over-building.
+5. **State success as outcomes, not output.** Success criteria describe a change in the world tied
+   to the parent KR, not a list of artifacts produced.
+6. **Pair with a rubric.** Flag that the [eval-rubric](/skills/core/eval-rubric.skill) must be
+   authored before the build starts — the eval is written first.
+7. **Keep it at control altitude.** The PRD specs *what and why*; it does not write the
+   application code or dictate the agent's path
+   ([control-plane](/okf/core/concepts/control-plane.md)).
+
+## Required content
+
+A complete PRD instance contains:
+
+- **Identity** — `initiative_id`, `product_slug`, `pm_slug`, parent `KR`.
+- **Problem** — who has it, why now, what it costs to leave unsolved.
+- **Goal & non-goals** — the change sought; explicit out-of-scope.
+- **Requirements** — what must be true of the solution (capabilities, constraints).
+- **Success criteria** — outcome-based, tied to the KR.
+- **Risks & open questions** — including anything to escalate to the PM.
+- **Links** — parent KR, the paired eval rubric, relevant OKF concepts.
+
+## Output and placement
+
+- PRD instances are **operational**, not OKF knowledge. They live under `/planning/prd/`, not in the
+  bundle ([okf-governance](/okf/core/concepts/okf-governance.md)).
+- Filename: descriptive and slugged, e.g. `p0-prd.md`.
+
+## Quality bar
+
+Before handing off, confirm: parent KR present; problem precedes solution; out-of-scope is
+non-empty; success criteria are outcomes not output; the eval rubric is queued to be written first.
+
+## Level 3 sub-cases
+
+- Multi-product or platform PRDs that span more than one `product_slug`: see `prd-multiproduct.md`
+  (author on first need).
+- Spike / discovery PRDs where the deliverable is a learning, not a feature: see
+  `prd-discovery.md` (author on first need).

package/payload/state/discoveries.md

@@ -0,0 +1,2 @@
+# Discoveries & friction log (append-only; ISO dates; tag friction with #friction)
+

package/payload/templates/agent-run-eval-rubric.md

@@ -0,0 +1,46 @@
+# Eval Rubric: Agent-run capability baseline (kit seed — copy per initiative)
+
+> Kit-seeded generic rubric (D54). Two purposes: (1) it is the TEMPLATE to copy to
+> `<initiative-id>-eval-rubric.md` and specialize per initiative (rewrite the dimensions to the
+> initiative's own outcomes; keep weights summing to 1.0); (2) it keeps the `rubrics` CI check
+> meaningful from day one. It scores a generic agent run outcome-only (D14) with weighted partial
+> credit (D15).
+
+## Frontmatter
+- type: Rubric
+- eval_type: capability
+- initiative_id: (set per initiative)
+- pass_threshold: 0.80
+- canonical_path: pmos/planning/evals/agent-run-eval-rubric.md
+
+## Gate assignment
+- **Quality Gate (deterministic):** repo CI green; `pmos-gate` (anchored + rubrics) green.
+- **Review Gate (adversarial):** the weighted dimensions below — evaluator skill, default-to-refute,
+  outcome-only; verdict appended to `pmos/state/evals.jsonl`; ADVISORY until locally calibrated.
+- **Acceptance Gate (PM):** the human PM merges and disposes — final and non-delegable (D12).
+
+## Weighted dimensions (Review Gate)
+Outcome-only (D14); partial credit (D15); anchors 0 / 0.5 / 1.0.
+
+| Dimension | Weight | Score | Wtd |
+|---|---:|---:|---:|
+| Contract satisfaction — every done_criterion of the pre-run contract is met, verified per its test_method | 0.40 | — | — |
+| Correctness of the produced artifact — behaves/reads as specified; no defect a reviewer can demonstrate | 0.30 | — | — |
+| Scope discipline — nothing out of contract scope changed; state files appended, never rewritten | 0.20 | — | — |
+| Traceability — initiative anchored; run + eval + friction logged to pmos/state/ | 0.10 | — | — |
+| **Total** | **1.00** | | **vs 0.80** |
+
+### Anchors (0 / 0.5 / 1)
+- **Contract:** 0 = a criterion unmet; 0.5 = met but a test_method not actually exercised; 1 = all met and exercised.
+- **Correctness:** 0 = demonstrable defect; 0.5 = works with a material caveat; 1 = defect-free under the rubric's probes.
+- **Scope:** 0 = out-of-scope change or state rewrite; 0.5 = minor drift, flagged; 1 = clean.
+- **Traceability:** 0 = unanchored or unlogged; 0.5 = partial logging; 1 = complete.
+
+## Sprint contract (pre-run)
+initiative_id: (set)
+run_id: (set)
+done_criteria:
+  1. (numbered, testable — agreed BEFORE work starts)
+test_method:
+  1. (one per criterion; name the gate that checks it)
+PM_approved: false  <!-- flip to true only on the PM's explicit word -->

package/payload/templates/pmos-gate.yml

@@ -0,0 +1,29 @@
+# PMOS portable kit — CI gate drop-in (D54). Copy to .github/workflows/pmos-gate.yml in the
+# target repo. Enforces the loop fail-closed on every PR, entirely from files — no network.
+name: pmos-gate
+on:
+  pull_request:
+    types: [opened, synchronize, reopened, edited, labeled, unlabeled]
+
+permissions:
+  contents: read
+
+jobs:
+  anchored:
+    name: anchored
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Initiative gate (file-backed)
+        env:
+          HEAD_REF: ${{ github.head_ref }}
+          PR_BODY: ${{ github.event.pull_request.body }}
+          PR_LABELS: ${{ join(github.event.pull_request.labels.*.name, ' ') }}
+        run: bash pmos/scripts/gate-initiative.sh
+  rubrics:
+    name: rubrics
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Rubric well-formedness
+        run: python3 pmos/planning/evals/check_rubrics.py