dev-dispatch

Name: dev-dispatch
Availability: InStock
Author: graphrefly

Implement GraphReFly TypeScript or Python features with spec-aligned plans and approval gates.

1|Updated Mar 29, 2026

Search Tags:#typescript #python #cross-language #feature-implementation #spec-alignment #graphrefly #test-parity

Ready to run

npx skills add https://github.com/graphrefly/graphrefly-ts --skill dev-dispatch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-dispatch
Source: https://github.com/graphrefly/graphrefly-ts/tree/main/.gemini/skills/dev-dispatch
Command: npx skills add https://github.com/graphrefly/graphrefly-ts --skill dev-dispatch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dev-dispatch turns ambiguous “implement this” requests into a spec-aligned plan and a guarded implementation path for GraphReFly across TypeScript and Python.

Core Features & Use Cases

Spec-first delivery: Reads the GraphReFly spec as the source of truth and aligns architecture and behavior before coding.
Two-phase workflow with approval gate: Produces a concrete plan in Phase 2 and halts for user approval before Phase 3 implementation.
Cross-language parity mindset: Supports changes targeting graphrefly-ts and graphrefly-py and calls for a post-implementation parity check.
Repo-pattern adherence: Locates and mirrors the closest existing implementation pattern to reduce drift and ensure consistency.
Hard API/behavior guardrails: Enforces constraints like no async in public APIs, nanoseconds time handling, and required message tuple formats.
Verification-focused completion: Runs TS and PY test suites and validates spec invariants before reporting done.

Quick Start

Ask the assistant to dispatch your change request by saying “dev-dispatch: implement <your feature/fix>” and wait for the plan approval before any code is written.

Frequently Asked Questions about dev-dispatch

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

FAQPage Schema

How do I implement cross-language feature parity between TypeScript and Python?▼

To implement TypeScript and Python feature parity, this Skill uses a spec-first workflow that mirrors existing repo patterns and runs test suites in both languages to verify behavioral alignment before completion.

What's the best way to align new GraphReFly operators with the official spec?▼

Aligning new GraphReFly operators requires a two-phase architecture discussion that reads the spec as the source of truth, followed by a mandatory approval halt to verify design compliance before writing any code.

How do I plan a cross-language protocol change without breaking existing API constraints?▼

Planning a protocol change safely involves enforcing hard guardrails like no async in public APIs and nanosecond time handling, ensuring the new implementation adheres to GraphReFly constraints throughout the process.

Why does my GraphReFly implementation fail the cross-language parity check?▼

Cross-language parity checks fail when implementations drift from the spec or existing repo patterns; ensuring message tuple formats match and running TS and PY test suites validates spec invariants to resolve discrepancies.

Can I use this to implement topology changes across graphrefly-ts and graphrefly-py simultaneously?▼

Yes, you can implement topology changes across graphrefly-ts and graphrefly-py by supplying a task request, which generates a deterministic plan and executes post-implementation parity verification for both codebases.

When do I need to halt for approval during a feature implementation workflow?▼

You must halt for approval after Phase 2 produces a concrete implementation plan, ensuring the spec-aligned architecture is reviewed and authorized before any Phase 3 coding or test execution begins.