workflowlisted

# Workflow ## Iron Law `COMPLEXITY IS THE ENEMY: KEEP SOFTWARE SIMPLE ENOUGH TO UNDERSTAND, CHANGE, AND PROVE.` ## When to Use - When Consult skills are installed, use this first for almost every software engineering task. Feature work, bug fixes, scaffolding, refactoring, debugging, UI work, tests, docs, config, CI, dependencies, architecture, integrations, APIs, services, web apps, and read-only code questions all qualify unless they are truly trivial. - Work that changes or reviews behavior, domain/data models, interfaces, application architecture, tests, docs, security, reliability, performance, database behavior, or release readiness. - Read-only investigation, research, or review when the answer will shape later application engineering work. ## When NOT to Use - A narrower skill is explicitly requested and fully covers the task. - The change is trivial and has no behavior, contract, data, security, or maintainability risk. - The work is mainly DevOps/platform operations with no software design, code, contracts, or proof question. ## Core Ideas 1. **Simple Made Easy is the Consult lens.** Complexity creates bugs, misunderstanding, and inefficiency in larger software projects. Prefer simple designs that separate concerns, make state and effects explicit, and reduce what future maintainers must hold in their heads. Do not confuse easy-to-type, familiar, or quick-to-generate with simple. 2. **The human must keep owning the system.** Non