ridermw
- 6 skills
- 0 followers
- 22 hours ago last updated
- ▌ Sync Repos · ridermwUse when the user wants to update or sync many local git repositories at once — "pull latest for all repos", "sync all repos from main", "walk through the repos and pull", "update all my git repos", "fetch all clones", or bulk fast-forward across a folder of git checkouts. Non-destructive, fast-forward-only; never force/reset/stash/push.
- ▌ Project Room · ridermw bundleUse when organizing source files into a project room, capturing or indexing evidence, building a source inventory or working brief, drafting a source-cited deliverable, refreshing a room, or archiving superseded outputs. Includes first-run setup, new project rooms, room selection, and questions about what a room knows. Not for implementing the project itself.
- ▌ Plan Exit Review · ridermw bundleBounded, interactive engineering-readiness review of a concrete implementation plan BEFORE coding — routine features, refactors, bug fixes. Challenges scope (Step 0), then reviews architecture, code quality, tests, and performance with opinionated, recommendation-first questions. Review only — does not modify code. For an exhaustive maximum-rigor security/operations/failure-mode audit of a high-risk or cross-cutting plan use plan-mega-review, and for multi-reviewer adversarial critique of an idea, decision or artifact that is not a pre-coding plan gate use adversarial-review. Triggers: "plan exit review", "review my plan before I build", "engineering readiness review", "scope challenge", "is this plan ready to implement".
- ▌ Plan Mega Review · ridermw bundleMaximum-rigor, exhaustive review of a HIGH-RISK or cross-cutting implementation plan, design doc, or architecture proposal — use only when the user explicitly asks for a deep/mega/boil-the-ocean review or the change is high-blast-radius. Three modes: SCOPE EXPANSION (build the cathedral), HOLD SCOPE (bulletproof what is here), SCOPE REDUCTION (cut to essentials). Maps every failure mode, demands observability, models threats, names error and rescue paths. Review only — does not modify code. For an ordinary bounded pre-coding review use plan-exit-review, and for multi-reviewer adversarial critique of an idea, decision or artifact that is not a pre-coding plan gate use adversarial-review. Triggers: "mega plan review", "maximum rigor review", "boil the ocean review", "review this high-risk plan", "deep review before I build this".
- ▌ Adversarial Review · ridermwPressure-tests an idea, plan, or change by running separated adversarial reviewer perspectives rather than a generic pros/cons list, then synthesizes consensus-ranked findings with severity, confidence and cited evidence. SPAR mode debates a decision through roles with conflicting incentives; Rubber Duck mode runs independent critique reviewers over an artifact and ranks what they agree on. Always discloses the execution path it actually achieved and never claims reviewers or model diversity it did not. Use when the user asks to pressure-test, stress-test, poke holes in, red-team or critique an idea, proposal, strategy, architecture tradeoff, code change, test plan, debugging hypothesis, suspected bug or risky decision. For a bounded pre-coding readiness gate on a concrete implementation plan use plan-exit-review, and for a maximum-rigor audit of a high-risk plan use plan-mega-review; this skill is adversarial critique of any artifact or decision, not a plan-approval workflow.
- ▌ Ado Pr Build Monitor · ridermwUse when the user wants to monitor or watch an Azure DevOps (ADO) pull request build to completion — "monitor PR [url] and let me know when the build completes", "watch this PR build", "tell me when the PR build passes and a work item is linked", "is the PR gate green yet", ADO PR build/policy/gate status polling. Read-only; reports status, does not post comments or complete the PR.