smart

Implement a feature unit with TDD and Korean pseudocode comments for easy review

Create a PRD (Product Requirements Document) for a new project

Plan a feature with multi-agent analysis, decomposition, and implementation plans

Review implemented code against the plan with 3 parallel analysis agents

Define technical specifications and feature list for the project

Implement a feature unit with TDD and Korean pseudocode comments for easy human review. Reads IMPL_PLAN documents, writes tests first, then implements with Korean pseudocode as inline comments. Use this skill whenever the user says "구현 시작", "구현해줘", "코드 작성", "implement", "start coding", "build this", "개발 시작", "코딩 시작", or wants to begin implementing a planned feature. Always use this skill when the user wants to start coding after planning is complete.

Create a PRD (Product Requirements Document) for a new project. Generates docs/PRD.md with project overview, core goals, functional/non-functional requirements, constraints, and success metrics — excluding all visual/UI content. Use this skill whenever the user says "프로젝트 시작", "새 프로젝트", "프로젝트 초기화", "project init", "new project", "start a project", "PRD 작성", or describes a new project idea and needs to formalize requirements. Always use this skill proactively when a new project discussion begins, even if the user hasn't explicitly asked for a PRD.

Plan a feature with multi-agent risk analysis, architecture review, and implementation plans. Generates docs/FEATURE_PLAN.md (feature decomposition into big/small logical units) and docs/IMPL_PLAN_*.md (Korean pseudocode implementation plans per small unit — no real code). Use this skill whenever the user says "기획", "계획 세워줘", "어떻게 구현할까", "설계해줘", "플랜 짜줘", "기능 분해", "구현 계획", "feature plan", "let's plan", "before we implement", or describes a feature and asks how to approach it. Always use this skill proactively when a non-trivial feature discussion begins, even without explicit request.

Review implemented code against the plan using 3 parallel agents — checking plan-implementation alignment, code quality/security, and test coverage/performance. Outputs a structured review report to terminal. Use this skill whenever the user says "리뷰", "검토", "코드 리뷰", "review", "code review", "검토해줘", "리뷰해줘", "코드 확인", "코드 봐줘", or wants to review implemented code, check quality, or verify implementation matches the plan. Always use this skill when the user asks to review code, even if they don't explicitly mention "review".

Define technical specifications and feature list for a project. Generates docs/SPEC.md (tech stack, architecture, directory structure, monitoring strategy) and docs/FEATURE_LIST.md (prioritized features with dependencies and MVP scope). Use this skill whenever the user says "기술 스펙", "스펙 정의", "tech spec", "기술 스택", "feature list", "기능 목록", "아키텍처 설계", "스택 정하자", or wants to make technical decisions for a project. Always use this skill proactively when technical decision-making discussion begins, even without explicit request.