Skip to content
Cload Cloud
Productivity

review-implementing

Evaluate code implementation plans and align with specs.

View source More in Productivity

What review-implementing Does

Review-Implementing is a code review skill designed to evaluate implementation plans against technical specifications and project requirements. It bridges the gap between planning and execution by systematically assessing whether proposed code implementations align with documented specs, architectural decisions, and quality standards. This skill is essential for technical leads, product designers working with engineering teams, and AI agents orchestrating multi-step development workflows who need to validate that code changes won’t introduce technical debt or deviate from the intended design.

How to Install

  1. Clone or download the skill repository from the GitHub source
  2. Navigate to the engineering-workflow-plugin/skills/review-implementing directory
  3. Extract the skill files to your Claude Code environment or AI agent platform
  4. Ensure you have access to your project’s specification documents and implementation plans
  5. Configure the skill with your team’s code review standards and architectural guidelines
  6. Test the skill on a sample implementation plan to verify it’s working correctly

Use Cases

  • Pre-commit Review: Evaluate implementation plans before code is written to catch misalignment with specs early and reduce review cycles
  • Architectural Validation: Verify that proposed implementations follow established patterns and don’t violate system design constraints
  • Cross-functional Alignment: Help product managers and designers review technical implementation plans without needing deep code knowledge
  • Risk Assessment: Identify potential issues, performance concerns, or security implications in implementation approaches before development begins
  • Knowledge Documentation: Create structured feedback that serves as documentation for why certain technical decisions were made and what alternatives were considered

How It Works

Review-Implementing operates by systematically comparing implementation plans against multiple dimensions of specification requirements. The skill analyzes the proposed code structure, identifies dependencies, validates against documented APIs and data models, and checks for adherence to established patterns and conventions. It maintains a mental model of the project’s architecture and constraints, allowing it to spot conflicts or deviations that might not be obvious in isolation.

The skill uses a structured evaluation framework that examines: functional correctness (does the implementation achieve the intended outcome?), specification alignment (does it match documented requirements?), architectural compatibility (does it fit the existing system design?), and quality standards (does it follow code conventions and best practices?). Rather than just approving or rejecting plans, it provides detailed feedback identifying specific areas of concern and suggesting alternative approaches when misalignment is detected.

When integrated into AI agent workflows, Review-Implementing can be chained with other skills to create feedback loops where implementation plans are revised, re-evaluated, and refined until they achieve full specification alignment. This enables iterative planning that’s faster than traditional code review cycles while maintaining quality standards.

Pros and Cons

Pros:

  • Catches specification misalignment early, before development starts, reducing costly rework
  • Provides structured, documented feedback that serves as decision rationale and knowledge base
  • Scales code review across distributed teams without requiring synchronous meetings
  • Makes technical review accessible to non-engineers through clear, translated explanations
  • Integrates seamlessly into AI agent workflows for automated, iterative planning cycles
  • Creates reusable evaluation framework that standardizes review quality across projects

Cons:

  • Requires clear, detailed specifications to be effective—works poorly with vague or incomplete requirements
  • May miss subtle architectural issues that require deep domain knowledge of the codebase
  • Doesn’t replace human judgment for trade-off decisions between competing design approaches
  • Feedback quality depends on how well team standards and constraints are documented
  • Can introduce delays if overused as a gate before human review rather than enhancing it
  • Requires initial setup investment to configure project-specific standards and patterns
  • Code Architecture Validator: Analyzes codebase structure and ensures new implementations maintain architectural integrity
  • Specification Writer: Helps create clear, detailed technical specifications that Review-Implementing can evaluate against
  • Dependency Mapper: Identifies component relationships and potential conflicts before implementation begins
  • Performance Analyzer: Evaluates whether proposed implementations meet performance requirements and constraints
  • Risk Assessment Tool: Works alongside Review-Implementing to identify broader project and technical risks

