tezgah

Analyze a running web or mobile app from its structured accessibility / DOM / native view tree instead of taking screenshots. Use when a task must drive, inspect, or verify a running application - walk a flow, read the UI, check the console, network or device logs, or confirm behavior end to end - rather than only read its source. Covers a real browser (Playwright MCP), an iOS Simulator or Android emulator (Mobile MCP), and optional web diagnostics (Chrome DevTools MCP).

Pick and run the right multi-agent harness for a task in this tree, backed by the codebase-memory graph. Routes to the cbm-map, cbm-review, or cbm-impact dynamic workflows, or to a single general-purpose subagent briefed with the cbm tools when a full harness is overkill. Use when the user asks for depth, coverage, an audit, a full review, "every call site", "what breaks if", "how does this work end to end", says ultracode, or when a task is too wide for one context window.

Edit drafts into sharper, more human writing while preserving the writer's personal voice, or detect AI-slop patterns without rewriting. Use when the user wants a draft clearer, more direct, more opinionated, or less AI-sounding, or asks whether writing reads as AI. Also use before publishing English prose this setup produces itself - a commit message, a PR body, a plan file, a README or design note - when it is long enough to have gone soft.

Creates a new plan file under <git root>/plans/open/ from free text, bootstraps the plans/ layer (README + open/ + done/) if missing, refreshes the README status table, and commits it on main as `plan: add NNN slug`. Use when a piece of work spans sessions or waits on something and the user says "/tezgah:plan-add <text>", "add a plan", "track this as a plan", or "make a plan for ...". Do NOT use for small self-contained edits that fit in one session.

Reads every open plan under <git root>/plans/open/, enriches rows with live PR state from `gh`, rewrites the README status table, commits it as `plan: update status`, and ends with a single recommendation for which plan to work on next. Use when the user says "/tezgah:plan-status", "what plans are open", "plan status", "where are we on the plans", or at the start of a session to pick work. Read-only except the README table and filling an empty `pr:` field.

Closes out finished plans: fetches origin, checks each open plan's branch for a merged or closed PR (or a branch merged into main), marks it done or discarded, moves it to plans/done/, rewrites the README status table, and commits one `plan: done NNN slug` (or `plan: discard`) per moved plan. Use when the user says "/tezgah:plan-sync", "sync plans", "close finished plans", or after PRs were merged. Never deletes branches and never touches files outside plans/.

Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).

Runs an auditable research line in the repository: the two-loop rhythm (bootstrap, inner experiment loop, outer synthesis), the workspace that holds its state, protocol-before-run so a prediction is provably older than its results, a six-dimension review of the claims before they are reported, and a provenance record of what the session decided. Use when a task's deliverable is evidence rather than a code change: a literature or reference review, a hypothesis to test, a comparison of variants, a benchmark or ablation, a research report or figure, or when the user says "research", "investigate", "araştır", "literatür", "hipotez", "deney", "ablation", "benchmark". Route the execution through the OpenResearch CLI when it is installed. Do NOT use for code discovery ("where is X", "who calls Y") - that is the code graph.

The full tezgah working contract. Load on demand when a tezgah session needs the deep detail behind the always-on core: instruction fidelity (deliver the whole ask, never a shortcut, no sycophantic openers), the code-graph-first rule and its deferred tool loading, the dynamic graph harnesses, the two-tier orchestration model with the cheap codegen bridge and its automatic fallback, external-model consult, OpenResearch routing for research tasks, and the exact kill switches. Use when the compact core points here, or when a task needs the code graph, a subagent fan-out, codegen, or a second opinion in full detail.