Understand any codebase instantly. System intelligence for codebases, built for humans and AI.
TypeScript aiai-memoryclaude-codeclicode-analysiscode-mappingcode-memorycodebase-understandingcodexdeveloper-toolsllmopenclawpersistent-memoryprogram-analysissoftware-architecturesystem-intelligencesystem-mapping
chore: remove skills/ directory (#81)
Tanner Kocher867de4375e23
diff --git a/skills/ix-api-contract-change/SKILL.md b/skills/ix-api-contract-change/SKILL.mddeleted file mode 100644index ecefb9c6..00000000--- a/skills/ix-api-contract-change/SKILL.md+++ /dev/null@@ -1,56 +0,0 @@-----name: ix-api-contract-change-description: Use when adding or changing memory-layer routes or ix-cli client methods so API contracts stay aligned across Scala routes, models, and TypeScript IxClient calls.------# Ix API Contract Change--Use this when touching:-- `memory-layer/src/main/scala/ix/memory/api/*Routes.scala`-- `memory-layer/src/main/scala/ix/memory/model/*`-- `ix-cli/src/client/api.ts`--## Workflow--1. Map blast radius:-```bash-ix impact IxClient --format json-ix search Routes --kind class --format json --limit 30-```--2. Inspect changed route surface:-```bash-ix overview <RouteClassName> --format json-ix read <absolute/path/to/RouteFile.scala:1-220> --format json-```--3. Align client boundary:-```bash-ix overview IxClient --format json-ix read <absolute/path/to/ix-cli/src/client/api.ts:1-260> --format json-```--4. Check for shared request/response model impact:-```bash-ix search <ModelName> --kind class --format json --limit 20-ix impact <ModelName> --format json-```--5. Validate expected tests were considered:-```bash-ix search RoutesSpec --kind class --format json --include-tests --limit 20-```--## Contract Checklist--- Route path and HTTP verb match client usage.-- Request fields, optionality, and defaults are consistent.-- Response shape and error behavior are consistent.-- New route is wired into aggregate route registration.--## Guardrails--- Treat `IxClient` as a high-risk boundary.-- If you changed a route signature, update caller methods in `IxClient` in the same task.-- Do not leave route/client drift for a follow-up task unless explicitly planned.-diff --git a/skills/ix-api-contract-change/agents/openai.yaml b/skills/ix-api-contract-change/agents/openai.yamldeleted file mode 100644index 4aa140a5..00000000--- a/skills/ix-api-contract-change/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX API Contract Change"- short_description: "Keep Scala routes and IxClient in lockstep"- default_prompt: "Use $ix-api-contract-change to implement this endpoint/client change and verify contract alignment."--policy:- allow_implicit_invocation: truediff --git a/skills/ix-arango-query-change/SKILL.md b/skills/ix-arango-query-change/SKILL.mddeleted file mode 100644index 16103a44..00000000--- a/skills/ix-arango-query-change/SKILL.md+++ /dev/null@@ -1,47 +0,0 @@-----name: ix-arango-query-change-description: Use when modifying Arango-backed query/write behavior so schema, AQL, transaction semantics, and DB-facing tests remain aligned.------# Ix Arango Query Change--Use this when touching:-- `memory-layer/src/main/scala/ix/memory/db/ArangoClient.scala`-- DB query/write APIs and AQL construction-- schema or transaction behavior--## Workflow--1. Inspect DB surface:-```bash-ix overview ArangoClient --format json-ix impact ArangoClient --format json-```--2. Read query/transaction hot paths:-```bash-ix read <absolute/path/to/ArangoClient.scala:1-320> --format json-```--3. Locate nearby DB behavior and specs:-```bash-ix search GraphQueryApiSpec --kind class --format json --include-tests --limit 20-ix search GraphWriteApiSpec --kind class --format json --include-tests --limit 20-ix search SearchAqlSpec --kind class --format json --include-tests --limit 20-ix search ArangoClientSpec --kind class --format json --include-tests --limit 20-```--## DB Checklist--- Query semantics match intended node/edge filters.-- Sort/limit/pagination behavior is explicit and stable.-- Transactions remain atomic for multi-step writes.-- Schema bootstrap/ensure behavior is still safe and idempotent.-- Error mapping preserves actionable failure details.--## Guardrails--- Do not change query semantics without corresponding test updates.-- Treat default limits and sort order changes as behavior changes, not refactors.-- Keep API-level callers in sync when return shapes or cardinality change.-diff --git a/skills/ix-arango-query-change/agents/openai.yaml b/skills/ix-arango-query-change/agents/openai.yamldeleted file mode 100644index 6cd29fe2..00000000--- a/skills/ix-arango-query-change/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX Arango Query Change"- short_description: "Control AQL/schema/transaction behavior drift"- default_prompt: "Use $ix-arango-query-change to update Arango query logic and keep DB semantics and tests aligned."--policy:- allow_implicit_invocation: truediff --git a/skills/ix-ingestion-parser-change/SKILL.md b/skills/ix-ingestion-parser-change/SKILL.mddeleted file mode 100644index 9344d320..00000000--- a/skills/ix-ingestion-parser-change/SKILL.md+++ /dev/null@@ -1,58 +0,0 @@-----name: ix-ingestion-parser-change-description: Use when changing ingestion or parser behavior so parser routing, extracted entities/relationships, and graph patch generation stay coherent and testable.------# Ix Ingestion Parser Change--Use this when touching:-- `memory-layer/src/main/scala/ix/memory/ingestion/IngestionService.scala`-- `memory-layer/src/main/scala/ix/memory/ingestion/ParserRouter.scala`-- `memory-layer/src/main/scala/ix/memory/ingestion/parsers/*`-- `memory-layer/src/main/scala/ix/memory/ingestion/GraphPatchBuilder.scala`--## Workflow--1. Confirm impact:-```bash-ix impact IngestionService --format json-ix overview ParserRouter --format json-ix overview GraphPatchBuilder --format json-```--2. Locate parser family and routing points:-```bash-ix search Parser --kind class --format json --limit 30-ix read <absolute/path/to/ParserRouter.scala:1-260> --format json-```--3. Verify parse output contract:-```bash-ix overview ParseResult --format json-ix read <absolute/path/to/ParseResult.scala:1-220> --format json-```--4. Verify graph patch contract:-```bash-ix read <absolute/path/to/GraphPatchBuilder.scala:1-260> --format json-```--5. Validate parser and ingestion tests were considered:-```bash-ix search Spec --kind class --format json --include-tests --limit 60-```--## Change Checklist--- Parser selection logic and file-type routing stay deterministic.-- New extracted entity/relationship kinds are represented consistently.-- IDs/hashes remain stable where expected.-- Import-edge and named-edge resolution still converges on resolvable nodes.-- Graph patch operations still satisfy downstream commit assumptions.--## Guardrails--- Avoid parser-only changes that silently break patch building.-- If parser output shape changes, update parse result consumers in the same task.-- Record intended behavior shifts as an explicit decision via `ix decide`.-diff --git a/skills/ix-ingestion-parser-change/agents/openai.yaml b/skills/ix-ingestion-parser-change/agents/openai.yamldeleted file mode 100644index 1228260b..00000000--- a/skills/ix-ingestion-parser-change/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX Ingestion Parser Change"- short_description: "Guard parser routing and patch generation"- default_prompt: "Use $ix-ingestion-parser-change to make this ingestion/parser update without breaking graph patch behavior."--policy:- allow_implicit_invocation: truediff --git a/skills/ix-map-pipeline-change/SKILL.md b/skills/ix-map-pipeline-change/SKILL.mddeleted file mode 100644index fa455cf8..00000000--- a/skills/ix-map-pipeline-change/SKILL.md+++ /dev/null@@ -1,81 +0,0 @@-----name: ix-map-pipeline-change-description: Use when changing the architectural analysis pipeline — MapService, SmellService, SubsystemScoringService, or their routes/CLI commands — so the map → smells → subsystems chain stays coherent.------# Ix Map Pipeline Change--Use this when touching:-- `memory-layer/src/main/scala/ix/memory/map/MapService.scala`-- `memory-layer/src/main/scala/ix/memory/map/MapGraphBuilderFast.scala`-- `memory-layer/src/main/scala/ix/memory/map/MapPreflight.scala`-- `memory-layer/src/main/scala/ix/memory/map/LouvainClustering.scala`-- `memory-layer/src/main/scala/ix/memory/smell/SmellService.scala`-- `memory-layer/src/main/scala/ix/memory/subsystem/SubsystemScoringService.scala`-- `ix-cli/src/cli/commands/map.ts`-- `ix-cli/src/cli/commands/smells.ts`-- `ix-cli/src/cli/commands/subsystems.ts`--## Pipeline Overview--```-ix map → MapService (Louvain clustering → region hierarchy stored as REGION nodes)-ix smells → SmellService (AQL graph queries → smell claims on File nodes)-ix subsystems → SubsystemScoringService (join regions + smell claims → health scores)-```--Each stage stores versioned claims. Re-running retires old claims before writing new ones.--## Workflow--1. Understand current pipeline state:-```bash-ix briefing --format json-ix overview MapService --format json-ix impact MapService --format json-```--2. Check smell and subsystem dependencies:-```bash-ix overview SmellService --format json-ix overview SubsystemScoringService --format json-ix callers MapService --format json-```--3. Inspect the map types contract (shared across all three stages):-```bash-ix read memory-layer/src/main/scala/ix/memory/map/MapTypes.scala-```--4. After changes, verify all three stages still chain:-```bash-ix map --format json | head -20-ix smells --format json | head -20-ix subsystems --format json | head -20-```--5. Check region/claim data in graph:-```bash-ix stats --format json-ix smells --list --format json-ix subsystems --list --format json-```--6. Record the decision:-```bash-ix decide "<change title>" --rationale "<why>" --affects MapService --format json-```--## Key Invariants--- `MapService` stores results as `REGION` nodes and `CONTAINS_FILE` / `CONTAINS_REGION` edges. SmellService and SubsystemScoringService query these — don't change the node/edge kinds without updating all three.-- Smell claims use field prefix `has_smell.*` and `inference_version=smell_v1`. Subsystem scores use `field=subsystem_health` and `inference_version=subsystem_v1`.-- Both services call `retireOld*()` before storing new claims — this is idempotent by design.-- `SubsystemScoringService(client: ArangoClient, writeApi: GraphWriteApi)` — uses `writeApi` not `queryApi`.-- `SmellService(client: ArangoClient, writeApi: GraphWriteApi)` — uses `writeApi` not `queryApi`.--## Guardrails--- Run `ix map` before `ix smells` or `ix subsystems` — they depend on region data being current.-- If you change region granularity in MapService, SubsystemScoringService scores will shift — document the expected delta as a decision.-- Do not change claim field names (`has_smell.*`, `subsystem_health`) without updating the CLI commands that parse them.diff --git a/skills/ix-new-command/SKILL.md b/skills/ix-new-command/SKILL.mddeleted file mode 100644index 015cd31b..00000000--- a/skills/ix-new-command/SKILL.md+++ /dev/null@@ -1,89 +0,0 @@-----name: ix-new-command-description: Use when adding a new ix CLI command end-to-end — Scala route, IxClient method, CLI command file, oss.ts registration, and doc updates must all stay in sync.------# Ix New Command--Use this when adding a new `ix <command>` from scratch or extending an existing command with a new subcommand.--## Files that must all change together--| Layer | File |-|-------|------|-| Backend route | `memory-layer/src/main/scala/ix/memory/api/<Name>Routes.scala` |-| Route wiring | `memory-layer/src/main/scala/ix/memory/api/Routes.scala` |-| Server wiring | `memory-layer/src/main/scala/ix/memory/Main.scala` |-| TypeScript client | `ix-cli/src/client/api.ts` |-| CLI command | `ix-cli/src/cli/commands/<name>.ts` |-| OSS registration | `ix-cli/src/cli/register/oss.ts` |-| Docs | `CLAUDE.md`, `AGENTS.md` |--## Workflow--1. Understand current command surface:-```bash-ix overview IxClient --format json-ix search Routes --kind class --format json --limit 30-ix impact Routes --format json-```--2. Read existing route and client as pattern references:-```bash-ix read memory-layer/src/main/scala/ix/memory/api/SmellRoutes.scala-ix read ix-cli/src/cli/commands/smells.ts-```--3. After writing the new route file, read constructor patterns to wire correctly:-```bash-ix search <ServiceName> --kind class --format json --limit 5-ix read memory-layer/src/main/scala/ix/memory/api/Routes.scala-ix read memory-layer/src/main/scala/ix/memory/Main.scala-```--4. After writing the CLI command, verify registration isn't duplicated:-```bash-ix read ix-cli/src/cli/register/oss.ts-```--5. Compile-check the backend:-```bash-sbt "memoryLayer/compile" 2>&1 | grep -E "error|warning|success"-```--6. Build the CLI:-```bash-cd ix-cli && npm run build 2>&1 | grep -E "error TS|error:"-```--7. Smoke-test the command:-```bash-ix <newcommand> --format json-```--8. Update docs and ingest:-```bash-# Edit CLAUDE.md and AGENTS.md to add the command to the appropriate table-ix ingest ./ix-cli/src ./memory-layer/src-```--9. Record the decision:-```bash-ix decide "Add ix <name> command" --rationale "<why this command exists>" --affects IxClient --format json-```--## Common Wiring Errors--- `Routes.scala`: wrong constructor args — always read the `class <Name>Routes(...)` signature before instantiating-- `Routes.scala`: referencing a class from the wrong package — check import path matches where the service lives-- `oss.ts`: registering the same command twice — grep for the register call before adding it-- `api.ts`: method returns `Record<string,string>` but caller expects `Map` — prefer `Map` and use `new Map(Object.entries(result))`-- `api.ts`: method signature accepts no args but CLI passes options — always add `opts?: {...}` if the command has flags--## Done Criteria--- `sbt "memoryLayer/compile"` passes with no errors.-- `cd ix-cli && npm run build` passes with no errors.-- `ix <newcommand> --format json` returns a valid JSON response.-- Command appears in `CLAUDE.md` and `AGENTS.md`.-- No duplicate registration in `oss.ts`.diff --git a/skills/ix-pro-command-extension/SKILL.md b/skills/ix-pro-command-extension/SKILL.mddeleted file mode 100644index 23a9ce67..00000000--- a/skills/ix-pro-command-extension/SKILL.md+++ /dev/null@@ -1,56 +0,0 @@-----name: ix-pro-command-extension-description: Use when adding or modifying pro CLI commands to keep registration, dynamic loading, patch-building semantics, and command safety coherent across ix-cli and Ix-pro.------# Ix Pro Command Extension--Use this when changing pro command implementation or wiring.--## Scope--- `Ix-pro/src/cli/register.ts`-- `Ix-pro/src/cli/commands/*`-- `IX-Memory/ix-cli/src/cli/register/pro-loader.ts`-- Any shared client patch payload behavior (`GraphPatchPayload`, `PatchOp`)--## Workflow--1. Confirm command wiring:-```bash-ix read /home/ianhock/ix/Ix-pro/src/cli/register.ts:1-260 --format json-ix read /home/ianhock/ix/IX-Memory/ix-cli/src/cli/register/pro-loader.ts:1-260 --format json-```--2. Inspect changed command module:-```bash-ix read /home/ianhock/ix/Ix-pro/src/cli/commands/<command>.ts:1-320 --format json-ix overview IxClient --format json-```--3. Validate patch intent and edge semantics:-```bash-ix search build<Command>Patch --kind function --format json --limit 20-ix impact IxClient --format json-```--4. Verify discoverability and operator UX:-```bash-ix search registerProCommands --kind function --format json --limit 10-ix search tryLoadProCommands --kind function --format json --limit 10-```--## Checklist--- New command is registered in `registerProCommands`.-- Loader compatibility with `@ix/pro/register` is preserved.-- `--format json` output remains stable for automation.-- Patch ops (`UpsertNode`, `UpsertEdge`, `AssertClaim`) reflect intended graph semantics.-- Validation blocks unsafe command input where applicable (example: workflow command safety checks).--## Guardrails--- Treat command output schemas as APIs.-- Do not add command behavior that bypasses entity resolution safeguards.-- Keep edge predicates explicit and consistent with existing pro model.-diff --git a/skills/ix-pro-command-extension/agents/openai.yaml b/skills/ix-pro-command-extension/agents/openai.yamldeleted file mode 100644index deb0c36b..00000000--- a/skills/ix-pro-command-extension/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX Pro Command Extension"- short_description: "Extend pro CLI safely across loader and commands"- default_prompt: "Use $ix-pro-command-extension to add or refactor a pro CLI command without breaking registration or patch semantics."--policy:- allow_implicit_invocation: truediff --git a/skills/ix-pro-delivery-loop/SKILL.md b/skills/ix-pro-delivery-loop/SKILL.mddeleted file mode 100644index 89ad9651..00000000--- a/skills/ix-pro-delivery-loop/SKILL.md+++ /dev/null@@ -1,63 +0,0 @@-----name: ix-pro-delivery-loop-description: Use when executing work with pro CLI objects (goals, plans, tasks, bugs, decisions, workflows) to keep delivery state explicit and machine-queryable.------# Ix Pro Delivery Loop--Use this when a task should be tracked through pro objects, not ad-hoc notes.--## Trigger--Use when at least one applies:-- New work should be sequenced into tasks.-- A bug should be linked to affected entities and a responding plan.-- A repeatable staged workflow should be attached and run.--## Core Loop--1. Resume and inspect:-```bash-ix briefing --format json-ix tasks --status pending --format json-ix bugs --format json-```--2. Create or select plan context:-```bash-ix goal create "<goal>" --format json-ix plan create "<plan>" --goal <goal-id> --format json-ix plan next <plan-id> --with-workflow --format json-```--3. Add executable tasks:-```bash-ix plan task "<title>" --plan <plan-id> --workflow-staged '{"discover":["ix overview <x> --format json"],"implement":["ix impact <x> --format json"],"validate":["ix tasks --plan <plan-id> --format json"]}' --format json-```--4. Track defects and linkage:-```bash-ix bug create "<title>" --severity high --affects <EntityName> --format json-ix plan create "<plan>" --goal <goal-id> --responds-to <bug-id> --format json-ix plan task "<title>" --plan <plan-id> --resolves <bug-id> --format json-```--5. Attach and run workflows:-```bash-ix workflow attach task <task-id> --file <workflow.json> --format json-ix workflow validate task <task-id> --format json-ix workflow run task <task-id> --stage discover --format json-```--6. Close loop:-```bash-ix task update <task-id> --status done --format json-ix bug update <bug-id> --status resolved --format json-```--## Guardrails--- Workflows must contain `ix` commands only; no shell operators.-- Keep dependency edges explicit with `--depends-on`.-- Prefer linking bugs/plans/tasks (`RESPONDS_TO`, `TASK_RESOLVES_BUG`) in the same session.-diff --git a/skills/ix-pro-delivery-loop/agents/openai.yaml b/skills/ix-pro-delivery-loop/agents/openai.yamldeleted file mode 100644index f32d98bd..00000000--- a/skills/ix-pro-delivery-loop/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX Pro Delivery Loop"- short_description: "Operate goals/plans/tasks/bugs/workflows together"- default_prompt: "Use $ix-pro-delivery-loop to drive this work through plan/task/bug/workflow lifecycle with linked entities."--policy:- allow_implicit_invocation: truediff --git a/skills/ix-rebuild/SKILL.md b/skills/ix-rebuild/SKILL.mddeleted file mode 100644index 7dbae584..00000000--- a/skills/ix-rebuild/SKILL.md+++ /dev/null@@ -1,111 +0,0 @@-----name: ix-rebuild-description: Use when running or recovering from a full ix rebuild — sbt assembly + CLI build. Covers how to interpret compile errors and common failure patterns in this codebase.------# Ix Rebuild--Use this when running `./scripts/dev/rebuild.sh` or fixing compile errors after merging changes.--## Build Order--```-sbt assembly (Scala backend) → npm run build (TypeScript CLI) → Docker restart-```--`./scripts/dev/rebuild.sh` runs all three. For faster iteration use the individual steps below.--## Fast Iteration Commands--```bash-# Scala only (fastest feedback on backend changes)-sbt "memoryLayer/compile" 2>&1 | grep -E "error|warning|success"--# Full Scala assembly (needed before Docker restart)-sbt assembly 2>&1 | grep -E "error|warning|success|Built"--# TypeScript CLI only-cd ix-cli && npm run build 2>&1 | grep -E "error TS|error:"--# Both + Docker restart-./scripts/dev/rebuild.sh-```--## Common Scala Errors and Fixes--### Wrong constructor args-```-not enough arguments for constructor Foo: (a: A, b: B)-```-→ Read the class signature: `ix search Foo --kind class --format json --limit 5`-→ Then: `ix read <path-to-file>` to see the actual constructor.--### Type not found-```-not found: type BulkPatchCommitRoutes-```-→ The class doesn't exist. Search for it: `ix locate BulkPatchCommitRoutes --limit 5`-→ Check if it was renamed or removed from the route aggregator.--### Type mismatch on service-```-found: ix.memory.smell.SubsystemService-required: ix.memory.subsystem.SubsystemScoringService-```-→ The stash/upstream used different packages. Check which class actually exists on disk:- `find memory-layer/src -name "Subsystem*.scala"`-→ Update the import and usage to match what exists.--### Wrong queryApi vs writeApi-```-found: ArangoGraphQueryApi-required: GraphWriteApi-```-→ Check the service constructor: `grep "^class <Name>" memory-layer/src/main/scala/**/*.scala`-→ Services that store claims need `writeApi`; read-only services need `queryApi`.--## Common TypeScript Errors and Fixes--### Missing method on IxClient-```-Property 'commitPatchBulk' does not exist on type 'IxClient'-```-→ Add the method to `ix-cli/src/client/api.ts`.-→ Check what endpoint it should call by reading the corresponding Scala route.--### Missing export from module-```-Module '"../errors.js"' has no exported member 'parseBackendError'-```-→ Read `ix-cli/src/cli/errors.ts` to see what's actually exported.-→ Remove the import and inline the logic, or add the export if it belongs there.--### Wrong argument count-```-Expected 0 arguments, but got 1-```-→ The CLI passes options the api.ts method doesn't accept yet.-→ Add `opts?: { ... }` to the method signature in `api.ts`.--### Duplicate command registration-```-Error: cannot add command 'smells' as already have command 'smells'-```-→ Open `ix-cli/src/cli/register/oss.ts` and remove the duplicate `register<Name>Command(program)` call.--## Smoke Test After Rebuild--```bash-ix status # backend alive-ix stats --format json # graph accessible-ix map --format json | head -5 # map pipeline works-ix smells --format json | head -5 # smell pipeline works-ix subsystems --format json | head -5 # subsystem pipeline works-```--## Done Criteria--- `sbt "memoryLayer/compile"` exits with `[success]`.-- `cd ix-cli && npm run build` exits cleanly (no `error TS` lines).-- `./scripts/dev/rebuild.sh` prints `IX backend is ready!`.-- `ix status` reports `ok`.diff --git a/skills/ix-session-memory/SKILL.md b/skills/ix-session-memory/SKILL.mddeleted file mode 100644index 9da6c4f6..00000000--- a/skills/ix-session-memory/SKILL.md+++ /dev/null@@ -1,69 +0,0 @@-----name: ix-session-memory-description: Use this for any non-trivial IX-Memory task to keep context synchronized in ix (briefing, impact, planning, decisions, and bugs) and to produce resumable work.------# Ix Session Memory--Use this skill at the start of multi-step work and keep using it until the task is done.--## Trigger--Use when the task has at least one of:-- More than one file or subsystem-- A risky change with dependency impact-- Work that should be resumable by another agent later--## Workflow--1. Resume context:-```bash-ix briefing --format json-```--2. Scope impact:-```bash-ix overview <target> --format json-ix impact <target> --format json-```--3. If no active goal/plan exists, create one:-```bash-ix goal create "<outcome statement>" --format json-ix plan create "<plan title>" --goal <goal-id> --format json-ix plan task "<first task>" --plan <plan-id> --format json-```--4. Pull next actionable work:-```bash-ix plan next <plan-id> --with-workflow --format json-```--5. Track major reasoning:-```bash-ix decide "<decision>" --rationale "<why>" --affects <EntityName> --format json-```--6. Track defects explicitly:-```bash-ix bug create "<bug title>" --affects <EntityName> --format json-```--7. Mark completed tasks:-```bash-ix task update <task-id> --status done --format json-```--## Guardrails--- Always use `--format json` for any command that is parsed or chained.-- Prefer `overview` and `impact` before low-level traversal.-- If resolution is ambiguous, rerun with `--kind`.-- Never follow unresolved `rawId`; use `ix text` or `ix read` instead.--## Done Criteria--- The change is represented in at least one plan/task update.-- Any architectural tradeoff is captured as a decision.-- Any discovered defect is captured as a bug or fixed in-task.-diff --git a/skills/ix-session-memory/agents/openai.yaml b/skills/ix-session-memory/agents/openai.yamldeleted file mode 100644index 5f14d114..00000000--- a/skills/ix-session-memory/agents/openai.yaml+++ /dev/null@@ -1,7 +0,0 @@-interface:- display_name: "IX Session Memory"- short_description: "Keep ix state synced across multi-step work"- default_prompt: "Use $ix-session-memory to resume context, scope impact, and track this task in goals/plans/decisions."--policy:- allow_implicit_invocation: true