arukellt

Use when an assigned selfhost-retirement, bootstrap-governance, or source-of-truth-transition slice needs implementation with verification. Triggers: parity-exit criteria definition, bootstrap verification gate changes, source-of-truth transition rules, retirement sequencing for dual-managed compiler surfaces.

Use when a specific selfhost or compiler-core implementation work order needs completion with strict scope discipline. Trigger phrases: - 'Complete this selfhost issue slice' - 'Implement this resolver work' - 'Work on this typechecker task' - 'Finish this bootstrap verification' - 'Implement this acceptance criterion for selfhost' Examples: user provides ISSUE_ID=#309, SUBTASK='module import resolution', PRIMARY_PATHS=['src/compiler/resolver.ark'] → implement exactly that slice with regression tests. User says 'Complete the typechecker inference work in #311, fixtures in tests/fixtures/infer/' → implement only that scope. After defining a work order with ISSUE_ID, SUBTASK, PRIMARY_PATHS, REQUIRED_VERIFICATION, and DONE_WHEN → execute precisely that scope with no scope creep.

Use when a stdlib implementation work order needs completion with precision and closure. Trigger conditions: - User is assigned a stdlib API/runtime implementation work order with ISSUE_ID, SUBTASK, PRIMARY_PATHS - Manifest-driven stdlib behavior needs implementation - Stdlib docs generator contracts or consistency checks need work - Source-backed recipe/example linking in stdlib needs implementation Do NOT use for selfhost work, playground samples, or language-docs unless explicitly part of the assigned stdlib slice.

Use when you have a specific, scoped acceptance slice to complete within an issue and need ruthless scope discipline. Trigger phrases: - 'Complete this acceptance slice' - 'Implement only this specific part' - 'Work on this acceptance criterion' - 'Finish this slice without scope creep' Examples: user provides ISSUE_ID, SUBTASK with PRIMARY_PATHS, REQUIRED_VERIFICATION, and DONE_WHEN conditions → implement exactly that slice. User says 'Complete only the JSON serialization part, not the entire refactor' → focus on that single slice. After defining acceptance criteria with specific paths and verification, user says 'Now implement this' → execute precisely that scope.

Use when working in the Arukellt repository before implementing or reviewing changes. Triggers: need to find source-of-truth files, understand the verification contract, read large markdown files, or regenerate generated docs and issue indexes.

Use when designing and specifying language features, syntax decisions, and language design contracts. Triggers: need an ADR for a new language feature, need to resolve syntax ambiguity, conflicting design requirements need resolution before implementation can proceed, acceptance criteria need definition for language-level behavior.

Use when a selfhost MIR or compiler-core design slice needs an ADR, decision record, or contract clarification before implementation can safely proceed. Triggers: MIR representation ambiguity, SSA contract questions, design decisions blocking compiler implementation.

Use when an assigned stdlib modernization, audit, inventory, or migration-plan slice has explicit completion criteria and no product implementation in scope. Triggers: stdlib API audit needed, migration sequencing required, policy clarification before stdlib implementation, follow-up-ready design artifacts needed.

Use when an assigned benchmark suite, perf gate, or cross-language comparison script slice needs implementation with explicit verification and completion criteria. Triggers: benchmark harness creation, threshold gate definition, performance measurement infrastructure, CI perf gate changes.

Use when an assigned CLI, command-surface, or machine-readable-output implementation slice needs execution with verification. Triggers: new subcommands, flag/option UX changes, --json output, stdout/stderr contract fixes, CLI snapshot tests, help text changes.

Use when an assigned compiler-core, MIR, emitter, or validation implementation slice needs execution with explicit verification. Triggers: lowering fixes, type-table changes, backend emission changes, MIR validation strengthening, regression fixtures for compiler behavior, backend optimization passes.

Use when an assigned component-model, component-composition, or WIT-integration slice needs implementation with verification. Triggers: WIT parsing changes, component wrapper/emission, composition paths, canonical ABI support, component-focused regression fixtures, WIT contract documentation.

Use when an assigned editor-run, editor-debug, or launch-integration slice needs implementation with verification. Triggers: run command flow in editor, debug launch flow, launch configuration wiring, execution output surfacing in IDE, editor-side run/debug regression tests.

Use when an assigned language-reference, tutorial, or spec-sync documentation slice needs implementation with verification. Triggers: language reference page updates, spec-sync with current behavior, tutorial/example maintenance, sample code validation, docs consistency checks.

Use when an assigned playground work order needs implementation. Triggers: wasm packaging for browser, browser runtime entrypoint, playground editor shell, examples/share UX, docs-site integration, deploy/publish proof, playground governance/audit, ADR/scope decisions for playground. Do NOT use for selfhost or stdlib-only work.

Use when an assigned runtime, capability, or target-gating implementation slice needs execution with verification. Triggers: host-function wiring, target compatibility diagnostics, capability grant/deny enforcement, runtime fixture updates, capability-surface documentation changes.

Use when an assigned LSP, VS Code extension, or editor-behavior implementation slice needs execution with verification. Triggers: LSP request/response changes (definition, hover, diagnostics, references, CodeLens), extension command wiring, diagnostics parity between CLI and IDE, editor regression snapshots.

Use when reviewing Arukellt implementation changes for scope compliance, correctness, and gate discipline before issue closure. Triggers: implementation slice needs close review before issues/open to issues/done moves, completion report needs cross-check against actual diffs, policy violation detection needed (SKIP abuse, scope creep, false-done patterns). Independent from verify-agent (which runs tests) — analyzes diffs and reports for policy violations.

Use when verification tasks are needed: implementation completeness checks, parity checks, close-gate verification, issue closure, and queue hygiene. Triggers: need to confirm upstream done status, validate evidence files, move issues from issues/open to issues/done, regenerate queue indexes, run close-gate verification.