manual_slop/conductor/directives/stub_before_implement/meta.md

stub_before_implement

v1

Why this iteration: Lifted from docs/MMA_Support/Tier2_TechLead.md:39-46 (the "Contract-First Delegation (Stub-and-Resolve)" section) — Tier 2 "splits requirement into a Stub Ticket, Consumer Ticket, and Implementation Ticket," spawns a cheap contract_stubber, regenerates the skeleton, then runs Consumer and Implementer in parallel. The principle name is "Force Interface-Driven Development (IDD) to prevent hallucination." Source: docs/MMA_Support/Tier2_TechLead.md:39-46

---

Lifted: 2026-07-02 (scavenge pass — directive library expansion from unread markdown in docs/MMA_Support/)