bottle-note-api-server

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.

Local CI verification skill with 3 levels (L1 quick / L2 standard / L3 full). Trigger: "/verify", "/verify quick", "/verify l1", "/verify standard", "/verify l2", "/verify full", "/verify l3", or when the user says "검증해줘", "빌드 확인", "테스트 돌려줘", "CI 돌려봐", "run checks". Always use this skill when the user wants to check if their code compiles, passes tests, or is ready for PR. Branches on language via reference. Always runs against the ENTIRE project (modules can depend on each other).

배치 모듈 배포. "배치 배포", "batch deploy", "배치 이미지 올려줘" 요청 시 사용. 단계별 스크립트로 구성되어 개별 테스트 가능.