Writing Software

Overview

Use this as the default software-engineering skill when no narrower skill dominates. Keep changes small and reversible. Scale planning and proof to actual behavior and operational risk.

When to Use

• Designing or reshaping a code change before editing
• Starting a new subsystem, service, workflow, or greenfield project
• Refactoring complexity, duplication, or interface problems
• Deciding naming, validation, or compatibility boundaries
• Planning a larger change into small vertical slices
• Creating a durable implementation or refactor plan from a known requirement

When Not to Use