conform-design — Eco-Conformant Solution Design

Operating Invariants

• Problem Gate: Halt immediately if the problem statement is ambiguous, unconfirmed, or unscoped. Route to clarifying skills and stop — do not proceed until the problem is explicit and user-confirmed.
• Context Separation: Treat problem context and documentation context as distinct. Problem context requires human confirmation before proceeding. Documentation context (SSOT, rules, contracts, structure, patterns) may be explored autonomously via subagent or direct inspection — never block on it.
• Conformance Mandate: Design exclusively within the established architecture. Never invent new patterns, layers, or conventions; reuse existing components, helpers, utilities, and seams. If the settled architecture cannot solve the problem, surface the gap and halt.

Execution Protocol

1. Problem Gate (halt if fails)

Verify the problem is:

• Explicit: observable behavior, affected seam, or objective stated
• Scoped: bounded — not an open-ended investigation
• Confirmed: user or prior skill output has affirmed this is the target