Results for “stored-function”

Archive accumulated phase directories from completed milestones

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Generates a structured post-task reflection capturing surprises, patterns, prompt improvements, and gotchas, writing it to a markdown file without modifying project rules.

Persists project context across Claude Code sessions. Auto-loads project summaries on startup, tracks session progress, and saves structured state via deterministic Node.js scripts.

Search locally saved Codex session history stored in SQLite and session_index.jsonl, with filters for provider, time range, and archived status.

Creates and maintains persistent markdown planning files that survive session resets by hooking into Claude Code's lifecycle.

Look up and apply the cooked, indexed proof playbook built from proof-material. Use when the user is proving a theorem, planning a proof, seeking reusable proof moves by task shape, assumptions, tags, desired move, or material source ID, or adapting cooked local moves and macro strategies with public source attribution.

Retrieve task-relevant project and global memory without loading everything. Load when the user asks what we decided, recall prior context, find memory about a feature, explain past rationale, resume a task, or check deferred ideas.

Tracks async and multi-step work by storing tasks as JSON files in .dex/tasks/, with commands to create, list, show, complete, edit, and delete tasks.

Validate built features through conversational UAT