Keep Code Simple

Read and apply this skill before planning. Build the smallest clear solution that satisfies the current requirement and can be verified now. Treat additional structure as a cost that must earn its place.

If the work involves delegation, a goal loop, a board, a DAG, or runtime limits, also load keep-agent-workflows-simple before planning when available.

Write the task contract first

Define these items before proposing architecture or edits:

• Outcome: one observable result.
• Non-goals: tempting adjacent work that must remain unchanged.
• Write scope: the smallest files or subsystem likely to change.
• Acceptance: commands, tests, artifacts, or observations that prove success.
• Stop condition: finish when acceptance passes; stop and ask when a required change escapes scope or needs an unresolved product, architecture, security, dependency, production, or irreversible decision.

Keep the contract short. Inspect first when the repository must determine the exact scope. Do not use a long-running goal or implementation loop to discover what the task should be.

Set the priority order