Opportunity decision

Skill brian8a1/senso-agent-skills/skills/opportunity-decision

Support and record a product decision for one Senso Opportunity. Use when a product manager or designer is comparing responses, needs the evidence and contradictions behind an Opportunity, wants to create or update a Solution, record alternatives and reasoning, set an explicit priority boost, or decide that more evidence is required.From its SKILL.md

Install

npx -y skills add brian8a1/senso-agent-skills --skill opportunity-decision

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

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
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.

SKILL.md

2.0 KB, 342 tokens by cl100k_base, as published. Nobody here has run it

Make an Opportunity decision

Help the human choose a response to a confirmed Opportunity. Senso supplies evidence and memory; the human retains authority.

Procedure

Resolve the Opportunity with senso_lookup. Read its detail, related Solutions, relevant Living Document, recent Decisions, and only the cited raw Signals needed to judge the choice.
Use senso_analyze when the decision depends on cross-Opportunity volume, trend, source, segment, or activity rather than one item.
Present:
- the problem and affected users/accounts;
- evidence supporting it and contradictory evidence;
- existing Solutions and prior decisions;
- alternatives, assumptions, missing evidence, and reversibility;
- the exact decision that remains human-owned.
Do not write while the user is exploring. After an explicit decision, use senso_decide to create/update the Solution or log the Decision with its reasoning and alternatives.
Re-read the Opportunity/Solution and report the resulting Backlog item, state, priority boost, and Living Document reference.

Guardrails

Do not generate a technical implementation plan; the decision records what and why, not how a repository must change.
Do not use legacy RICE fields to rank the Backlog. Use Senso's returned priority and only apply priority_boost when the human explicitly chooses it.
Do not erase contradictory evidence or rejected alternatives.
Use senso_map only when the confirmed decision changes a Group, node, anchor, or metric relationship.

Result

Return the confirmed Decision, created or updated Solution, supporting references, rejected alternatives, and remaining measurement question.

What ships with it: 1 file

493 B alongside SKILL.md

agents/

openai.yaml493 B