v2.2.4 — the project brief now works end to end
v2.2.4 — the project brief now works end to end
The project brief is what turns a rough goal into a real plan. It has to be obvious for a first-time user, and it has to actually reach the parts of the system that plan and build. A full code trace found gaps on both fronts — this release closes them.
What's new
- Import an existing plan as the brief. Paste markdown or upload a
.mdfile, see a live preview, and submit — it's written verbatim todocs/PRD.mdand the brief is finalised. No retyping a spec into the chat. - The brief is clearly the required first step — but still one click away. It was required before plan generation, yet the UI called it "optional" three times. The wording now matches reality, with a plain-language explainer ("what is the brief, and why"), a Sarah greeting + example-question chips in the empty chat, and a Generate-Plan button that's disabled with a clear hint until the brief is ready.
- The full brief reaches the planner. Plan generation passed only six structured fields and never read the rendered
docs/PRD.md; now the full PRD is fed to the planner, and the plan's goal is pinned to your project goal verbatim (no planner drift). Same on the automatic QA-replan path. - The brief reaches the executing agents. Every dispatched agent prompt gains a compact "Project context" section, so design preferences and constraints are honoured by the implementers, not just the planner.
- New-project goal field no longer fights you. Both new-project dialogs auto-filled the goal with the template's example and refilled it whenever you cleared it; the example is now a placeholder, so the field starts empty.
Update (existing install)
/plugin marketplace remove wisp-local
/plugin marketplace add Samuel0101010/wisp-orchestrator
/plugin install wisp@wisp-local
Then /wisp-dashboard. The version chip reads v2.2.4. (If you see Permission denied (publickey), run once: git config --global "url.https://github.com/.insteadOf" "git@github.com:".)
Verification
All 8 local gates green; server (573) + web (197) + package unit tests; e2e (54) green; CI (verify + e2e) green. Built subagent-driven: each phase = dev subagent → adversarial review subagent (caught real residual issues before each commit) → lead verification, including dark + light screenshots of the new brief UI.
🤖 Generated with Claude Code