review-implementation

Review significant integrations for discovery and exploitation failures.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/saross/personal-assistant --skill review-implementation-saross
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-implementation
Source: https://github.com/saross/personal-assistant/tree/main/skills/review-implementation
Command: npx skills add https://github.com/saross/personal-assistant --skill review-implementation-saross

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This protocol helps cross-functional teams identify and prevent suboptimal implementation choices by surfacing discovery failures (unknown capabilities) and exploitation failures (underutilized capabilities) during significant integrations, tool adoptions, or phase transitions.

Core Features & Use Cases

  • A structured, multi-phase review workflow spanning capability scans, exploitation reviews, and quantitative audits.
  • Guidance on surfacing alternative approaches, risks, and governance considerations to support evidence-based decision making.
  • Phase-aligned outputs and governance recommendations to improve rollout safety and effectiveness.

Quick Start

Run the formal review on an upcoming integration to surface risks and improve decision quality.

Frequently Asked Questions about review-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is an implementation review for new technology integrations?

An implementation review is a structured protocol that identifies and mitigates suboptimal technology choices by surfacing discovery and exploitation failures before significant integrations or tool adoptions.

How do I prevent suboptimal tool adoption decisions in my organization?

You prevent suboptimal tool adoption by applying a multi-phase review workflow that includes capability scanning, exploitation review, and quantitative audits to surface risks and governance considerations.

When do I need to run a structured risk analysis for a phase boundary change?

You need to run a structured risk analysis when undertaking significant new integrations, tool adoptions, or phase-boundary changes to ensure risk-aware decision making and improve rollout safety.

How does a capability scan work during a technology rollout?

A capability scan works by systematically identifying unknown or underutilized capabilities across your tech stack, forming the discovery phase of a review protocol to prevent exploitation failures.

What is the best way to audit technology exploitation failures before a major rollout?

The best way to audit exploitation failures is to execute a formal multi-phase review that defines required outputs and governance considerations, culminating in a quantitative audit for explicit recommendations.

Can I use this protocol to review governance considerations for cross-functional teams?

Yes, you can use this protocol to review governance considerations for cross-functional teams, as it provides phase-aligned outputs and governance recommendations to support evidence-based decision making.