David Laribee laribee

🧠 Framing Assistant Prompt

You are a Framing Assistant. Your job is to help a team collaboratively define their identity, mission, and operating context through a guided process called Framing.

At each step, you must:

Act as a facilitator and assistant
Use retrieval-augmented generation (RAG) to ground your responses using provided documents
Never fabricate information or answer beyond your expertise
Make the process iterative, not linear: teams can return to any prior step

Impact- and Outcome-focused OKR Evaluation AI/LLM Prompt

Persona

You are an expert in OKRs, Lean UX, and business strategy.

Instructions  Please evaluate the following OKRs using the strategic outcome framework that distinguishes between Impact OKRs and User Behavioral Outcome OKRs.

Paste your OKRs below:

Fannie Mae Digital Products Engineering Dojo

Timeframe

3 Weeks, March 7th

Elevator Pitch

Our product engineering dojo is an immersive learning space where teams build a product mindset and best-in-class engineering skills. We do this by putting learning ahead of process by working on their actual product backlog, pairing teams with dedicated product and engineering coaches, and iterating rapidly twice a week.

Welcome to the DevOps Dojo

In 2016 I was hired as one of the head coaches of a massive DevOps transformation. The goal was to, in a 7000+ person IT organization, get teams fluent in topics such as CI/CD, automated testing, and product management. Our dojo team created a successful, impactful program at scale.

I’ll share experiences and learnings from my 6-month journey. Starting with the concept of a DevOps Dojo, we’ll then explore it from four, detailed perspectives: product, place, process, and people.

Product: Elaborating on the classic “coder’s dojo” - focused on building technical skills - to a “DevOps Dojo” where we perfect technical skills while delivering on product learning goals.
Place: A virtual tour through the engineering spaces that promote collaborative, rapid feedback, and high energy work.
Process: How we scaled to 12 concurrent dojo teams of 4-16 people with a custom pull system (kanban) featuring unusual-but-realistic WIP limits.
People: What skills (some s

	[HttpPost]
	public IActionResult Post(CreateEventDto m)
	{
	var organizer = new OrganizersService().GetOrganizerDetails( new AuthenticationService().GetCurrentUser());

	if (m.Description == null) throw new ArgumentException();
	if (m.Title == null) throw new ArgumentException();

	if (m.Starts > m.Ends)
	{

	'use strict';

	const fizzBuzz = (inputNumber) => {

	let returnVal = '';

	if (inputNumber % 3 === 0) {
	returnVal += 'Fizz';
	}

	'use strict';

	const fizzBuzz = (inputNumber) => {

	let returnVal = '';

	if (inputNumber % 3 === 0) {
	returnVal += 'Fizz';
	}

	### Keybase proof

	I hereby claim:

	* I am laribee on github.
	* I am laribee (https://keybase.io/laribee) on keybase.
	* I have a public key ASD4kwsLADFP_VSMoNdr-Tg-I_ISFKzuU_jwwmpqTAYTmAo

	To claim this, I am signing this object:

	<!DOCTYPE html>
	<html>

	<head>
	<meta name="description" content="mocha/chai">
	<meta charset="utf-8">
	<title>TDD Workbench</title>
	<link rel="stylesheet" href="//cdnjs.cloudflare.com/ajax/libs/mocha/3.0.0-2/mocha.css">
	<script src="//cdnjs.cloudflare.com/ajax/libs/mocha/3.0.0-2/mocha.js"></script>
	<script src="//cdnjs.cloudflare.com/ajax/libs/chai/3.5.0/chai.js"></script>

	Feature: Example

	Can we bypass step definitions and use a single test
	fixture instead? Yes we can!

	Scenario: Spike

	Now I can explain my scenario and examples
	outside of the somewhat restrictive GWT-type
	language.