bottle-note

Incremental feature implementation across any language/stack. Trigger: "/implement", or when the user says "API 추가", "기능 구현", "기능 개발", "feature implementation", "build this". Branches on project type (web-api / cli / batch / library) and language (java-spring / python / go / ...) via arguments and references. Enforces Task / Slice / Commit 3-level granularity. For test implementation, use /test after this skill completes.

Systematic root-cause debugging for build failures, test failures, and runtime errors. Trigger: "/debug", or when the user says "에러 났어", "테스트 실패", "빌드 안 돼", "왜 안 되지", "debug this", "this is broken". Follows a structured 6-step process: STOP, REPRODUCE, LOCALIZE, FIX, GUARD, VERIFY. Use when anything unexpected happens — do not guess at fixes.

Clarifies requirements before any code is written. Creates a plan document with assumptions, success criteria, and impact scope. Trigger: "/define", or when the user says "이거 구현해줘", "기능 추가", "요구사항 정리", "define requirements", "spec this". Use when starting a new feature, when requirements are vague, or when the scope of a change is unclear. Do NOT write code during this skill — the output is a plan document, not implementation.

Diagnoses where in the GSL lifecycle the work currently is, proposes the single next command, and may auto-trigger ONLY read-only verification (never any write). Trigger: "/next-flow", or when the user says "다음 단계", "이제 뭐 해야 해", "next step", "what's next". Use after completing any GSL step (`/define`, `/plan`, `/implement` Task, `/test`, `/verify`, `/debug`) to find out what to do next. Strictly read-only: this skill never writes files, edits code, or modifies plan documents.

Breaks work into ordered, verifiable tasks with acceptance criteria. Trigger: "/plan", or when the user says "계획 세워줘", "태스크 분해", "plan this", "break it down". Use after /define when requirements are clear and a plan document exists. Adds the Tasks section to an existing plan document created by /define.

Scans a project ONCE to discover its real conventions (directory layout, naming, build system, test patterns, error model) and writes a single artifact for downstream GSL steps to consult. Trigger: "/scan-conventions", or when the user says "관습 파악", "프로젝트 스캔", "scan conventions", "convention discovery", "preflight". Use on project entry, or when conventions have drifted significantly from the existing artifact. Other GSL skills (`/define`, `/implement`, `/test`) consult the artifact at their Phase 0 — they do not re-scan.

Pre-commit quality gate with 5-axis code review. Trigger: "/self-review", or when the user says "리뷰해줘", "review this", "코드 리뷰", "self review". Use before every commit, after completing a Task in /implement, or when the user wants to review changes. Evaluates code across correctness, readability, architecture, security, and performance.

Test implementation guide across any language/stack. Trigger: "/test", or when the user says "테스트 작성", "테스트 구현", "테스트 추가", "write tests", "implement tests". Branches on language via argument and references. Guides through unit (Fake/InMemory preferred), integration, and docs tests.

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 "기능 정의", "스펙 작성", "요구사항 정리".

Bottle Note Product(사용자향) API 명세를 조회하는 레퍼런스 스킬. API 문서(https://bottle-note.github.io/bottle-note-api-server/bottle-note/product-api/product-api.html) 기반으로 엔드포인트 스펙(method, path, request/response 스키마)을 제공한다. 트리거: (1) "product API", "프로덕트 API", "사용자 API" 등 명시적 요청 (2) 프론트엔드 API 구현 전 스펙 확인이 필요할 때 (3) "리뷰 API", "위스키 API", "마이페이지 API" 등 도메인별 요청 (4) "bottlenote-product-api" 언급 시