Menu
Author the minimal authenticated probe script that exercises one success path and one error path against the real service, without executing it.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Compile the contract set in your head — simulate how the real application would run from the specs, and disprove (or confirm) it works before any source .py is written.
Author test stub files (.pyi) whose signatures express the domain, relationships, and compositions, as the first contract surface.
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.
Squash-merge the feature commits into dev, regenerate docstrings, and verify the whole suite plus whole-suite stubtest are clean.
Publish the delivered batch as release notes, a PR to main, or a tagged release.
| name | write-probe |
| description | Author the minimal authenticated probe script that exercises one success path and one error path against the real service, without executing it. |
~/.secrets/<project>.env via dotenv_values() — never load_dotenv() into os.environ (secrets stay scoped to the probe, off the process env); non-secret config (base URLs) comes from the workspace .env. Reference every secret by name; never print or log it. IF a secret the probe needs is not yet set up THEN instruct the user how to obtain and place it — do not create it. Per [[software-craft/secrets-and-config]].