skills.rest
RobinNorberg
RobinNorbergCOMMUNITY
Explore all skills by this author →
GitHub

deep-dive

Orchestrate a 3-lane trace and interactive interview to crystallize requirements.

5|Updated Mar 16, 2026
Search Tags:#automation#requirements#orchestration#interview#trace#spec#deep-dive
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill deep-dive-robinnorberg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-dive
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/deep-dive
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill deep-dive-robinnorberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Deep Dive skill coordinates a 3-lane trace and an interactive interview to crystallize requirements before committing to a solution, reducing ambiguity and rework.

Core Features & Use Cases

  • Three parallel trace lanes to surface root causes across code, configuration, and measurement domains.
  • 3-point injection into the interview that seeds the initial questions from observed gaps and critical unknowns.
  • Execution bridge integration to hand off a well-scoped spec to downstream planners and autopilot pipelines.
  • Ideal for brownfield and greenfield problems where requirements are unclear or evolving.

Quick Start

Invoke /deep-dive with your initial problem statement to start the orchestration.

Frequently Asked Questions about deep-dive

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I crystallize requirements before starting complex software execution?▼

To crystallize requirements before execution, you can orchestrate a 3-lane trace and an interactive interview. This process surfaces root causes across code, configuration, and measurement domains to reduce ambiguity and rework.

What is the best way to explore root causes in brownfield projects with unclear requirements?▼

Exploring root causes in brownfield projects with unclear requirements is best handled by running parallel trace lanes across code, configuration, and measurement. This surfaces critical unknowns before seeding an interactive interview to formalize specs.

How does a trace-based injection model work for requirements gathering?▼

A trace-based injection model works by analyzing three parallel trace lanes for gaps, then injecting those three points into an interactive interview. This seeds initial questions from observed gaps to safely guide requirements crystallization.

Can I hand off formal specs to downstream planners after a requirements interview?▼

Yes, you can hand off formal specs to downstream planners after a requirements interview using an execution bridge. This integration passes the well-scoped specification directly into downstream execution pipelines.

Do I need oh-my-copilot components to orchestrate a deep-dive trace?▼

Yes, orchestrating a deep-dive trace requires integration with oh-my-copilot components. You need trace lanes, the deep-interview prompt, and execution bridges to enforce the trace-based injection model and preserve safety.

Related Skills

Explore More Software Engineering Skills→
dropsyoondropsyoon

deep-dive

Trace root causes across three parallel lanes and crystallize evidence-grounded requirements.

Community
Advanced
ImL1sImL1s
6

deep-interview

Clarify vague product ideas into actionable requirements through Socratic questioning.

Community
Advanced
yjzhang2003yjzhang2003
26

gateway-guide

Manage oh-my-feishu gateway services and trigger repair workflows.

Community
Intermediate
ImL1sImL1s
6

deep-dive

Coordinate trace-driven investigation and structured interviews to crystallize requirements into actionable specs.

Community
Advanced