메뉴
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Implement OpenSpec change using Ralph Loop - parallel specialized agents with fresh context per iteration. Use when user wants faster implementation with domain experts working in parallel, or when the change spans multiple domains (backend, frontend, database).
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Archive multiple completed changes at once. Use when the user wants to clean up several completed changes.
Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
| name | openspec-archive-change |
| description | Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. |
Archive a completed change in the experimental workflow.
When to Use
Input: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
Steps
If no change name provided, prompt for selection
python .agents/openspec_kit.py list
Show only active changes (not already archived).
IMPORTANT: Do NOT guess or auto-select. Always let the user choose.
Check artifact completion status
python .agents/openspec_kit.py status "<name>"
Parse JSON:
artifacts: List with status (done or other)isComplete: BooleanIf not complete:
Check task completion status
Read openspec/changes/<name>/tasks.md
Count: - [ ] (incomplete) vs - [x] (complete)
If incomplete tasks:
Assess delta spec sync state
Check for delta specs: openspec/changes/<name>/specs/
Compare with main specs: openspec/specs/<capability>/spec.md
Show summary of what would be synced.
Prompt options:
If user chooses sync, use openspec-sync-specs logic first.
Perform the archive
python .agents/openspec_kit.py archive "<name>"
Display summary
Show:
Output On Success
## Archive Complete
**Change:** <change-name>
**Schema:** <schema-name>
**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
**Specs:** ✓ Synced (or "No delta specs" or "Sync skipped")
All artifacts complete. All tasks complete.
Guardrails