ferrox-add-tests

To generate unit and end-to-end tests for completed software phases, provide phase summaries, context files, and verification documents. The skill uses these specifications to classify implementation files and deterministically produce committed test coverage with gap reporting.

You can use specification documents like SUMMARY.md, CONTEXT.md, and VERIFICATION.md to drive test creation. These files act as the source of truth for expected behavior, allowing the skill to convert finished feature phases into verified test files without reconstructing behavior manually.

Test classification separates implementation files into unit, browser e2e, or skip categories before writing any tests. This ensures deterministic RED-GREEN test generation by applying the correct testing methodology to each file based on its role in the phase.

You need approval gates to verify test generation in a phase-based build workflow. The skill enforces approval checkpoints and RED-GREEN verification to ensure test creation stays deterministic and auditable throughout the software engineering process.

The best way to automate test coverage for documented implementation phases is to use a specification-driven approach. By extracting expected behavior from documentation, the skill removes the burden of designing coverage after a phase is built and provides gap reporting for missing tests.

Test generation requires phase summaries and verification documents because they serve as the documented specifications for expected behavior. Without these inputs, the skill cannot accurately classify implementation files or produce deterministic test coverage that reflects the phase's documented promises.