pedroromeroluna
- 13 skills
- 0 followers
- 12 hours ago last updated
- ▌ Cpo · pedroromerolunaThe 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.
- ▌ Cto · pedroromerolunaThe standing craft of a Chief Technology Officer — every technical question answered in four steps (diagnosis of what exists and its constraints, at least two options with tradeoffs and long-term cost, a clear stance that always names the alternatives discarded and why, next steps that can be verified) under five golden rules for a non-developer builder. The state of the art — models, prices, capabilities — is verified live before opining, never answered from memory. Load it as context when acting as CTO of a workspace; it is also activated by `role: cto` in that workspace's node.
- ▌ Prd · pedroromerolunaInterview 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.
- ▌ Grill · pedroromerolunaPressure the facts behind a claim before a decision closes — counter-question with a concrete example, capped attempts, escape hatches, evidence hierarchy — and route what comes out to the loaded node's decisions or backlog. Manually triggered, and also the method any other interviewing tool cites by path.
- ▌ UX Research · pedroromerolunaDesign one research round against the single riskiest hypothesis — behavioral screening, one modality chosen on purpose, a guide whose every question is tied to a hypothesis or a job dimension — and write the Research Plan as dated research of the loaded product node. Manually triggered, third station of the discovery pipeline.
- ▌ Insight Engine · pedroromerolunaConverge the raw answers of real fieldwork —clusters with their noise and their outliers, jobs to be done in three dimensions with two verbatims each, the customer profile, opportunities scored against the business outcome— and write the Insight Brief as dated research of the loaded product node. Manually triggered, fifth station of the discovery pipeline: the first one that runs after real fieldwork.
- ▌ Ideation Engine · pedroromerolunaRun the solution space in two modes — DIVERGE prepares the workshop (traceable How Might We, seed ideas sealed until the humans have ideated, a timeboxed agenda and the board written zone by zone) and CONVERGE reads what the team produced and voted and writes the Value Map plus the prototype brief. Manually triggered, sixth station of the discovery pipeline; it never picks the winning idea.
- ▌ Market Research · pedroromerolunaSize the opportunity with secondary research only — directional TAM/SAM/SOM where every number carries its cited source and the assumption that turns it into a number for this product — and write the Market Brief as dated research of the loaded product node. Manually triggered, second station of the discovery pipeline.
- ▌ Product Metrics · pedroromerolunaBuild 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.
- ▌ Synthetic Users · pedroromerolunaPilot the v1 research guide against synthetic personas —every trait marked as evidence or assumption, at least one skeptic— to find broken questions before spending real fieldwork, and write the Diagnosis + Script v2. Manually triggered, fourth station of the discovery pipeline; it validates nothing.
- ▌ Visual Designer · pedroromerolunaSpecify 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.
- ▌ Product Strategy · pedroromerolunaRun 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.
- ▌ Product Builder Resolver · pedroromerolunaThe 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.