om-pre-implement-spec

Analyze specifications for backward-compatibility issues and readiness gaps before implementation.

6|2|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/SHGrowth/om-superpowers --skill om-pre-implement-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-pre-implement-spec
Source: https://github.com/SHGrowth/om-superpowers/tree/main/skills/om-pre-implement-spec
Command: npx skills add https://github.com/SHGrowth/om-superpowers --skill om-pre-implement-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes a specification before implementation to identify backward-compatibility risks, gaps, and readiness, enabling teams to address issues early.

Core Features & Use Cases

  • Backward-compatibility audit across contracts and interfaces.
  • Spec completeness verification, risk assessment, and remediation planning.
  • AGENTS.md compliance checks and phased remediation guidance.
  • Cross-module exploration to surface dependencies and impact.

Quick Start

Provide the spec to be analyzed and run the pre-implementation analysis to generate a readiness report.

Frequently Asked Questions about om-pre-implement-spec

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

FAQPage Schema
How do I check a spec for backward-compatibility issues before implementation?

A pre-implementation spec analysis identifies backward-compatibility risks and readiness gaps across multiple modules, contracts, and interfaces. It audits completeness, assesses risks, checks AGENTS.md compliance, and outputs a structured readiness report.

What is backward-compatibility gap analysis in software specifications?

Backward-compatibility gap analysis in software specifications is the process of auditing contracts and interfaces to surface readiness gaps and risks before implementation. It enforces completeness checks and AGENTS.md compliance to produce a structured remediation plan.

How do I assess cross-module risks and AGENTS.md compliance in a specification?

You assess cross-module risks and AGENTS.md compliance by applying a pre-implementation analysis to the specification. This enforces a BC audit across categories, verifies completeness, and generates a final readiness report in the .ai/specs/analysis directory.

Can I generate a remediation plan for spec readiness gaps before coding starts?

Yes, you can generate a remediation plan for spec readiness gaps before coding starts. The pre-implementation analysis identifies backward-compatibility issues, verifies spec completeness, and provides phased remediation guidance in a structured report.

What are the limitations of pre-implementation spec analysis for BC readiness?

The limitations of pre-implementation spec analysis center on its scope as a readiness check rather than an implementation tool. It identifies BC risks, completeness gaps, and AGENTS.md compliance issues but does not write code or execute the remediation plan itself.