admin-dashboard

Implement Bottlenote admin dashboard features strictly from an existing docs/features/{feature-slug}/plan.md. Use when spec.md, design.md, and plan.md already exist and Codex should make code changes, update tests/mocks, run verification, and hand off manual UI review points without redefining the feature. Trigger on "plan.md대로 구현", "구현해줘", "implement this plan", or requests that provide a docs/features/{feature-slug}/plan.md path.

Create Korean pull requests for Bottlenote admin dashboard changes. Use when Codex needs to prepare or create a PR after feature work, bug fixes, API contract work, tests, or documentation changes in this repository. Trigger on requests like "PR 만들어줘", "PR 생성", "pull request 만들어줘", "한글 PR", "작업 올려줘", or when implementation is complete and the user asks to open a PR.

Create or update Bottlenote admin feature UI design docs in docs/features/{feature-slug}/design.md from an approved spec.md and existing shadcn/Tailwind admin dashboard patterns. Use when Codex needs to define route/sidebar placement, list/detail/form UI, states, validation copy, and manual UI review points before implementation planning. Trigger on design, UI structure, 화면 설계, 디자인 문서, or admin page layout requests.

Check Bottlenote admin API documentation and apply frontend API contract updates for this dashboard. Use when Codex needs to inspect admin API specs, compare docs with code, add or update endpoints, fix request/response type mismatches, or support feature spec/plan work with API field analysis. Trigger on requests mentioning Bottlenote API, admin API docs, endpoint updates, response shape changes, or code/API inconsistencies.

Route Bottlenote admin dashboard feature, bug, API, implementation, verification, and PR requests to the correct project-local skill workflow. Use when the user gives a vague or multi-stage admin request and Codex needs to decide whether to create a spec, design, implementation plan, implement from an existing plan, inspect API docs, or prepare a Korean PR. Trigger on "기능 개발", "버그 수정", "구체화", "어드민에 추가", "구현해줘", "PR 만들어줘", or similar admin workflow requests.

Create or update decision-complete implementation plans in docs/features/{feature-slug}/plan.md from Bottlenote admin feature spec.md and design.md. Use before code implementation so another agent can implement without reinterpreting product requirements or UI design. Trigger on implementation plan, 개발 계획, 구현 계획, plan.md, or requests to prepare a feature for implementation.

Create or update Bottlenote admin feature specifications in docs/features/{feature-slug}/spec.md from user intent, API documentation, response shapes, and existing dashboard behavior. Use before design, planning, or implementation for new admin pages, workflows, API-backed features, or substantial feature changes. Trigger on requests for feature definition, spec writing, requirements, acceptance criteria, or Korean requests like "기능 정의", "스펙 작성", "요구사항 정리".