القائمة
Conduct an in-depth structured interview with the user to uncover non-obvious requirements, tradeoffs, and constraints, then produce a detailed implementation spec file.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Creates a new git branch following the project's branch naming convention. Use this skill whenever the user wants to start new work, create a branch, switch to a new branch.
Generate PR title and body from commits since the base branch, then create the PR on GitHub following the project PR template exactly.
Check PR review comments, reflect valid feedback into code, commit, push, then reply to each comment with the resolving commit hash.
Create Git commits following Flooding project conventions. Splits changes into logical units with correct type prefix and Korean description.
Run a structured checklist over changed files — Kotlin style, JPA/transaction correctness, naming conventions, test coverage, and security basics. Produces a ✓/⚠/✗ report.
Run KtLint formatting on all Kotlin source files via Gradle. Use when .kt files need formatting or after bulk edits.
| name | plan-deep-dive |
| description | Conduct an in-depth structured interview with the user to uncover non-obvious requirements, tradeoffs, and constraints, then produce a detailed implementation spec file. |
Interview the user in detail about the requested feature or task — cover technical implementation, architecture decisions, edge cases, tradeoffs, and concerns. Ask non-obvious, in-depth questions. Continue interviewing until you have enough information, then write the complete spec to a file named SPEC.md.
Cover at minimum:
