메뉴
Shared support references for the rolling-wave engineering skill set. Use only when a rolling-wave workflow skill explicitly points here, or when maintaining the shape-project, prepare-next-slice, implement-slice, review-slice, and complete-slice skills.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Relentlessly pressure-test an existing plan or design artifact until every material branch is resolved, explicitly deferred, or ruled out. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, or similar decision document; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.
Shape or update a rolling-wave engineering project before slice preparation. Use when the user wants to start a rolling-wave project, define the finish line, clarify success criteria, create or update docs/rolling-wave/{project}/project.md, sketch a broad roadmap, or interrogate project-level direction without implementation details.
Review changed code for YAGNI, removable over-complexity, reuse, code quality, and efficiency, then apply worthwhile simplifications. Use when the user asks to simplify, clean up, tighten, de-hack recent changes, identify logic that can be dropped, or review whether added safeguards and edge-case handling are actually needed.
Complete a reviewed rolling-wave slice after user review. Use when the user says a slice is done, wants to mark an in-review slice done, capture implementation and review learnings, update docs/rolling-wave/{project}/project.md potential risks and review notes, output a roadmap progress checklist of completed and remaining slices, and prepare later slices to inherit what was learned.
Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.
Implement a ready rolling-wave slice without locking it down with tests yet. Use when the user explicitly wants to code the current docs/rolling-wave/{project}/slices/NNN-slug.md slice, mark it in progress, execute the prepared parallel work chunks with one implementation subagent per agent-fit chunk where available, pause or hand off chunks marked human-fit when appropriate, record implementation notes, defer test-writing to implement-tests, and preserve the original slice contract for review.
| name | rolling-wave-common |
| description | Shared support references for the rolling-wave engineering skill set. Use only when a rolling-wave workflow skill explicitly points here, or when maintaining the shape-project, prepare-next-slice, implement-slice, review-slice, and complete-slice skills. |
This is a support skill for the rolling-wave skill set. It is not a user-facing workflow entry point.
Use these references when maintaining or executing the phase skills:
references/artifacts.md: project and slice artifact templates.references/lifecycle.md: status ownership and transition rules.references/pushback.md: shared evidence-based pushback standard.Each phase skill still duplicates the short core invariants in its own SKILL.md so it can operate in fresh context. Load these shared references only when detailed templates or transition rules are needed.