Trigger config redesign (phase 1): sentence builder + recipes#261
Merged
Conversation
…n phase 1)
Reimagines the column automation UI per .tickets/_docs/TRIGGER_UX_REDESIGN.md.
Presentation-layer only — reads/writes the same ColumnTriggers JSON; no backend
or pipeline change.
Replaces the 3-tab form (General / Triggers / Exit, with the common case buried
behind a hidden "advanced editor" split across two tabs) with one flowing modal:
- **Identity** (name · icon · color) up top.
- **Automation** — a plain-language sentence: "When a task enters this column,
[run an AI agent ▾] using [Claude ▾] [opus ▾] · then move it on when
[the agent finishes ▾]." Each token is an inline dropdown. Led by a one-click
**recipe gallery** (⚡ Code it · 👀 Review+approve · 🧪 Run tests · 🔀 Open PR ·
▫ Manual) that wires a complete runnable rule. Picking a real exit condition
implies auto-advance; "manually" doesn't.
- **Advanced** (collapsed) reuses the existing full editors verbatim — on-entry /
on-exit ActionEditor, the exit-details editor (retries/timeout/auto-advance),
and capacity — so nothing is lost; power users open one expander.
- A plain-language **summary chip** in the footer ("▸ Run an AI agent · advance
when the agent finishes").
New: column-recipes.ts (recipes, plain-language clauses, summary, model values
matching the spawn-cli editor) + column-automation-sentence.tsx. +7 tests.
Phase 2 (cleanups: unify model vocab, de-jargon, drop dead trigger_task / the
LLM-generate box) and phase 3 (column-card chip, zero-config defaults) follow.
tsc · lint · vitest (419) green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reimagines the column automation UI per
.tickets/_docs/TRIGGER_UX_REDESIGN.md. Presentation-layer only — reads/writes the sameColumnTriggersJSON, no backend/pipeline change.Before → after
Was: a 3-tab modal (General / Triggers / Exit) where the common case ("run Claude, advance when done") was buried behind a hidden "advanced editor" and split across two tabs with no visible link between the action and its exit criterion.
Now, one flowing modal:
ActionEditor, exit details, capacity) — nothing lost; power users open one expander.New
column-recipes.ts+column-automation-sentence.tsx; +7 tests. tsc · lint · vitest (419) green.Known phase-1 scope
column-trigger-editor(NL-generate box) is now unused by the dialog; removed in phase 2.Phase 2 = cleanups (unify model vocab to opus/sonnet/haiku, de-jargon Terminal/Managed, drop dead surface). Phase 3 = on-card chip + zero-config defaults.