Menu
Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout.
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.
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.
Close the pipeline cycle: regenerate the living spec from current tests, summarize the carry-over cache files, regenerate source docstrings then strip all .py so the next cycle starts compact.
| name | interview-general |
| description | Funnel level 1 — establish the big picture with seven broad questions, applying CIT, Laddering, and CI Perspective throughout. |
.cache/<session_id>/interview-notes.md does not exist THEN render it from .templates/cache/interview-notes.md.template (substitute <session_id>). The skeleton carries the funnel level headers only; absence on a first pass is expected — never a deliberation point. IF it exists THEN it carries the prior cycle's summarized interview (a ~1000-word summary left by refresh-cycle) — read it for continuity and append the general findings beneath the Level 1 header.