669 skills · sorted by relevance
Rewrite a feature-based roadmap around the changes customers and the business should experience. The result pairs each initiative with an outcome statement, success metrics, sequencing notes, and context connecting the plan to company strategy.
Bret Taylor 视角. Sierra 联合创始人 / CEO, OpenAI 董事会主席 (2024-), ex-Salesforce co-CEO, Google Maps 联合创造者. B2B SaaS enterprise 派代表 / outcome-based pricing 第一手提倡者 / brand-as-moat 在 agent 时代重新阐述者. 把 monetize-agents 语境从 "卖软件 access" 换成 "卖 outcome — 客户问题解决一次收一次费", 把 product 设计从 "feature breadth" 换成 "vertical depth + measurable outcome + procurement-grade trust". 用途: 当用户问 "agent 该怎么定价 / per-seat 还是 per-outcome / B2B agent 怎么 GTM / enterprise 0 到 1 / vertical 还是 horizontal / design partner 怎么搭 / 一开始要不要融大钱" 类问题时, 用 Bret Taylor 视角先把 "outcome 可不可测量 + vertical 是哪个 + 第一批 design partner 是谁" 盘清楚, 再给定价 / GTM / 融资判断. 当用户提到 "Bret Taylor" "Sierra" "outcome-based pricing" "deflection" "vertical agent" "design partner" "enterprise agent" "B2B agent GTM" "agent 定价" "agent procurement" 时使用. 即使用户只是说 "用 Sierra 思路看一下" 也应触发.
The English summary is being prepared. Showing the original description.
Create or assess an evidence-grounded, falsifiable outcome hypothesis: a testable prediction of what measurable business result will change, for whom, by when, and how leading and lagging indicators will prove or disprove it. Use when framing measurable outcomes, turning an MVP, POC, feature, or technical initiative into a beneficiary result, defining targets and indicators, or judging whether evidence is strong enough to invest. Also applies to business outcome hypotheses, value hypotheses, and outcome statements.
The English summary is being prepared. Showing the original description.
Review open commitments in acc and record success or failure with supporting notes. Distinguish self-assessment from owner validation or observed real-world results, and keep commitments open when they are still waiting on an outcome.
Evaluate a Claude Managed Agent against a written rubric, a set of checkable criteria, and guide improvements within a fixed attempt limit. After a version passes, prepare separate evaluation cases to check performance beyond the examples used for revision.
Break a feature into job stories that describe the user's situation, motivation, and desired outcome. Add six to eight observable acceptance criteria per story, defining how success will be checked, and include links to designs or prototypes.
Plan agent replacements while keeping the same workspace identity. The skill separates creating a successor from assigning it to the existing role, records both outcomes, and prepares durable handover notes and traceable replacement history.
Logs the outcome of a skill execution to observations/<skill-name>/runs.md. Trigger on: "log this run", "skill worked", "skill failed", "this didn't work", "log the outcome", "record this", "note that", or after any skill completes with a clear success, partial, or failure outcome. Creates the observations file if it does not exist, then appends an entry with date, task description, skill used, outcome, what worked, what failed, and any error messages observed.
The English summary is being prepared. Showing the original description.
Audit a roadmap or backlog to distinguish outcomes from outputs. Use when the user says "outcome vs output", "escaping the build trap", "are we building the right things", "roadmap review", "feature factory", "output-driven team", "we keep shipping but nothing changes", or wants to shift focus from shipping features to delivering value - even if they don't explicitly say "outcome vs output".
The English summary is being prepared. Showing the original description.
Design guidance for program outcome measurement in Salesforce nonprofit orgs: logic model structure, indicator taxonomy, impact reporting design, and grant compliance reporting using NPSP Program Management Module (PMM) or Nonprofit Cloud (NPC) Outcome Management. NOT for configuring PMM programs, cohorts and service deliveries - use admin/npsp-program-management. NOT for setting up grant tracking, funding awards and disbursements - use admin/grant-management-setup.
The English summary is being prepared. Showing the original description.
Post-launch review of a shipped PRD against the brief's success metrics. Did we move the metric? What did the data actually show? Which assumptions held, which broke? Which accepted-gap decisions resolved (confirmed vs. invalidated)? What would we do differently? Triggers on "outcome review", "did it work", "post-launch review", "did we move the metric", "retro the feature", "was it worth it". Produces a Confluence outcome-review page and updates the brief + linked decisions.
The English summary is being prepared. Showing the original description.
Write or revise a Paperclip plan that states the intended outcome, constraints, approach, and success checks. Capture unresolved decisions, maintain the saved plan, and request approval when the work requires it.
Create a one-page HTML onboarding plan for a new employee. Bring together first-day and first-week schedules, manager and buddy details, 30/60/90-day milestones, useful resources, and a checklist of outcomes that show readiness.
Look up active Polymarket prediction markets for elections, economic outcomes, and geopolitical events. Filter by topic or keyword to see market-implied probabilities, meaning probabilities reflected in prices, alongside trading volume and closing dates.
Store preferences, task lessons, and procedure outcomes in Hindsight, then retrieve relevant context before starting new work. It records detailed observations and can synthesize past experience into guidance for approaching the next task.
Route a goal through acc's scored-memory workflow, which uses evaluated stored information. Handle returned reasoning frames, submit proposals with confidence estimates, and present final answers with reference IDs before recording the eventual outcome.
Create a personalized investment proposal for a prospective client, covering goals, asset allocation, projected outcomes, fees, and transition steps. Outputs include a branded PowerPoint presentation, a PDF version, and a one-page summary for follow-up.
Build an Opportunity Solution Tree, a structured map linking one measurable product outcome to customer needs, possible solutions, and experiments. Use research findings to prioritize problems and define hypotheses, metrics, and success thresholds for testing ideas.
Build a daily or weekly worklog from recorded activity and checked outcomes. Separate plans, observed work, and verified completion, then summarize useful results and unfinished tasks with source links and clearly marked gaps or estimates.
Help a long-running agent reconnect with the intended product outcome after context compaction or a major work transition. Trace the current work hierarchy and read relevant source files to rebuild grounding before the next consequential action.
Evaluate an AI product or feature idea by connecting customer problems, business outcomes, testable assumptions, risks, and differentiation. Produce a structured recommendation with lightweight experiments, success measures, and next steps for an investment decision.
Turn a major product initiative into a testable hypothesis with a clear target user and expected outcome. Define small experiments, measurable success criteria, and an evaluation timeframe before committing to full development.
Analyze incoming Slack messages, emails, or escalations before replying. Separate the explicit request from the outcome behind it, clarify requirements and success criteria, and develop a reply or counterproposal while clearly labeling assumptions.
Investigate failed or unexpected Stripe payments using exact record IDs, processing states, events, amounts, and currencies. Separate what the customer sees from Stripe's state and integration behavior, then identify the next action without changing payment records during diagnosis.