gdd

Load relevant GDD nodes for Roastr.ai issue assessment and planning.

Updated Aug 2, 2025
One-click install
npx skills add https://github.com/Eibon7/roastr-ai --skill gdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdd
Source: https://github.com/Eibon7/roastr-ai/tree/main/.claude/skills/gdd
Command: npx skills add https://github.com/Eibon7/roastr-ai --skill gdd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Roastr.ai often confronts massive specifications when handling issues. This Skill loads just the essential GDD context required for assessment, node resolution, and pattern awareness, dramatically reducing cognitive load and token usage.

Core Features & Use Cases

  • Fragmented context loading: Breaks spec.md into specialized nodes and loads only the relevant subset.
  • Bidirectional synchronization: Keeps nodes synchronized with the spec.md to prevent drift.
  • Context size reduction: Decreases loaded context to a targeted sub-set (often under 15k tokens) per issue.
  • Issue-centric planning: Prepares a concise, loaded context for FASE 0 assessment, pattern mapping, and dependency resolution.

Quick Start

To begin, provide an issue number. The Skill will fetch issue metadata, map it to GDD nodes, resolve dependencies, load the necessary nodes, and present a structured context ready for FASE 0 planning.

Frequently Asked Questions about gdd

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

FAQPage Schema
How do I load only the minimal context needed to resolve a GitHub issue in a large specification?

Graph-driven development (GDD) context loading fetches only the relevant nodes from your specification that relate to an issue, reducing cognitive load and token usage from massive specs down to targeted subsets—often under 15k tokens per issue.

What is graph-driven development and how does node mapping help with issue assessment?

GDD breaks specifications into interconnected nodes and maps issue labels to those nodes, enabling dependency resolution and pattern awareness. This approach automates node identification, performs FASE 0 assessment, and prepares structured context for planning without loading irrelevant sections.

Can I keep my specification synchronized with fragmented GDD nodes?

Yes, bidirectional synchronization prevents drift between spec.md and individual GDD nodes, ensuring that updates in one location automatically reflect in the other while you load only the minimal subset needed for each issue.

How do I start resolving an issue using node resolution and context loading?

Provide an issue number; the Skill fetches issue metadata, maps it to GDD nodes via label matching, resolves node dependencies, loads necessary documentation, and delivers a concise, structured context ready for FASE 0 planning and assessment.

What problems does minimalist context loading solve for large project specifications?

Fragmented context loading eliminates overwhelming cognitive load by delivering only essential nodes per issue, drastically reduces token usage during processing, and accelerates issue assessment and planning artifact generation for complex specifications.