메뉴
Implements an approved plan from docs/plans and tracks phase completion.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ad-hoc Pull Request Publisher — commits the current changes, pushes the branch, opens a GitHub pull request against the repository's default branch, and creates a matching SSP Jira issue in the current sprint following the ad-hoc work convention (summary = PR title + " #<PR number>", PR link in the "Merge Request" field, no description, moved to In Progress). Works for any ad-hoc change — fixes, small improvements, tooling, docs. Use when the user asks to publish/ship the current work end-to-end, or invokes /adhoc-pr.
Generates a PR description focused on business value using the project's PR template. Analyzes branch changes and writes a clear, user-facing explanation of what changed and why. Use when the user asks to create/write/generate a PR description, or invokes /pr-description.
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :)
Locates files, directories, and components relevant to a feature or task. Call `codebase-locator` with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
codebase-pattern-finder is a useful subagent for finding similar implementations, usage examples, or existing patterns that can be modeled after. It will give you concrete code examples based on what you're looking for! It's sorta like codebase-locator, but it will not only tell you the location of files, it will also give you code details!
Coding principles and conventions for the Shopsys monorepo — DRY/KISS/reuse, comment and docblock quality, test-code rules, the per-folder visibility/typing rules (packages vs project-base vs utils), and documentation best practices. Read it before writing or modifying PHP so your code matches the codebase.
| name | implement-plan |
| description | Implements an approved plan from docs/plans and tracks phase completion. |
The canonical instructions are authored from the project perspective. Read them:
project-base/.agents/skills/implement-plan/SKILL.mdThis skill is process-only, so no monorepo-vs-project path/architecture delta applies — docs/plans/ and the verification commands are the same here. The one thing to carry over from .agents/skills/monorepo-vs-project/SKILL.md: where the plan you are implementing places new business logic, follow package-first (it belongs in packages/, not project-base/).