dry-run

dynos-work: Dry Run

Validate that the contract.json files across all skills form a valid pipeline chain. This skill reads every skills/*/contract.json, determines the pipeline order, and verifies that each stage's outputs satisfy the next stage's required inputs.

Ruthlessness Standard

• Treat missing or incompatible contract fields as real pipeline breakage, not paperwork.
• Do not infer compatibility from naming similarity alone.
• If a downstream stage depends on behavior the upstream contract does not guarantee, call it broken.

What you do

Step 1 -- Discover contracts

1. Scan all directories under skills/ in the project root.
2. For each directory, check if a contract.json file exists.
3. If any skill directory lacks a contract.json, emit a warning that names every specific directory:

   WARNING: Missing contract.json in: skills/foo/, skills/bar/
   

4. Parse each discovered contract.json file. If any file contains invalid JSON, report it as an error and skip that contract.

Step 2 -- Determine pipeline order

The linear pipeline chain is fixed:

start -> plan -> execute -> audit -> learn

Skills that are NOT part of the linear pipeline (utility skills) are:

• status
• investigate
• resume
• repair
• execution
• dashboard
• dry-run

Utility skills have contracts but do not participate in linear chain validation. They should still be loaded and listed in the report.

Step 3 -- Validate chain links

For each consecutive pair in the pipeline (stage N -> stage N+1):

1. Read the output_schema of stage N.
2. Read the input_schema of stage N+1.
3. For every field in stage N+1's input_schema where required is true:
   • Check if a field with a matching key exists in stage N's output_schema.
   • If the field exists, check that the type values are compatible (exact match or both resolve to the same base type).
   • If the field is missing from stage N's output_schema, record a FAIL with details.
   • If the field exists but the type does not match, record a FAIL with details.
4. For optional fields (where required is false), check availability but only emit an INFO-level note if missing, not a FAIL.