backend-planning

5-step planning document pipeline for backend projects, organized by domain.

When to Use

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

When NOT to Use

• Frontend-only projects (use the frontend planning pipeline instead)
• Fixing a single endpoint or small API tweak
• Editing or updating existing specification documents
• Non-backend work such as CI/CD, infrastructure, or tooling

Pipeline Overview