- Skills
- 11
- 仓库
- 1
- 职业覆盖
- 4
- 场景覆盖
- 3
- Stars
- ★ 0
iyulab 的 Skills 11
drive
Pushes the open stage of a product to its agreed satisfaction bar — implement one failing scenario at a time, have an independent evaluator judge the running build, repeat until the stage passes or needs something only the owner can supply, then show the owner a demo. Use after `/iyu:charter` has a signed stage contract.
charter
Interviews the owner to set a product's goal and writes the stage contract — an ordered ladder of stages that each work on their own, with scenarios an observer can watch, a calibrated satisfaction bar, the promises each stage must keep, and every owner decision that could block it. Use before `/iyu:drive`, and again at each stage boundary.
accept
Judges the open stage by having an independent evaluator subagent drive the real, running build like a user — scenario by scenario, against the rubric — and record an evidence report and the status fields. Use to get a verdict without building anything; `/iyu:drive` dispatches the same evaluator each round.
telemetry-az
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.
ship
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.
run-cycle
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
resume
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 settles the decisions `/iyu:handoff` flagged the way a capable employee would — grounded options, trade-offs, and a recommendation that becomes the provisional decision, recorded at once for the owner to correct rather than answer. Only external blockers, owner-gated acts, and criterion gaps are left waiting on the owner. Then stops — execution is a separate, explicit step.
mindset
Applies a maintainer's critical-but-constructive judgment — weighs a proposed feature, design change, or instruction against the project's own philosophy, architecture, and design docs, names any conflict instead of silently complying or refusing, and flags scope creep and boundary leaks.
issue-triage
Supplies decision matrices and reply templates for accepting, adapting, deferring, redirecting, or declining an external issue, feature request, or pull request. Use when deciding whether to accept or merge input from outside contributors, or how to respond to its author.
handoff
Checkpoints a work session — at its close (the main use), mid-session before clearing context or switching focus, or at the end of a `/iyu:run-cycle` run. 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.
backlog-discover
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; adopts into ROADMAP.md only the items the project's own evidence grounds and that stay inside its declared role, and leaves everything else in the proposal for a human.