526c19fc21
- Persist chat stars in the operator-session registry (chat_star) so every browser/device shows the same Starred group; migrate old local stars once. - Add a compact pipeline graph shape to list responses and draw a lightweight list miniature; replace the cryptic id/version line with the stage count. - Surface OpenCode form questions as a chat card (chat_answer), replay a pending form to late subscribers, and notify for background questions. - Make the mobile dock's Search cell equal to every destination, keep the tab row visible with 100svh, and let Source use the full pane height. - Let a fresh sign-in auto-connect to its own origin; use a Lax session cookie with Expires so Remember me survives app/link launches. - Keep shipped starters and the skill agnostic: no repository paths, project areas or personal device commands; add Diagnose/Fix and Research starters. - Refresh the installed skill and document the new browser conventions.
50 lines
2.4 KiB
Markdown
50 lines
2.4 KiB
Markdown
# Small tasks and execution
|
|
|
|
Choose the simplest reliable route: direct work, delegation or a pipeline. The
|
|
manager remains responsible for completion and may take over any role directly.
|
|
|
|
## An item
|
|
|
|
One item changes one observable behavior. State its goal, relevant files, a few
|
|
testable acceptance checks and scope boundaries. Avoid long history, invented
|
|
implementation plans and boilerplate rules already in the project map.
|
|
Separate independent features even when they share a file; resolve small hunks
|
|
at integration. Serialize only actual dependency or resource conflicts.
|
|
|
|
## Stage jobs
|
|
|
|
- Plan: a short approach and acceptance checks when they help.
|
|
- Code: the focused change, tests and focused checks.
|
|
- Review: the whole task diff and independent verification.
|
|
- UIReview: rendered behavior with controlled data and captures.
|
|
- Land: commit the reviewed work, integrate main and resolve conflicts.
|
|
|
|
Names are a convention, not a requirement; a pipeline can use any clear stage
|
|
names. Keep each stage's job narrow enough to judge its output.
|
|
|
|
Hand off the desired behavior and the evidence that should exist at the end, not
|
|
another stage's restrictions. A clean worktree is a successful no-op for
|
|
preparation, not a failure. Nonvisual work needs no rendered evidence; a visual
|
|
change does.
|
|
|
|
## Pipeline choice
|
|
|
|
Prefer the smallest workflow that makes the work verifiable: plan when the design
|
|
is genuinely uncertain, review when a change is risky or broad, and a visual survey
|
|
when appearance is the question. Stage names describe jobs, not fixed roles. Read
|
|
the project's own maps and commands instead of assuming an area layout. Keep models
|
|
and costs as agreed.
|
|
|
|
## Recovery and landing
|
|
|
|
Inspect `pipelines inspect ID --json` and actual files after failure. Preserve
|
|
partial changes. Prefer resuming the original stage with corrected input or fixing
|
|
and merging directly; do not repeat completed work or add a merger pipeline.
|
|
For delivery=true, return a clean checked candidate and let the server land it.
|
|
For direct recovery, merge safely and verify it. Only then check ancestry.
|
|
Record real failures without blocking unrelated progress. Never delete branches.
|
|
|
|
Use `pipelines wait ID` as a background wait for active runs; no polling driver.
|
|
Record stale docs in a per-item note unless documentation itself is the task.
|
|
Keep reports short and separate code, testing, landing and deployment status.
|