# Implementation Review

> Review feature implementations for spec compliance, code quality, and organizational consistency. Use when implementing features, checking spec compliance, validating API implementations, or preparing releases. Use when this capability is needed.

- Skill: `tomevault-io/implementation-review` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/implementation-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/implementation-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/implementation-review

---


# Implementation Review

> Comprehensive review of feature implementations against specifications and organizational standards.

## When to Use

- Implementing or completing new features
- Validating spec compliance before merge
- Checking API implementation correctness
- Preparing release readiness assessments

## Instructions

### Step 1: Gather Context

1. Identify the implementation scope:
   ```bash
   git diff --name-only HEAD~5
   git status
   ```
2. Locate relevant specification: `UPP-1.3.spec.md` or related spec files
3. Identify affected providers/modules

### Step 2: Spawn Review Sub-Agents

Delegate parallel reviews to sub-agents for:

| Agent Focus | Review Scope |
|-------------|--------------|
| **Spec Compliance** | Compare implementation against spec requirements |
| **Code Standards** | Organizational consistency, naming, patterns |
| **API Validation** | Search web to validate API parameters, endpoints, payloads |
| **Regression Check** | Search codebase for potential breaking changes |

### Step 3: Synthesize Reports

Collect sub-agent findings and compile:

1. **Compliance gaps** - Missing or incorrect spec implementations
2. **Quality issues** - Code smells, inconsistencies, design concerns
3. **API correctness** - Validated against official documentation
4. **Regression risks** - Potential breaking changes identified

## Output Format

```markdown
# Implementation Review Report

## Summary
[One paragraph overview]

## Spec Compliance: [PASS/PARTIAL/FAIL]
- [ ] Requirement 1
- [ ] Requirement 2

## Code Quality Issues
| Severity | File | Issue | Recommendation |
|----------|------|-------|----------------|

## API Validation
[Findings from web search validation]

## Regression Risks
[Identified risks and mitigation]

## Release Readiness: [READY/BLOCKED/NEEDS WORK]
[Estimation with blockers listed]
```

## Notes

- Always validate external API usage against current documentation
- Cross-reference with existing provider implementations for consistency
- Flag any deviations from established patterns

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/providerprotocol) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-13 -->