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:

Scope = the change directory openspec/changes/<name>/ plus delta sync targets named in this change's specs
Do NOT delete or modify files outside that scope, for any reason
Do NOT touch other in-progress changes in openspec/changes/ — they may be active work from parallel sessions
Spec sync edits ONLY sections directly affected by this change; never rewrite unrelated content
When uncertain whether a sync target belongs to this change, skip it and warn in the summary

Before launching the subagent, gather context from the current conversation:

If an OpenSpec change name exists (from a prior spec/implementation/verification):
- Pass the change name — the subagent auto-detects artifacts to archive
If user provides explicit arguments:
- Pass those directly

Brief the user, then launch Agent tool with subagent_type: "osf-archive".

Plus depuis ce dépôt

même dépôt

apply

nullmastermind/viber-router

Implement tasks from OpenSpec change or conversation plan. Use when the user wants to start implementing, continue implementation, or work through tasks.

2026-05-204

autopilot

nullmastermind/viber-router

Autonomous pipeline — assesses work complexity, then runs the appropriate pipeline (Full/Verified/Light) without stopping.

2026-05-204

chore

nullmastermind/viber-router

Execute maintenance work directly. Brief mini-plan, then carry out the change.

2026-05-204

clean-room

nullmastermind/viber-router

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.

2026-05-204

explore

nullmastermind/viber-router

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.

2026-05-204

nullmastermind/viber-router

Execute UI/UX work directly (refine UI, optimize, fix UX). Reads or bootstraps the project's UI DNA before any change.

2026-05-204

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:

Scope = the change directory openspec/changes/<name>/ plus delta sync targets named in this change's specs
Do NOT delete or modify files outside that scope, for any reason
Do NOT touch other in-progress changes in openspec/changes/ — they may be active work from parallel sessions
Spec sync edits ONLY sections directly affected by this change; never rewrite unrelated content
When uncertain whether a sync target belongs to this change, skip it and warn in the summary

Before launching the subagent, gather context from the current conversation:

If an OpenSpec change name exists (from a prior spec/implementation/verification):
- Pass the change name — the subagent auto-detects artifacts to archive
If user provides explicit arguments:
- Pass those directly

Brief the user, then launch Agent tool with subagent_type: "osf-archive".