dev-planning

Unified planning document pipeline for all project types, organized by domain. The first 4 steps are shared across all domains. Step 5 branches by domain type. Step 6 generates a test specification referencing IDs from all previous steps.

When to Use

• User says "기획", "planning", "설계", "plan backend", "plan frontend", "plan infra"
• User says "기획 문서", "기획 문서 만들어줘", "dev planning", "API 설계", "UI 설계"
• Starting a new project that needs structured design documents
• Adding a major feature that requires multi-document planning

When NOT to Use

• Fixing a single endpoint, component, or small tweak
• Editing or updating existing specification documents
• Work that doesn't need multi-document planning