interview-building-blocks
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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 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.
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-building-blocks |
| description | Funnel level 3 — identify building-block names and rough boundaries only, and run gap analysis. |
rework — modifies existing <block> and record the stakeholder's CIT-grounded reason. This is a requirements-level observation only — discovery does not touch tests. Plan reads these flags at author-test-stubs and marks the matching existing tests @pytest.mark.pending so the build backlog picks them up as rework per [[software-craft/tdd]]. A finding with no such flag is new work.