Menu
Pull the next source contract to build from the pending backlog, respecting outside-in dependency order.
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
| name | select-build-target |
| description | Pull the next source contract to build from the pending backlog, respecting outside-in dependency order. |
feature/<session_id>: if absent, branch it off dev (git checkout -b feature/<session_id> dev); if it exists (resumed cycle), check it out. The contract surface was committed to dev at plan, so the branch starts from it.uv run pytest --collect-only -m pending -q). Map each pending test to the source module it exercises.uv run python scripts/strip_docstrings.py <package>/<module>.py. Skip if absent (new contract).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.