Results for “forward-outcomes”

Transform output-focused roadmaps into outcome-focused ones that communicate strategic intent, rewriting initiatives as outcome statements reflecting user and business impacts.

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Use when making a forward-looking claim with a checkable outcome (reply within 24h, error rate will drop, this skill will see more use) — record to state/predictions.jsonl with a review horizon so reflection can grade you later. Closes the in-the-moment double-loop.

Create product objectives, key results, initiatives, guardrails, and review cadence.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Record and analyze post-trade outcomes for trading signals, tracking false positives, missed opportunities, and regime mismatches to generate feedback for signal aggregation and skill improvement.

Runs a post-launch review of a shipped PRD against its success metrics, interviewing the user on metric movement, assumptions, and decisions, then publishing an outcome-review page to Confluence and updating linked artifacts.

Translates stakeholder feature requests into validated outcome statements before any work is committed. Use this skill — proactively and without waiting to be asked — whenever a stakeholder, exec, or customer arrives with a pre-packaged solution: "we need a dashboard", "add a Slack notification", "build an export feature", "create a report", "let's add a filter", "can we just add X". Also triggers for: "how do I push back on this request", "what outcome does this feature solve", "outcome vs output", "outcomes not features", "what are we really trying to achieve", "we're being a feature factory", "I need to reframe this as a problem", "the stakeholder is pushing a specific solution", "discovery before delivery", "assumption testing", "translate this request into an outcome", "ship outcomes not features". Runs the 'One Framework. Four Questions.' protocol (Liatti + Cagan + Torres): Behavior Change → Assumption Test → Cheapest Test → Success Metric. Produces an Outcome Brief with embedded AI prompts ready to pas

当意识到当前行为模式可能导致不理想的未来，需要一种具体方法来激发改变动力时

Generates frontend source code files and a PR description from BA, TechLead, PM, and BE artifacts, following a level-based implementation plan.

Facilitate a structured sprint retrospective to surface insights and produce actionable improvements with owners and deadlines.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Generates frontend source code and a PR description from BA, TechLead, PM, and BE artifacts, following a level-based implementation plan.

Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"

After a Content Factory run completes successfully, harvest prompts, character references, cost data, and quality scores; diff them against the canonical prompt_registry and character_identity store; open improvement PRs (prompt updates + new character references). Runs ONCE per successful run, then closes. Also files findings into a CF_IMPROVER_ISSUES.csv (Intelliverse audit framework pattern) for the librarian's weekly roll-up.

Monthly P&L, cashflow forecast, runway calculation, and top movers. Investor-ready Gamma deck plus Slack summary, archived to Notion. Runs monthly on a 1st-of-month cron schedule.

Aggregate closed trades from trader-memory-core into a weekly performance report with win rate, expectancy, profit factor, R-multiple, MAE/MFE, and pattern breakdowns by source skill, exit reason, sector, and mechanism.

Forwards a Gmail message to new recipients, with options for body notes, attachments, CC/BCC, HTML formatting, drafts, and dry runs.

Progress Tracking

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.

Push the LLM to reconsider, refine, and improve its recent output. Use when user asks for deeper critique or mentions a known deeper critique method, e.g. socratic, first principles, pre-mortem, red team.

Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.

Retro

Form UX

Tie out a fund NAV package end to end — assets, liabilities, capital, and per-share/per-unit price — proving the accounting equation, the price, and the day-over-day movement before the NAV is released.

Facilitates structured sprint retrospectives, analyzing team feedback and sprint data to generate prioritized, actionable improvement items.

Skeptical pushback on the outline before drafting starts. Asks whether the outline is MECE, BLUF, problem-agitate-solution; whether it covers the topic better than the SERP top-5; whether sections duplicate; whether each section earns its visual. One revision pass on FAIL (BLOG_AGENT_OUTLINE_REVISION_BUDGET, default 1).

Use this skill to evaluate which DataQ challenges have winning evidence and which don't. Covers documented vs anecdotal evidence and the 8 high-success patterns.

Create process maps with steps, decisions, and handoffs. TRIGGERS - Use when user needs help with process-map related tasks.

Protokolliert beA-Nachrichten, Versand und Empfangsbekenntnisse mit Fristen- und Risikoampel sowie Sofortschritten für Kanzlei-Workflows.

Run a pre-mortem — imagine the project has already failed one year from now and work backward to find the root causes before they happen. Load when the user asks for a pre-mortem, wants to imagine failure before committing, asks "what could go wrong before we start", "assume this fails — why", "risk analysis before launch", "what kills this project", "what could go wrong", or when deep-thinking diagnoses a pre-mortem frame. Based on Gary Klein's prospective hindsight method, which surfaces failure causes more effectively than forward risk analysis. Most useful right before a major commitment.

Orquestrador do pipeline de evolução do Reversa. Detecta o estágio físico da feature ativa em `_reversa_forward/` e sugere o próximo agente do ciclo forward (requirements, clarify, plan, to-do, audit, quality, coding). Use quando o usuário digitar "/reversa-forward", "reversa-forward", "iniciar evolução", "iniciar pipeline forward" ou pedir para conduzir o ciclo de uma feature do zero ao código. Não escreve artefatos de feature por conta própria, apenas roteia.

Plan team outings with activities and logistics. TRIGGERS - Use when user needs help with team-outing related tasks.