dev-dispatch

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.

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.

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.

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.

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.

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.