원클릭으로
implement-plan
Standard workflow to implement a plan. Use only when user instructs or other skill references.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Standard workflow to implement a plan. Use only when user instructs or other skill references.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Manage interactive or persistent terminal sessions. Must use before running these sessions, like start a dev server, SSH, REPL, ...
Guidelines to help you write code smartly by using workers. Only use
Disciplined diagnosis loop for hard bugs and performance regressions. Use only when user instructs or other skill references.
Workflow to transform vague ideas into validated designs and stepped implementation plans. Use only when user instructs or other skill references.
Review a plan before implementation. Use only when user instructs or other skill references.
Inspect Git history and uncommitted changes to obtain delta in blueprint.
| name | implement-plan |
| description | Standard workflow to implement a plan. Use only when user instructs or other skill references. |
| disable-model-invocation | true |
You will be responsible for the entire implementation of a specific plan. Every implementation based on a plan in plans/ should go through the audit - implement - review workflow as follows. Maximize rigorousness and future maintainability.
Without reading the plan, delegate an Oracle agent with exact prompt (no need to follow format): Use "audit-plan" skill to audit <plan-file-path>.
You must use smart-delegation skill, following the guideline to complete the work with maximum quality and quality.
Resume the same Oracle session as in step 1: Now the implementation is finished, review using "review-implementation" skill.
If the Oracle rejects, fix the raised issue, and request review again: All raised issues are addressed, restart review.
When the Oracle says the review passes but asks for simplification. You must simplify all the points it raises. When simplification is done, proceed to next step, no need to review again.
Present a implementation summary to the user.