gpd-tangent

Manage research workflow tangents with stay, check, defer, or branch options.

Updated May 1, 2026
One-click install
npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-tangent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-tangent
Source: https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry/tree/main/.agents/skills/gpd-tangent
Command: npx skills add https://github.com/Unified-Field-Theory-Research/finite-capacity-causal-geometry --skill gpd-tangent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a structured approach for researchers to manage tangents in their workflows, ensuring that potential side investigations are considered without silently widening scope.

Core Features & Use Cases

  • Tangent Management: Decide the fate of tangents, such as whether to stay on the main path, perform a quick check, defer as a todo, or open a hypothesis branch.
  • Contextual Decision Making: Offers guidance based on the current research mode and project context.
  • Rust-Native Execution: Built for Rust-only repositories, leveraging the Get Physics Done (GPD) framework.

Quick Start

Use the gpd-tangent skill to handle an unexpected tangent: gpd-tangent "Consider the implications of this new observation."

Frequently Asked Questions about gpd-tangent

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

FAQPage Schema
How do I manage research tangents without losing scope in my workflow?

Tangent management decision support evaluates side investigations by offering options to stay on the main path, run quick checks, defer items as todos, or open hypothesis branches, preventing silently widened project scope.

Can I use this tangent management tool with my Rust-based research project?

Yes, tangent management is built for Rust-only repositories leveraging the Get Physics Done framework, requiring project-aware context to provide guidance based on current research mode.

What is the best way to handle an unexpected tangent during a research workflow?

Handle unexpected tangents by evaluating four structured options: stay on the main path, perform a quick check, defer the tangent as a todo, or open a dedicated hypothesis branch for deeper investigation.

Does this decision support skill require specific project context to work?

Yes, tangent decision support requires project-aware context to function correctly, using current research mode and project context to offer relevant guidance for deciding tangent fate.

When should I open a hypothesis branch instead of deferring a tangent as a todo?

Open a hypothesis branch when a tangent warrants deeper investigation, whereas deferring as a todo is best for side observations addressed later without immediately widening research scope.