feat: use richer output surfaces than AskUserQuestion for user-facing output

Aperta
  • Qualcosa non va?
#252 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
shell
Ambito
developer-experience

Direzione di ricerca

Start by reading the /review, /build, /plan, and /debrief skills and the portability work in #225–#229. Define which output uses each surface, how each skill falls back when a surface is unavailable, and how the existing docs/ files remain discoverable from a cold start; done means these rules are stated and applied to the listed outputs.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

feature p2

Description

Every skill treats AskUserQuestion (and its per-harness equivalents) as the only way to put something in front of the user. It fits a short decision with 2–4 options. It is the wrong surface for most of what Wingspan actually produces: consolidated review reports, plan summaries, brainstorm documents, debrief timelines. Today those are written to docs/ and flattened into a few lines of chat.

Other surfaces exist — Claude Artifacts, for one: a published page the user can read, share with the team, and come back to after the context is gone. Wingspan should pick the surface per output instead of defaulting to a question prompt.

Requirements

  • A rule for which output goes to which surface: decision with options → AskUserQuestion; long report or document → artifact/file; progress → chat.
  • Candidates to move first: the consolidated review.md from /review and /build, the plan from /plan, the debrief from /debrief.
  • In agent mode (#258), the log of decisions taken on the user's behalf becomes one interactive page: the user reviews each decision, keeps or changes it, and adds notes, and the agent adapts to what changed.
  • Surfaces are harness-specific. Each skill needs a stated fallback when the surface is unavailable (relates to the portability work in #225–#229).
  • A richer surface must not replace the docs/ file — the next phase still discovers its input from a cold start.

Additional Context

Wingspan is harness-agnostic by design, so this is a capability-detection problem, not a Claude-Code-only feature.

Lingua principale
Shell
Stelle
114
Fork
16
Merge medio
6g 1h
PR unite (30g)
10

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di VeryGoodOpenSource/vgv-wingspan

Tutte le issue di VeryGoodOpenSource/vgv-wingspan

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.