backend-planning
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
More from ywj3493/claude-skills
new-policy
Creates a new policy document in docs/en/policy/ with the standard format, and simultaneously creates its Korean translation in docs/ko/policy/. Use this when the team needs to establish a new working rule or standard. Triggered by "add a policy", "create a policy for X", "새 정책 만들어줘", "규칙 문서화", or describing a convention that needs to be formalized.
23new-issue
Creates a new issue for tracking work. When a git remote exists, creates a GitHub Issue via `gh` CLI, sets up a working branch, and opens a draft PR linked to the issue. When no remote is configured, falls back to creating local issue documents in docs/en/issue/ with Korean translations. Use this whenever starting new work — features, bug fixes, tasks, or investigations. The user may say "create an issue", "new issue", "이슈 만들어줘", or simply describe work they want to start.
21init-docs
Initializes the standard docs/ directory structure for a new project. Creates docs/en/{specifications,issue,policy}/, docs/ko/{specifications,issue,policy}/, and docs/reference/, seeds initial policy documents in both English and Korean, and places a CLAUDE.md in the project root. Use this when starting a fresh project that should follow the standard documentation system.
19sync-dev
Audits docs/specifications/, docs/issue/, and docs/policy/ for English documents that are missing a Korean translation in docs/dev/, or where the Korean version appears out of date compared to the English source, then creates or updates those translations. Use this to keep docs/dev/ in sync. Triggered by "sync docs", "번역 동기화", "update translations", "sync dev", or "mirror docs".
10sync-translations
Audits docs/en/specifications/, docs/en/issue/, and docs/en/policy/ for English documents that are missing a Korean translation in docs/ko/, or where the Korean version appears out of date compared to the English source, then creates or updates those translations. Use this to keep docs/ko/ in sync. Triggered by "sync docs", "번역 동기화", "update translations", "sync translations", or "mirror docs".
10frontend-planning
[DEPRECATED] Use dev-planning instead. Former 6-step frontend planning pipeline.
10