Skip to main content

rp-why

Load when reflecting on AI collaboration quality or tracking growth over time. Analyzes session history to surface how deeply you think with AI tools and whether your orchestration sophistication matches your cognitive depth. Provides actionable nudges to push toward more strategic work.

Source facts

Repository
block/agent-skills
Last source activity
June 25, 2026 at 09:05
Detected SKILL.md language
English
Stars
25
Forks
50

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
14 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
rp-why
description
Load when reflecting on AI collaboration quality or tracking growth over time. Analyzes session history to surface how deeply you think with AI tools and whether your orchestration sophistication matches your cognitive depth. Provides actionable nudges to push toward more strategic work.
author
dakotafabro
version
4.0
tags
["reflection","growth","ai-collaboration","self-assessment","productivity","learning","three-dimensions"]
# rp-why: Three Dimensions of AI Collaboration ## Overview The **rp-why** skill is a self-reflection framework that helps AI practitioners measure and improve their collaboration practice. It tracks three dimensions: - **DOK (Depth of Knowledge)** - Cognitive complexity of human prompts, scored 1.0-4.0 using Webb's framework. "Adjusted" accounts for compression of intent. - **TM (Tool Maturity)** - Intentional orchestration of AI tools, tracked through the Orchestra Model (Tiers 1-6). - **ADT (Agentic Delegation Trust)** - The relationship between tool sophistication and cognitive depth. Derived from the TM x DOK matrix. The intersection of these dimensions produces **diagnostic zones** that reveal the health of the collaboration practice. --- ## How to Use This Skill ### Installation ```bash npx skills add https://github.com/block/agent-skills --skill rp-why ``` ### Available Commands | Command | What It Does | |---------|--------------| | `/rp-why init` | Generate a baseline from your session history | | `/rp-why baseline` | Same as init | | `/rp-why current` | Analyze the current session | | `/rp-why compare` | Compare current session to your baseline | | `/rp-why overall` | Full longitudinal analysis across all sessions | | `/rp-why token-spend` | Daily token spend breakdown across all sessions | ### Alternative: Natural Language You can also ask naturally: ``` You: Analyze my AI collaboration patterns You: What's my DOK distribution for this session? You: How does this session compare to my baseline? You: Give me the full rp-why longitudinal report ``` ### When to Use - **First time**: Run `/rp-why init` (or `/rp-why baseline`) to establish your starting point - **End of session**: Run `/rp-why current` to reflect on your work - **Weekly**: Run `/rp-why compare` to track progress against baseline - **Monthly**: Run `/rp-why overall` for the full growth picture --- ## The Three Dimensions ### Dimension 1: DOK (Depth of Knowledge) Measures the cognitive complexity of human prompts. Scored 1.0-4.0 using Webb's Depth of Knowledge framework. | Level | Name | Description | Prompt Indicators | |-------|------|-------------|-------------------| | 1 | Recall & Reproduction | Simple factual prompts | "What is X?" "Show me the syntax for Y" | | 2 | Application of Skills & Concepts | Applying learned skills to solve a problem | "Build this component" "Fix this error using pattern X" | | 3 | Strategic Thinking | Reasoning across multiple concepts to plan, analyze, or design | "Design a system..." "Analyze trade-offs..." "What if..." | | 4 | Extended Thinking | Creating something entirely new - frameworks, cross-disciplinary synthesis | "Research and synthesize..." "Create a framework..." | **Adjusted DOK** accounts for compression of intent - when short prompts carry complex meaning due to established context. A compressed "proceed" that triggers a multi-step architectural deployment is not DOK 1. **DOK 3+4 %** is the primary growth signal. It measures what proportion of your work operates at strategic or extended thinking levels. **Compression %** tracks how often short directives carry complex intent. Compression emerges as trust deepens between practitioner and agent. ### Dimension 2: TM (Tool Maturity) - Orchestra Model Measures intentional orchestration - how deliberately you coordinate AI tools, agents, and workflows. Only counts actions the user deliberately initiated. | Tier | Name | Description | |------|------|-------------| | 1 | Solo | Human works alone. AI reviews after. | | 2 | Duet | Back-and-forth conversation. Human prompts, AI responds, human edits. | | 3 | Ensemble | Human provides meaningful body of work. Evaluates holistically. | | 4 | Chamber | Human delegates work streams. Sub-agents introduced. Orchestration required. | | 5 | Symphony | Multiple AI interactions coordinated toward unified goal. Minimal intervention. | | 6 | Virtuoso | Flow state. Human and AI synthesized. Optimal DOK, ADT, and TM. | ### Dimension 3: ADT (Agentic Delegation Trust) - Diagnostic Zones Measures the gap between Tool Complexity and Human Cognitive Depth. The TM x DOK matrix produces six zones: | Zone | Description | Signal | |------|-------------|--------| | **Frontier** | TM and DOK matched and growing together | Operating at the productive edge | | **Growing** | Approaching a match between tool sophistication and cognitive depth | Building toward effective use | | **Expected** | Tool usage and cognitive depth appropriate for current level | Healthy starting position | | **Thinking Ahead** | Cognitive depth exceeds tool sophistication | Opportunity to adopt more powerful orchestration | | **Underutilizing** | Tool sophistication exceeds cognitive depth | Opportunity to deepen the questions being asked | | **Overpowered** | Significant mismatch between tool complexity and task depth | Resources spent without proportional cognitive return | --- ## Diagnostic Zone Matrix ``` DOK 1 DOK 2 DOK 3 DOK 4 (Recall) (Application) (Strategic) (Extended) +-----------+--------------+-------------+-------------+ Tier 5-6 | Overpowered| Underutil- | Frontier | Frontier | (Symphony/ | | izing | | | Virtuoso) | | | | | +-----------+--------------+-------------+-------------+ Tier 3-4 | Overpowered| Expected | Growing | Frontier | (Ensemble/ | | | | | Chamber) | | | | | +-----------+--------------+-------------+-------------+ Tier 1-2 | Expected | Growing | Thinking | Thinking | (Solo/ | | | Ahead | Ahead | Duet) | | | | | +-----------+--------------+-------------+-------------+ ``` --- ## Report Formats ### `/rp-why init` or `/rp-why baseline` Establishes the starting point. Analyzes all available session history. **Report structure:** ``` +==================================================================+ | rp-why . BASELINE | +==================================================================+ DATA SUMMARY -------------------------------------------------------------------- Period: [start] - [end] ([N] days) Sessions: [N] Prompts: [N] classified THREE DIMENSIONS -------------------------------------------------------------------- DOK (Depth of Knowledge) [score] TM (Tool Maturity) Tier [N] . [Name] ADT (Delegation Trust) [Zone] DIAGNOSTIC ZONE: [Zone Name] -------------------------------------------------------------------- [Zone description from the six-zone model] DOK DISTRIBUTION -------------------------------------------------------------------- DOK 1 (Recall): [bar] [%] DOK 2 (Application): [bar] [%] DOK 3 (Strategic): [bar] [%] DOK 4 (Extended): [bar] [%] DOK 3+4: [%] Compression: [%] GROWTH TARGETS -------------------------------------------------------------------- DOK 3+4 target: [%] Compression target: [%] Next TM tier: Tier [N] . [Name] ([what it means]) -------------------------------------------------------------------- Baseline saved to: ~/.config/goose/rp-why-baseline.json Run /rp-why current after sessions to track progress. ``` ### `/rp-why current` Analyzes the active session. The quick-check mirror. **Report structure:** ``` +==================================================================+ | rp-why . CURRENT SESSION | +==================================================================+ SESSION SNAPSHOT -------------------------------------------------------------------- Date: [date] Conversations: [N] Prompts: [N] classified THREE DIMENSIONS
View on GitHub
This SKILL.md is very large, so SkillsMP previews the first section here. View on GitHub