pedroromerol
6 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
pedroromerolunacpo
The standing craft of a Chief Product Officer — every strategic question answered in four steps (diagnosis, at least two options with tradeoffs, a clear stance, next steps) under four golden rules. Load it as context when acting as CPO of a workspace; it is also activated by role: cpo in that workspace's node.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27
pedroromerolunaprd
Interview the operator and write the strategic layer of a product —vision, problem, users, scope, competitors, opportunities, open questions, glossary— into the context/ of its node in the brain, never into the body repo. Manually triggered, last link of the discovery pipeline and the gate before specs.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27
pedroromerolunaproduct-builder-resolver
The capability index of the product-builder pack — which skill answers which capability, and where each one lives once installed. Load it to route a request to the right skill of the pack instead of guessing, and to see what the pack does not cover.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27
pedroromerolunaproduct-metrics
Build the measurement layer of a product — one candidate North Star, the tree of levers that hold it up with where each is measured, one metric per active hypothesis with its value today or a gap with an owner, and the antimetrics with their alarm thresholds — and write the Metric Brief. Manually triggered, or entered when the metric gate of product-strategy does not pass.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27
pedroromerolunaproduct-strategy
Run the socratic discovery interview that separates the symptom from the cause, grades the evidence, applies the metric gate and prioritizes up to three hypotheses, and write the Discovery Brief as dated research of the loaded product node. Manually triggered, first station of the discovery pipeline.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27
pedroromerolunavisual-designer
Specify any visual piece —a product interface, a presentation, an infographic— screen by screen or slide by slide: purpose, structure, hierarchy, the content of every block and the visual criteria applied, written as a dated document of the loaded product node. It closes by checking whether the session has a tool able to build it and only then offers to; with no tool it closes with the document. Manually triggered, invocable on its own.
- installs
- 1
- GitHub stars
- 2
- Updated
- Aug 27