Agile and Lean software development methodologies for iterative, adaptive project execution. Covers Scrum (roles, ceremonies, artifacts), Kanban (WIP limits, flow metrics), XP (TDD, pair programming, CI), SAFe overview, Lean Software Development (Poppendieck's 7 principles), user stories (INVEST criteria), estimation via story points and velocity, and the Agile Manifesto's values and principles. Includes Cynefin framework for methodology selection and GSD's relationship to Agile as a structured Lean variant.

A postmortem is the work product that converts an incident from a surprise into learning. A *blameless* postmortem does this without punishing the people closest to the incident — not because punishme

Fact-checking and source verification workflow for research documents. Launches parallel fact-checkers, aggregates findings, applies corrections systematically.

Design heuristics for three-dimensional interaction — input modalities (6DoF controllers, gaze, gesture, voice), selection and manipulation techniques (ray-cast, virtual hand, go-go, world-in-miniature), navigation (teleport, continuous, redirected walking), and feedback loops (haptic, audio, visual). Covers Fitts' law in 3D, discoverability vs affordance, safe-zone design, and comfort/simulator sickness mitigation. Use when designing VR/AR interactions, immersive walkthroughs, or any input system where the user's body is the controller.

Augmented reality succeeds or fails on registration — the precise alignment of virtual content with the physical world. A perfectly rendered virtual object floating six inches from where it should be

Philosophical theology — the use of philosophical tools to analyze and evaluate theological claims. Covers classical arguments for and against the existence of God (cosmological, ontological, teleological, moral, evil), the divine attributes (simplicity, omniscience, omnipotence, eternity, impassibility), the relation of faith and reason, religious epistemology, and the boundary between natural theology and revealed theology. Use when a query asks whether a theological claim is rationally defensible, how a divine attribute should be understood, or how philosophical frameworks across traditions have engaged religious questions.

Apprenticeship pedagogy for the trades — how craft is actually taught, which is almost nothing like how classroom subjects are taught. Covers the observe/practice/correct loop, the role of the master as model rather than lecturer, the ladder from sweeping the shop to working on real jobs, the honest handling of failure, and the modern adaptations of apprenticeship for contexts where a traditional master-apprentice relationship is not available. Use when designing a training program, diagnosing why a trainee is stuck, or understanding why textbook learning falls short in craft domains.

Tools and machines as the leverage-amplification layer of the trades — how hand tools, powered tools, and programmable machines differ in what they amplify, what they constrain, and what skill they demand. Covers the tool-to-machine progression, the Nasmyth steam-hammer lineage of precision power, the block-making machinery at Portsmouth as the first mass-production machine shop, and the modern CNC/robotics layer. Use when selecting tools for a job, justifying a tool purchase, or teaching a learner why tools are organized the way they are.

Thinking frameworks for decisions and problem analysis. Use when evaluating options, root causes, or prioritizing.

Composes three-part DACP bundles from skill library artifacts. Determines fidelity level, queries catalog, and records assembly rationale.

Deterministic git operations with state verification for skill-creator managed repos. Use when managing repos, branches, worktrees, or contribution workflows.

Complex systems and emergent behavior — chaos theory, fractals, neural networks, cellular automata, and computability. Analyzes dynamical systems for chaos via Lyapunov exponents, classifies bifurcations, measures fractal dimension, and models emergent phenomena. Use when analyzing chaotic systems, computing Lyapunov exponents, classifying bifurcations, measuring fractal dimension, modeling neural networks, or studying emergent behavior from simple rules.

Foundational measurements and relationships. The axioms of the system — numbers, distance, angles, and the geometry of seeing.

Periodic phenomena and frequency analysis. How repetition creates structure — from simple oscillation to Fourier decomposition.

Passive Sensing, Threat Assessment, and Coordinated Signaling for Agent Systems.

Use trace-mcp apply_codemod for any bulk mechanical change instead of repeated Edit calls. Activate whenever the same edit pattern would be applied 2+ times, across one file or many.

Simplify code while preserving behavior, public contracts, and side effects. Favor explicit code and local clarity over clever or compressed constructs.

Create atomic commits by staging the right files, analyzing the staged diff, composing a conventional commit message, and optionally pushing.

This skill should be run only when the user explicitly invokes it. Orchestrates end-to-end task implementation — understands the task, assesses complexity, implements directly or via a team of subagents for complex work, and always finishes with a code-polish pass.

**Company:** Series B Healthcare SaaS (80 people)

**Company context:** Series B healthcare SaaS, ~80 employees

This is an in-product profiling survey designed to run during a new user's first session. It routes signups to the correct onboarding path and flags whether the account is a potential buyer or a non-c

A product leader trapped in back-to-back meetings faces a compounding problem: every meeting demands decisions, and every decision depletes a finite cognitive resource. The result is decision fatigue

**Organization:** B2B Analytics SaaS

**Prepared for:** Mid-level PM (3 years experience) at a 500-person enterprise SaaS company

**Title:** Q1 All-Hands: What We Shipped, What's Next, and Where We Need Help

**Prepared for:** Director of Product, 200-person fintech startup

- **Date type:** Fixed external deadline

Design employee onboarding (first 90 days + trajectory). See also: user-onboarding (product UX onboarding).

**Role:** Product Lead (IC/people-manager hybrid typical of product leadership)

Create a Pricing Strategy Pack (value metric, packaging, price points, conversion mechanics, rollout).

Prioritize product roadmap: scoring model, ranked opportunities, decision narrative. See also: technical-roadmaps (engineering roadmap).

- **Product:** Team collaboration SaaS

- **Product**: Team collaboration SaaS

**Decision statement (one sentence):**

**Prepared for:** New Product Lead, 5 direct reports (3 PMs, 1 Designer, 1 Data Analyst)

**Team:** Product Team (10 people, remote-first)

Since the user did not provide answers to intake questions, the following explicit assumptions are made. Open questions that could change the ship decision are listed in Section 8.

**Feature:** Role-Based Access Control (RBAC) for Admin Users

Align stakeholders and secure buy-in: stakeholder map, pre-brief plan, decision summary.

**Founders:** 2 co-founders (ex-ops managers in logistics + PM from warehouse software)

Decide whether/how to pivot: diagnosis, exhaustion check, pivot options, validation plan.

**Company:** AI Support Copilot (E-commerce)

**Date:** March 2026

Apply systems thinking: feedback loops, second-order effects, leverage points, intervention plan.

**Remote Cross-Functional Team: Reduce Chaos, Increase Decision Velocity**

**Context:** 12-person remote team (PM, Design, Engineering, Data) seeking to reduce chaos and increase decision velocity.

Design product user onboarding to drive activation: aha moment, first-mile plan, experiment backlog. See also: onboarding-new-hires (employee).

Create an Amazon-style PR/FAQ plus a backcasting launch plan.

Draft and edit written artifacts (email, memo, doc) with a quality gate.