investigate

Identifies inconsistencies across specs, environments, interfaces, contracts, and assumptions, generating structured risk reports.

Updated Mar 23, 2026

Search Tags:#interfaces #reporting #spec #investigate #contracts #cross-spec

Ready to run

npx skills add https://github.com/mattphanm/Codex-Agentic --skill investigate-mattphanm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: investigate
Source: https://github.com/mattphanm/Codex-Agentic/tree/main/.codex/skills/investigate
Command: npx skills add https://github.com/mattphanm/Codex-Agentic --skill investigate-mattphanm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and surface connection points between specs, atomic specs, and master specs. Identify inconsistencies in environment variables, APIs, data shapes, and deployment assumptions before implementation.

Core Features & Use Cases

Identify cross-spec interface mismatches and dependency risks across spec groups.
Generate structured investigation reports highlighting critical, high, medium, and low risks.
Align contracts between specs to prevent integration bugs during later implementation.

Quick Start

Run /investigate with a scoped command (e.g., /investigate sg-<name>, /investigate ms-<id>, or /investigate --all) to begin an investigation and generate a report.

Frequently Asked Questions about investigate

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

FAQPage Schema

How do I check cross-spec dependencies for interface mismatches before implementation?▼

To check cross-spec dependencies, you investigate connection points between spec groups, atomic specs, and master specs to surface interface mismatches, environment variable inconsistencies, and API contract misalignments before writing any implementation code.

What is a spec investigation report and what risks does it highlight?▼

A spec investigation report is a structured document generated by analyzing connection points across specs to highlight critical, high, medium, and low integration risks including data shape conflicts and deployment assumption failures.

When do I need to run cross-spec contract alignment checks?▼

You need to run cross-spec contract alignment checks before master spec implementation, before one-off-spec implementation, and after requirements gathering to enforce API contract alignment and prevent integration bugs during later development.

How do I investigate environment variable naming conventions across multiple spec groups?▼

You investigate environment variable naming conventions by running a scoped investigation command against single spec groups, cross-spec dependencies, or master specs to enforce interface consistency and identify naming mismatches across systems.

Can I use spec investigation to find deployment assumption risks across atomic specs?▼

Yes, you can use spec investigation to identify deployment assumption risks by surfacing connection points between atomic specs and master specs, generating structured reports that prevent integration failures before implementation begins.

What is the best way to align API contracts between multiple specs?▼

The best way to align API contracts is to run a structured cross-spec investigation that surfaces connection points between systems and components, enforcing interface consistency and generating risk reports to prevent integration bugs.