메뉴
Execute an approved backend Work Plan autonomously through task execution, quality fixes, commits, and final verification.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/shinpr/codex-workflows --skill recipe-build명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | recipe-build |
| description | Execute an approved backend Work Plan autonomously through task execution, quality fixes, commits, and final verification. |
coding-rulestestingai-development-guidesubagents-orchestration-guidellm-friendly-contextEvery spawn_agent call uses fork_turns="none" and supplies the exact artifact paths needed by that specialist.
The orchestrator owns plan selection, approval dialogue, task-set computation, routing, commits, and completion reporting. Invoke specialist agents for task decomposition, implementation, test review, quality repair, and final verification. A user-requested plan revision follows Work Plan Approval.
Work plan: $ARGUMENTS
Apply subagents-orchestration-guide Work Plan Resolution with docs/plans/tasks/{plan-name}-task-*.md as the managed task pattern, excluding basenames that start with integration-tests-.
Report a missing Work Plan as the exact missing prerequisite.
Apply subagents-orchestration-guide Work Plan Approval. When plan-level user approval is absent or ambiguous, ask before agent invocation or task analysis:
Approve this Work Plan as the implementation scope and authorize task decomposition, implementation, quality fixes, and per-task commits?
[path]
Record approval in the plan's existing plan-level status field and proceed to Step 3. A requested change returns through work-planner and document review before this gate.
Proceed directly to task generation. Run recipe-prepare-implementation only when the user explicitly requests repository-local setup. If task-local execution later identifies a concrete missing repository capability, resolve it through Orchestrator Escalation Resolution and run the preparation side path when that is the smallest authorized resolution.
The managed set is exactly docs/plans/tasks/{plan-name}-task-*.md implementation task files, excluding basenames that start with integration-tests-. The pending set contains managed files with at least one unchecked task checkbox.
When the managed set is empty, invoke task-decomposer with the exact approved Work Plan path. Verify the generated task files, then recompute both sets. Batch approval already authorizes this decomposition. When the managed set exists and the pending set is empty, proceed to final verification.
Order pending tasks by their declared dependencies.
Use the active execution plan when one exists. When none exists, create one after the task set is known with one step per task cycle and a final verification step. Update the same plan throughout execution.
Execute each pending task through the subagents-orchestration-guide autonomous task cycle using task-executor and quality-fixer. Pass the exact task file and preserve the canonical Per-Task Change Set. After quality approval and a successful implementation commit, update the Task File, corresponding Work Plan task and phase, and execution plan locally; keep Task Files and the Work Plan outside the implementation commit.
Apply subagents-orchestration-guide Requirement Change Detection During Flow and resume from its named artifact while preserving unaffected completed work.
Apply subagents-orchestration-guide Post-Implementation Review to the actual files changed by completed tasks and their governing documents. Route required fixes through the same task cycle.
Apply a security-reviewer finding only when leaving it unresolved would violate an explicit governing requirement or repository rule, or leave a concrete material security failure in the actual reachable trust model. The violated requirement, rule, or failure defines implementation scope: route the smallest correction that resolves it, treating the reviewer's suggestion as one candidate implementation.
Remove the consumed task files after final verification and preserve the Work Plan as the progress record. A cleanup failure is reported with its exact path and leaves completed implementation valid.
Report the Work Plan path, completed tasks, commits, verification results, and any verification limitation that could not be exercised in the available environment.