메뉴
Implementation rules: only implement what is in PRD/design/implement scope. Don't expand scope. Don't commit. If design gaps are found, return to planning. Output changed files, summary, validation attempted, and unresolved risks.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | trellis-implement |
| description | Implementation rules: only implement what is in PRD/design/implement scope. Don't expand scope. Don't commit. If design gaps are found, return to planning. Output changed files, summary, validation attempted, and unresolved risks. |
in_progress.Only implement what is in the PRD, design, and implement scope. Do not expand scope. If you discover something that should be done but is not in scope, record it as a follow-up, not as an implementation addition.
Do not commit. Commits happen in Phase 3.2 after spec update decision and review gates pass.
If you find a design gap — something the PRD or design did not account for that affects implementation — do NOT guess. Return to planning. Record the gap and request clarification or a PRD/design update.
If you are already running as a trellis-implementer sub-agent, implement directly. Do NOT spawn another implement sub-agent.
implement.md steps.implement.md as you complete each step.The subagent-stop-guard validates this output format. It must contain all four
summary sections plus an explicit no-commit confirmation. The implementer must
also write {TASK_DIR}/agent-results/trellis-implementer-<timestamp>.json.
## Implementation Summary
### Changed Files
- [file path]: [what changed and why]
- [file path]: [what changed and why]
### Summary
[1-3 sentences on what was implemented]
### Validation Attempted
- [command]: [result]
- [command]: [result]
### Unresolved Risks
- [risk]: [why unresolved, recommended next step]
- (or "none" if all risks are resolved)
### Did Not Commit
- Did not commit: yes
Required agent-result JSON fields: version, agent, status,
object-shaped changed_files, validation, and blocking_issues.
agent-results/trellis-implementer-<timestamp>.json exists and uses the required schema.Read all task artifacts and specs before writing code. Outputs implementation constraints. Use after task.py start and before any source editing — the before-dev gate is mandatory and blocks code changes until satisfied.
Quality verification: git diff/status, lint, type-check, tests, no debug logs, no suppressed errors, no unsafe type bypass. Deep check for L4/L5 adds spec compliance, cross-layer data flow, API/schema/type consistency, and code reuse. Outputs PASS/FAIL with blocking issues.
Review dependency direction, module boundaries, abstraction quality, duplicated concepts, layering violations, shared utility misuse, API contract clarity, and future extensibility. Outputs to review/architecture-review.md with PASS/FAIL. Required for L4/L5 tasks.
Review code for correctness, readability, maintainability, error handling, performance, tests, security, and unnecessary complexity. Outputs to review/code-review.md with PASS/FAIL, separating blocking from non-blocking issues. Use as a review gate when selected in the Review Gate Contract.
Decide execution mode, branch strategy, TDD approach, review gates, and architecture guidance for the task. Outputs Development Strategy and Review Gate Contract to implement.md. Use during Phase 1.4 after PRD and design are complete.
Finalize a completed task: verify gates passed, archive task, update workspace journal, update task index, summarize commits/PR, record follow-ups, and mark task done. Does NOT write code, fix bugs, bypass failed gates, or auto-push. Rejects if preconditions are not met.