메뉴
Create or update risk assessment document from template
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
One-command project setup for OpenUP - interactive initialization wizard
Mark a task as complete, update roadmap, commit changes, and prepare traceability logs
Execute an already-claimed lane's Operations boxes with script/judgment classification — script steps run directly with zero self-brief, judgment steps self-brief and execute. Handles only pick/resume; every other resolve path routes to /openup-next.
Run OpenUP Assess Results at iteration end — check evaluation criteria, demo only completed acceptance-tested work, feed discovered work back, and trigger the milestone review at a phase boundary
Run the phase milestone go/no-go — prepare derived evidence, pause for the human decision via an input-request, and record the milestone (never advance the phase itself)
Begin a new OpenUP iteration with proper phase context and task selection
| name | openup-create-risk-list |
| description | Create or update risk assessment document from template |
| model | sonnet |
| arguments | [{"name":"risks","description":"JSON array of risks to add (optional)","required":false}] |
This skill creates or updates a risk list document from the OpenUP template.
Use this skill when:
Do NOT use this skill when:
After using this skill, verify:
docs/risk-list.mdIf docs/project-config.yaml exists, apply it before drafting (skip if
absent): inject its context: as <project-context> and its rules.risk-list
as <project-rules>, then confirm every injected rule holds before marking
the artifact complete. Rules are additive — they may add but never waive a
framework criterion. Full mechanism + precedence (the single source):
docs-eng-process/project-config.md.
Check if docs/risk-list.md exists:
If creating new, copy docs-eng-process/templates/risk-list.md to docs/risk-list.md
Read docs/project-status.md, docs/vision.md to identify potential risks.
Update with:
$ARGUMENTS[risks] or identify from project context
For each risk, document:
Apply the Self-Critique SOP (docs-eng-process/sops/self-critique.md) before
validating: take a hostile-reviewer stance, surface every load-bearing
assumption into the list, and confirm each risk has a concrete trigger and a
mitigation you could actually verify was carried out — not a restatement of the
risk itself. List every weakness you find — including ones you are uncertain about — then fix or explicitly flag each one. Rank them and record the top one or two with their resolutions.
Re-check every item in Success Criteria (top of this skill) against the document you produced; fix any gap before returning.
Returns:
| Error | Cause | Solution |
|---|---|---|
| Template not found | Template path incorrect | Verify docs-eng-process/templates/risk-list.md exists |
| No risks identified | Project context insufficient | Review vision and requirements for potential risks |
| Missing mitigation | Risks documented without mitigation | Add mitigation strategy for each risk |
docs-eng-process/templates/risk-list.mddocs-eng-process/openup-knowledge-base/practice-management/risk_val_lifecycle/docs-eng-process/openup-knowledge-base/core/role/roles/project-manager-4.md