Commit 82e600c
ux: actionable gap notifications — what happened + what to do
Gap notifications now tell the user:
1. What happened (plain language, not jargon)
2. Why it matters (context about the gap type)
3. What to do next (specific /forge commands)
Before:
→ Document required tools/access in skills or create
setup-verification skills
After:
Your agent needed tools or access it doesn't have for
operations tasks. Check what's missing with /forge gaps,
then either install the required tool or create a skill
that documents the setup.
/forge gaps — full gap details
/forge behavior_gaps — all behavior patterns
Every gap type (fallback, deferral, uncertainty, infrastructure)
now has domain-specific context and actionable next steps.1 parent 422b997 commit 82e600c
2 files changed
Lines changed: 10 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
376 | 376 | | |
377 | 377 | | |
378 | 378 | | |
379 | | - | |
| 379 | + | |
380 | 380 | | |
381 | | - | |
| 381 | + | |
382 | 382 | | |
383 | 383 | | |
| 384 | + | |
| 385 | + | |
| 386 | + | |
| 387 | + | |
384 | 388 | | |
385 | 389 | | |
386 | 390 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
228 | 228 | | |
229 | 229 | | |
230 | 230 | | |
231 | | - | |
232 | | - | |
233 | | - | |
234 | | - | |
| 231 | + | |
| 232 | + | |
| 233 | + | |
| 234 | + | |
235 | 235 | | |
236 | 236 | | |
237 | 237 | | |
| |||
0 commit comments