gpd-quick

Execute small ad-hoc research tasks with atomic commits and state tracking.

1|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-quick-chargrnmn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpd-quick
Source: https://github.com/CharGrnmn/roomtemp-superconductor-gpd/tree/main/.agents/skills/gpd-quick
Command: npx skills add https://github.com/CharGrnmn/roomtemp-superconductor-gpd --skill gpd-quick-chargrnmn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gpd-planner, gpd-executor, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the execution of small, ad-hoc research tasks with GPD guarantees, allowing for atomic commits and state tracking without the overhead of optional agents.

Core Features & Use Cases

  • Atomic Execution: Ensures atomic commits and state tracking for small tasks.
  • Skipping Optional Agents: Allows for rapid execution by omitting research, plan-checker, and verifier agents.
  • Quick Mode Directory: Tasks are executed in .gpd/quick/, separate from planned phases.
  • Task Tracking: Updates the "Quick Tasks Completed" table in STATE.md.

Quick Start

Execute a quick task by running gpd-quick "My task description".

Frequently Asked Questions about gpd-quick

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

FAQPage Schema
How do I execute quick physics research tasks without running the full planning pipeline?

You can execute ad-hoc research tasks rapidly by running a single command, which skips optional agents like the plan-checker and verifier to deliver fast atomic commits and state tracking for quick physics calculations and lookups.

What is the best way to track state for ad-hoc research calculations in a GPD runtime?

State tracking for ad-hoc research calculations in a GPD runtime is handled by atomic execution, which records commits and updates a Quick Tasks Completed table within the STATE.md file.

Do I need gpd-planner and gpd-executor to run rapid research task lookups?

Running rapid research task lookups requires gpd-planner and gpd-executor as dependencies, alongside a compatible GPD runtime environment to properly support the execution of these quick tasks.

Can I use quick task execution for small physics checks without affecting planned research phases?

You can run small physics checks without affecting planned phases because quick tasks execute in a separate .gpd/quick/ directory, keeping them fully isolated from your main research workflow.

Why does skipping optional agents speed up research task execution, and what are the limitations?

Skipping optional agents like the research, plan-checker, and verifier speeds up execution by removing validation overhead, but means these quick tasks lack the deeper verification and planning guarantees of the full pipeline.