iyu

Discovers and judges new backlog phases for a project's ROADMAP.md like an owner-manager — runs a convergent/emergent research playbook (vision-gap, trend/competitive research, domain-practice and academic scans, stewardship inspection of dependencies/config/docs/repo hygiene, telemetry reuse, active dogfooding, plus emergent sessions rotated in by symptom) on a persistent per-activity cadence, then synthesizes the findings into a state-of-the-product diagnosis, an evidence-grounded importance ranking, and a dependency-ordered now/next/later staging toward the vision. Always produces a proposal document for human review; never merges into ROADMAP.md automatically.

Closes out a work session — records where things stand, migrates completed work out of the continuity docs into the history index, derives and stages the next scope, flags (not briefs) the decisions waiting on a human for `/iyu:resume` to brief when the next session opens, and commits everything it can confidently attribute (this session's work, pre-existing uncommitted leftovers, and its own doc edits) toward a clean `git status` — never pushing, and reporting rather than guessing at anything ambiguous. Produces the document a fresh session (or another person) resumes from, so nothing depends on the current conversation surviving.

Use when discussing whether to accept, reject, or redirect an external issue or PR. Triggers on "triage this issue", "evaluate this feature request", "should I accept/merge this", "is this in scope", "review this PR/contribution", "how should I respond to this issue".

Critical-but-constructive maintenance mindset — auto-activates during conversational issue, PR, and development discussions to keep evaluation principled and architecture-defending

Opens a work session — reads the continuity docs and recent state, synthesizes where things actually stand, proposes a re-prioritized next scope with any derived prerequisites or objections, and briefs the decisions `/iyu:handoff` flagged with grounded options and a recommendation. Records what gets decided immediately, then stops — execution is a separate, explicit step.

Executes adaptive iterative development cycles — each cycle is a self-contained plan/execute/verify/reflect loop that reshapes the roadmap and derives emergent follow-on scope from its own output

Takes finished work out — bumps the version, commits, pushes, and watches the CI run to completion, reporting what failed if it fails. Checks first whether now is the right moment — if remaining backlog work would touch the same consumer-facing surface, it says so and asks rather than publishing a version the next few items obsolete.

Analyzes Azure Application Insights telemetry since the last run to surface defects, performance regressions, and feature-drop signals, tracked run-over-run as a quality trend (error-rate/p95/issue-count direction, with closed-issue recurrence detection), plus a report-only user-analytics reading (active-user growth, feature/page preference shifts, engagement). Triages findings against project philosophy, files issues only for threshold-crossing ones, and leads every report with a both-purpose Trend section backed by a 12-run history.