karta

Use when implementing one work item from a karta binder in an isolated git worktree — stack-agnostic (frontend, backend, CLI, data, IaC, …) — running the project's lint/test/build plus the item's acceptance check, tagging commits, and completing the item on its branch (in a wave the orchestrator merges; invoked directly the worker merges into the per-binder integration branch). No PR. Trigger phrases: "build this binder item", "implement work item `<id>`", "karta-build `<binder> <id>`".

Harvest every KARTA-DEFER and KARTA-SME-OVERRIDE marker in the repo into a one-shot, read-only ledger so deliberate shortcuts and overrides don't rot into "later means never". Groups by file, flags deferrals with no follow-up trigger and legacy-format overrides due for migration. Writes nothing, tracks nothing. Trigger phrases: "karta debt", "list the shortcuts", "what did we defer", "harvest the overrides".

Deliver a karta binder by building its work items in parallel waves onto a per-binder integration branch, serializing only where correctness or collision demands it; resume is git-native; ends at the assembled integration branch (no PR). Trigger phrases: "deliver this binder", "run the binder", "karta-deliver `<binder>`".

Automatically correct documentation drift after a delivery (or on demand). Opt-in via .karta/doc-gardner.json; when on, it rewrites prose docs (README, docs/, AGENTS.md, ARCHITECTURE) to match the current code and commits the fix to the integration branch — no report-only mode, no severity tiers, no human waive. Trigger phrases: "gardner the docs", "fix doc drift", "run doc-gardner".

Improve the project's stack packs from what its builds keep repeating. Opt-in via .karta/kaizen.json, and the switch is absolute: absent or disabled means kaizen never runs, even when invoked directly. When on, it seeds every pack the project uses into .karta/sme/ on the first enabled run, then writes pack edits as labeled kaizen: commits a human reviews — it never weakens a rule and never promotes a pack to enforcing. Sharpening rules from repeated overrides, erosion notes, and the first-draft discipline are live; new-pack suggestions and the advisory/enforcing pack flag come in a later phase. Trigger phrases: "run kaizen", "kaizen the packs", "improve the stack packs".

Write or revise prose so a real reader can use it on the first read. Apply this whenever drafting or editing user-facing writing — documentation, READMEs, guides, announcements, emails, policies, regulations, release notes, help text, error messages, public-facing copy, or any message someone has to act on. Also apply when the user says "make this clearer," "simplify this," "rewrite in plain English," "less jargon," "tighten this up," asks for an edit pass on existing prose, or wants text to read less like AI/LLM output — "remove the AI tells," "de-slop this," "make it sound human-written," "less ChatGPT-sounding." Skip for code, code comments, commit messages, and internal log lines — those follow different conventions.

Analyze a problem/feature description and/or a design mock or non-functional prototype, grill the user in rounds about every decision the repo cannot answer, and synthesize a validated binder of work items — or an ordered set when a named test says the work must land in stages — for ad-hoc orchestration; stack-agnostic (frontend, backend, CLI, data, library/SDK, IaC, mobile, ML, docs — UI is one stack among many); emits .karta/binders/<slug>.json. The draft is reviewed as an editable in-chat card — or one plannotator browser annotation session when that separately-installed CLI is present — and commits only on the explicit "commit" verb. Trigger phrases: "plan this with karta", "synthesize a binder", "break this work into a binder", "karta-plan this feature".

Show what's next in a karta run — where you are and the single next action, at binder and work-item level, derived from git and never stored. Read-only. When someone wants to SEE or watch status, it opens the live Karta Watch browser page by default — ephemeral for this session unless the repo is opted into the persistent multi-repo hub; a one-shot terminal map is the headless fallback. Trigger phrases: "what's next", "karta status", "where am I in this binder", "show me the karta status", "karta watch", "turn off karta watch", "karta-status".

Compare a running frontend implementation against design HTML files exported from Claude Design OR a runtime-JSX design source. Opens both the live app (at the caller-provided app URL) and the served design prototype through bundled uv-run capture scripts, captures screenshots and DOM snapshots, then reports structured discrepancies across layout, color, typography, spacing, component structure, and visual hierarchy. Validates one view per invocation — the calling pipeline loops for multiple views. Invoke when validating implementation fidelity — trigger phrases include "validate against the design", "compare implementation to design", "check design fidelity", "does this match the design", "visual QA against design HTML", or any request to diff what's running vs the design prototype files.

Verify one built work item against its behavioral acceptance check (oracle types unit/integration/e2e/smoke) in a read-only, fresh session on the actual diff; check acceptance + external-contract conformance + boundary crossings; kick findings back to build and escalate to the human only on retry-exhaustion.