syngen

Use to verify or set up the local Syngen development environment — creates a `.venv` if missing, installs `requirements.txt`, probes runtime imports, and confirms pytest collection works. Invoke this on a fresh checkout, when pytest reports `ModuleNotFoundError`, or when `python -m build / twine / mypy` says the tool is not installed.

Use for implementing production-grade Syngen features or non-trivial code changes.

Use for selecting the correct test, lint, CI, or packaging command for a given Syngen change.

Use when a coding or testing session reveals that a harness file (rule, skill, agent, or doc) is inaccurate, incomplete, or blocking correct work. Requires human approval before any harness file is changed.

Use for marshmallow validation errors, metadata schema failures, and CLI argument validation issues in Syngen.