eigi-scope-discipline

Keeps Eigi planning and implementation scoped to what is actually required, with every addition beyond the source requirement tagged and listed for approval. Use whenever writing or reviewing a PRD, TRD, ADR, data model, schema, implementation plan, migration plan, ticket breakdown, or the code that follows from them. Use it even when the user only says "write the data models", "plan this out", "break this into tasks", or "build this feature" without mentioning scope — this skill decides what goes in and what gets flagged instead of built. Apply alongside eigi-backend-standards and eigi-frontend-standards, which govern how the in-scope work is structured.