resolve

Name: resolve
Availability: InStock
Author: tesserine

Diagnose operational obstacles and implement permanent structural fixes before resuming tasks.

Updated Mar 3, 2026

Search Tags:#workflow #debugging #config #infrastructure #resolve #friction

Ready to run

npx skills add https://github.com/tesserine/groundwork --skill resolve-tesserine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve
Source: https://github.com/tesserine/groundwork/tree/main/skills/resolve
Command: npx skills add https://github.com/tesserine/groundwork --skill resolve-tesserine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Friction in the operational environment blocks progress when essential tools, configurations, or conventions are missing or misaligned. This skill guides the agent to stop, diagnose the obstacle, and implement a permanent structural fix so the task can resume with a clearer path forward.

Core Features & Use Cases

Stop momentum when an obstacle is detected and avoid cascading workarounds.
Ground the context by identifying the obstacle category and the simplest structural fix.
Implement the fix (install tools, update configs, adjust conventions) and verify it before returning to the task.

Quick Start

Identify the friction in the current task and apply an inline structural fix to resume progress.

Frequently Asked Questions about resolve

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

FAQPage Schema

How do I permanently fix broken workflow configurations that block progress?▼

To fix broken workflow configurations, identify the specific obstacle category, implement a structural fix by updating the config or installing missing tools, verify the change, and resume the original task with the improved environment.

What is the best way to resolve operational friction in a software development environment?▼

Resolving operational friction involves stopping momentum when an obstacle is detected, objectively grounding the context, executing a permanent structural fix, and validating it before returning to the original task to prevent cascading workarounds.

How do I stop undocumented infrastructure requirements from causing debugging friction?▼

Stop debugging friction from undocumented requirements by grounding the obstacle, implementing a structural fix to document or adjust the infrastructure convention, and verifying the environment is improved for future sessions.

When should I pause my current task to apply a structural fix to my infrastructure?▼

You should pause to apply a structural fix immediately when an obstacle is detected, preventing cascading workarounds and ensuring the environment is permanently improved before continuing with the original task.

Can I use this approach to fix missing development tools during project execution?▼

Yes, you can fix missing development tools by stopping the current execution stage, installing the required tools, validating the installation, and returning to the task with the operational environment permanently improved.