メニュー
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
Implement tasks from OpenSpec change or conversation plan. Use when the user wants to start implementing, continue implementation, or work through tasks.
Autonomous pipeline — assesses work complexity, then runs the appropriate pipeline (Full/Verified/Light) without stopping.
Execute maintenance work directly. Brief mini-plan, then carry out the change.
Port a feature from an external git repo into the current project. Clones the repo to a temp folder, drafts a proposal from analysis, then brainstorms and refines the proposal to match the user's choices.
Shared explore/plan mode behavior for all planning commands (feat, fix, chore, refactor, perf, docs, test, ci, docker). Provides the stance, continuous verification, fluid workflow, subagent protocols, OpenSpec awareness, and guardrails.
Execute UI/UX work directly (refine UI, optimize, fix UX). Reads or bootstraps the project's UI DNA before any change.
| name | archive |
| description | Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. |
SCOPE DISCIPLINE
Parallel sessions may share this branch. When briefing osf-archive, include these rules verbatim:
openspec/changes/<name>/ plus delta sync targets named in this change's specsopenspec/changes/ — they may be active work from parallel sessionsBefore launching the subagent, gather context from the current conversation:
Brief the user, then launch Agent tool with subagent_type: "osf-archive".