Alternatives

  • Traditional Code Review Processes: Manual peer review of finished code is thorough but occurs later and is more expensive to fix issues
  • Linters and Static Analysis Tools: Catch syntax and style issues but don’t evaluate high-level alignment with specifications or architectural fit
  • Design Review Meetings: Structured discussions about implementation plans provide human judgment but don’t scale across distributed teams and lack systematic documentation
Glossary

Key terms

Implementation Plan
A detailed proposal describing how code will be structured, what components will be created or modified, dependencies between components, and the technical approach to achieving specified functionality. It's the bridge between requirements and actual code.
Specification Alignment
The degree to which a proposed implementation matches documented requirements, APIs, data models, and functional specifications. Perfect alignment means the implementation fulfills all stated requirements without adding unspecified features.
Architectural Fit
Whether a proposed implementation follows established patterns, respects system boundaries, maintains separation of concerns, and adheres to documented architectural principles. Good architectural fit ensures changes integrate smoothly with existing systems.
Code Review Cycle
The iterative process of submitting code for review, receiving feedback, making revisions, and resubmitting until approval. Review-Implementing aims to reduce cycle time by catching issues earlier, during planning rather than implementation.
Specification Gap
Areas where documented specifications are incomplete, ambiguous, or missing information needed to evaluate an implementation. The skill identifies these gaps so teams can resolve them before development begins.
FAQ

Frequently Asked Questions

How does Review-Implementing differ from code review tools like Reviewers or Linters?

Review-Implementing evaluates implementation *plans* before code is written, focusing on alignment with specifications and architectural fit. Traditional code review tools check finished code for syntax, style, and common bugs. This skill operates earlier in the workflow, during planning, and answers 'should we build it this way?' rather than 'is this code correct?'

What specifications does the skill need to work effectively?

The skill works best with clear technical specifications that include: functional requirements, API contracts, data models, architectural constraints, performance requirements, and any relevant design patterns or conventions. It can work with partial specifications but will flag areas where it lacks sufficient detail to evaluate the implementation plan.

Can non-technical team members use this skill?

Yes. While it evaluates technical implementation plans, the skill translates its findings into clear explanations of what the implementation does, how it aligns with requirements, and potential risks. Product managers and designers can review the skill's output to understand whether proposed implementations match the intended functionality without needing to read code.

How does Review-Implementing handle edge cases or ambiguities in specs?

The skill flags areas where specifications are ambiguous or where implementation plans make assumptions about unspecified behavior. It documents these gaps clearly and suggests questions the team should resolve before implementation begins, helping prevent scope creep and misaligned development.

What happens if the implementation plan contradicts the spec?

The skill provides detailed feedback identifying the specific contradictions, explains why the deviation matters, and suggests alternatives that would satisfy both the specification requirements and the implementation's underlying goals. This becomes valuable context for team discussions about whether specs need updating or implementations need adjusting.

Can this skill integrate with existing development workflows?

Yes. The skill is designed to be chainable in AI agent workflows and can integrate with project management tools, documentation systems, and code repositories. It can consume implementation plans from planning documents, pull requests, or design proposals, and output structured feedback that feeds into development tracking systems.

How comprehensive is the review?

Review-Implementing provides a comprehensive assessment across functional correctness, architectural alignment, specification compliance, and quality standards. However, it doesn't replace human review—it enhances it by providing structured analysis that human reviewers can build upon, particularly valuable for distributed teams and asynchronous workflows.

What's the typical output format?

The skill produces structured feedback including: a summary of alignment status, detailed findings organized by evaluation dimension, specific recommendations for improvement, flagged risks or concerns, and confidence ratings for different aspects of the review. This can be formatted as markdown, JSON, or integrated directly into your team's documentation systems.

More in Productivity

All →
Productivity

outline

Search, read, create, and manage documents in Outline wiki instances (cloud or self-hosted).

sanjay3290
Productivity

google-workspace-skills

Suite of Google Workspace integrations: Gmail, Calendar, Chat, Docs, Sheets, Slides, and Drive with cross-platform OAuth.

sanjay3290