Software Engineering Flow

Overview

Use this as the first engineering router. Keep it short: pick the right narrower skill, then execute. For GPT-5.6, keep prompts outcome-first: name the goal, success evidence, important constraints or approval boundaries, and stop condition; let the narrower skill choose routine steps. Preserve required evidence and artifacts. Prefer a small task-specific structure over generic brevity rules or an always-on response template.

When to Use

• Software-engineering planning, research, edits, reviews, debugging, or verification
• New features, new codebases, existing complex codebases, refactors, CI, tests, and deploy-readiness work
• Any task where code, architecture, runtime behavior, or verification is the main subject

When Not to Use

• Marketing, SEO, finance, docs-only prose, or simple shell lookups
• Non-engineering work where another domain skill is the real router