freedom-winds/talqor

grammar-change-impact

Assess the impact of a proposed Talqor syntax or grammar change before implementation. Use for new syntax, operators, precedence shifts, keyword additions, AST shape changes, or parser recovery changes.

ir-runtime-design

Design or refactor Talqor IR, lowering, runtime services, ABI, and backend boundaries with explicit invariants, migration costs, and extension strategy.

language-conformance-review

Review a Talqor change for spec conformance, hidden breakage, missing tests, diagnostic quality, and docs or tooling drift.

parser-ast-implementation

Implement or refactor the Talqor lexer, parser, and AST from the approved grammar while preserving spans, diagnostics, and regression coverage.

stdlib-api-design

Design Talqor standard-library or module APIs with a minimal v1 surface that avoids premature runtime, ABI, or type-system lock-in.

tooling-release-pipeline

Build and harden Talqor CLI, formatter, LSP, syntax tooling, CI, benchmarks, packaging, and release automation without diverging from the language spec.

type-system-implementation

Implement Talqor name resolution, symbol tables, type checking, generics / inference behavior, and semantic diagnostics from the approved semantics.

v1-cut-planner

Separate must-have Talqor v1 work from later extensions. Use when a feature could force irreversible parser, type-system, runtime, ABI, module-system, or tooling choices.