By iyulab
Productivity toolkit for library maintainers - adaptive iterative development, issue triage, PR review, telemetry-driven issue discovery, and playbook-driven backlog discovery with project philosophy alignment
Adaptively discovers new backlog phases for a project's ROADMAP.md by running a convergent/emergent research playbook — vision-gap analysis, trend/competitive research, telemetry-az output reuse, voice-of-customer mining, technical-debt audits, active dogfooding (a team member driving the product live in a fresh vision-anchored scenario to observe feature/UI/UX/app-flow gaps first-hand), plus deliberately emergent techniques (pre-mortems, subtraction sessions, chaos engineering, fresh-eyes onboarding) — selected via a persistent per-activity cadence state, self-diagnosing which emergent session to rotate in when the backlog feels stale. Always produces a proposal document for human review; never merges into ROADMAP.md automatically. Use when the backlog is running dry, when run-cycle reports the feature frontier exhausted, or periodically to keep the roadmap fed with fresh, philosophy-aligned candidates. An empty or already-recently-run backlog is a deepen-signal (go use the product and re-check the vision), never a done-signal. Fully independent of run-cycle — run-cycle only consumes ROADMAP.md, this skill only feeds it.
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".
Triages external issues with critical evaluation against project philosophy and scope
Critical-but-constructive maintenance mindset — auto-activates during conversational issue, PR, and development discussions to keep evaluation principled and architecture-defending
Reviews pull requests with project philosophy alignment
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of Claude Code plugins for library maintainers and developers.
As mainstream harness / loop-engineering tooling grows heavier — an "OS wrapped around the model" — these plugins make the opposite bet: stay thin and ride Claude Code's native loop, tools, and context management, adding only the judgment a generic harness cannot supply. A custom layer is always slower to evolve than the harness beneath it, so the goal is to fill gaps, never fence off native features.
Three governing principles (the plugin's constitution):
How that differs from the mainstream:
| Mainstream harness / loop tooling | iyu | |
|---|---|---|
| Stance | Wrap the model in an OS | Thin layer on Claude Code native |
| Human instruction | Ground truth to execute | Below the project constitution; corrected via amendment |
| Termination | Stops at delivery (compiles / marker hit) | Climbs the lifecycle ladder past delivery |
| Feedback loop | Ends at merge | Closed — production telemetry (App Insights) flows back to the backlog |
# Add the marketplace
/plugin marketplace add iyulab/claude-plugins
# Install the iyu plugin
/plugin install iyu@iyulab-plugins
Versioning — two independent version numbers exist by design:
marketplace.json → metadata.versiontracks the marketplace registry (structure of this catalog), while each plugin'splugin.json → versiontracks that plugin itself. They advance separately. Per-pluginkeywordsare sourced fromplugin.jsonand mirrored into the marketplace entry. See CHANGELOG.md for the iyu plugin history.
Productivity toolkit for open-source library maintainers — adaptive iterative development, issue triage, PR review
| Component | Type | Activation | Description |
|---|---|---|---|
mindset | Skill | Auto (background) | "Critical but Constructive" mindset for conversational triage/dev discussions |
issue-triage | Skill | Auto (conversational) | Decision matrices and triage advice |
/iyu:issue | Skill | Manual | Full issue triage report |
/iyu:pr | Skill | Manual | PR review with security focus |
/iyu:run | Skill | Manual | Plan-driven development execution |
/iyu:run-cycle | Skill | Manual | Adaptive iterative cycles (re-plan → execute → verify → reflect) |
/iyu:telemetry-az | Skill | Manual | Azure App Insights telemetry triage — defects, regressions, feature drop |
/plugin install iyu@iyulab-plugins
The plugin automatically activates when you discuss issue evaluation or PR review. Just ask naturally:
| Command | Description |
|---|---|
/iyu:issue | Systematic issue evaluation with root cause analysis |
/iyu:pr | Professional PR review with security awareness |
/iyu:run | Plan-driven development execution |
/iyu:run-cycle | Adaptive iterative development cycles |
/iyu:telemetry-az | Azure App Insights telemetry triage and issue discovery |
# Triage a GitHub issue
/iyu:issue https://github.com/user/repo/issues/123
# Quick decision only
/iyu:issue https://github.com/user/repo/issues/123 --quick
# Triage and save report
/iyu:issue ./docs/feature-request.md --save
# Full PR review
/iyu:pr https://github.com/user/repo/pull/123
# Quick review (critical issues only)
/iyu:pr https://github.com/user/repo/pull/123 --quick
npx claudepluginhub iyulab/claude-plugins --plugin iyuMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
GitHub issue triage, creation, and management
This is a getty104's base tool set
GitHub workflow: issues, PRs, worktrees, sub-issues
For easy problems, start here. For harder problems, do this after Explore.