feat: redesign Feature Planner for continuous improvement and fix observability gaps#83
Merged
zacharias-ona merged 1 commit intomainfrom Apr 16, 2026
Merged
Conversation
…ervability gaps - Redesign Feature Planner to triage unlabeled GitHub Issues (user-created feature requests and bugs) in addition to decomposing product specs - Add needs-human-requeue automation (cron 30min) to detect user responses on needs-human issues and remove the label for re-triage - Update PR Reviewer to merge ona-user labeled PRs without issue reference - Add issue quality requirements to Incident Responder, Post-Merge Verifier, and Performance Monitor (acceptance criteria + technical notes sections) - Fix Performance Monitor missing status:backlog label on created issues - Create development-workflow skill documenting the full automation roster and how feature requests/bugs flow through the system - Update Feature Planner skill with continuous improvement workflow - Add GitHub issue templates for features and bugs - Document automation development loop in AGENTS.md and conventions.md - Update needs-human label from permanent exclusion to re-queueable - Create GitHub Issues #80, #81, #82 for Sentry observability fixes Co-authored-by: Ona <no-reply@ona.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
✅ UI verification skipped — no UI files changed ( |
4 tasks
Collaborator
Author
|
✅ Post-merge verification passed — live site is functional. Ad-hoc smoke tests (all passed):
E2E test suite: 8 passed, 15 failed, 4 skipped Skipped routes:
|
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
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.
What
Redesign the Feature Planner automation for continuous improvement (not just initial spec decomposition), establish issue quality requirements across all automations, and create GitHub Issues for the Sentry observability fixes.
Changes
Automation updates (6 files, all registered)
needs-human+ questions to insufficient ones.needs-humanissues and removes the label for re-triage.ona-userlabel without requiringCloses #N.status:backloglabel (bug fix: issues were never picked up) + Acceptance Criteria and Technical Notes sections.Documentation (3 files)
ona-userlabel, updatedneeds-humanfrom "permanently excludes" to re-queueable..agents/conventions.md— new Development Loop section documenting how to queue work,ona-userconvention,needs-humanfeedback loop..ona/skills/development-workflow/SKILL.md(new) — full reference for how feature requests and bugs flow through the automation system.Supporting files (3 files)
.github/ISSUE_TEMPLATE/feature.yml— enforces description + priority at creation time..github/ISSUE_TEMPLATE/bug.yml— enforces description + steps to reproduce + expected vs actual.GitHub Issues created
priority:1priority:2, depends on Add Sentry error capture helper, conventions, and regression test #80priority:2, depends on Add Sentry error capture helper, conventions, and regression test #80How
The observability fixes are delegated to the Feature Builder automation via GitHub Issues. Issue #80 (priority:1, no deps) will be picked up first. After it merges, #81 and #82 (priority:2) become unblocked.
Testing
No code changes — only automation YAML, documentation, and issue templates. All automations registered and verified via
ona ai automation update."