investigate_skill

This skill analyzes connections between specs, surfaces inconsist inconsist in env vars, APIs, data shapes, and deployment assumptions before implementation.

TypeScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill matthew-plusprogramming/monorepo --skill investigate

SKILL.md8.8 KB

Overview

This skill investigates connection points between spec groups, atomic specs, and master specs to surface inconsistencies before implementation. It finds mismatched env var names, API endpoint disagreements, data-shape conflicts, and deployment assumption drift. The goal is to block risky implementations and produce concrete decisions and canonical contract recommendations.

How this skill works

You provide a scope (one or more spec groups, a master spec, or all active specs) and the skill inspects declared inputs/outputs, environment variables, API endpoints, data shapes, and deployment assumptions. It produces a structured investigation report with a connection map, severity-ranked inconsistencies (Blocker/High/Medium/Low), decisions required with options, and recommended canonical contracts. The report also indicates whether implementation can proceed or is blocked until decisions are resolved.

When to use it

Before implementing a MasterSpec or any coordinated workstreams
When one spec group will depend on outputs from another
After manual review uncovers conflicting assumptions
After requirements gathering to catch early assumption gaps
Before atomizing a parent spec into atomic specs

Best practices

Run investigation as a mandatory gate before multi-workstream implementation
Scope investigations narrowly at first, then re-run with cross-spec mode if needed
Document canonical decisions in a shared contracts location to prevent repeat conflicts
Include env var templates and explicit API shapes in specs to make investigations faster
Resolve blockers before merging implementation changes

Example use cases

Investigate ms-auth-system to surface mismatched session and auth assumptions across workstreams
Compare two spec groups that will be integrated by a downstream service to find missing env vars or differing data fields
Run cross-spec investigation to reconcile SSH/key handling and container image naming conventions
Validate that a monitoring workstream declares the same runtime secrets as a build workstream before deployment
Generate decision record items (DEC-xxx) to drive spec updates and team alignment

FAQ

It expects spec groups and master specs with declared interfaces, env var templates, and API endpoint definitions; the minimum requirement is at least one spec group with documented interfaces.

Can it investigate across many spec groups at once?

Yes — use the cross or all modes to include multiple spec groups and surface cross-spec dependencies and conflicts.

What happens if blockers are found?

The report marks implementation as blocked, lists blockers and decisions required, and recommends updating specs and re-running the investigation after resolutions.