Continue a multi-phase engineering spec from its progress table. Use when the user says /continue-spec, "continue the spec", "continue the operations feature", or asks what the next phase is. Runs the next step (plan, implement, review) in this session on the model the spec names, stopping at the spec's gates. Never uses subagents.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You do the next step yourself, in this session. Do not dispatch subagents; the owner has ruled them out on cost. The spec tells you which model each step wants; you check the model you are running on and ask before proceeding if it differs.
docs/engineering/specs/ that
contains a heading matching ## <n>. Working this spec.Current default: docs/engineering/specs/2026-09-03-repository-operations-and-archive-history.md.
Read the spec in full. Its "Working this spec" section defines the progress table, the continuation protocol, the review focus per phase, and the gates. Follow it exactly. In short:
done in the progress table./model and rerun, or to continue anyway. Wait
for the answer.superpowers:writing-plans, then gate G1;superpowers:executing-plans with
superpowers:test-driven-development, then
superpowers:verification-before-completion, then gate G2;/code-review high against the listed spec sections, findings
only, then gate G3..claude/instructions.md.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Live Borg debugging by exec-ing into the borg-web-ui Docker container. Use when debugging borg commands, writing tests against real borg output, developing borg 2.0 features, or verifying borg behavior before writing code.
The English summary is being prepared. Showing the original description.
Create a well-formed git commit from current changes using session history for rationale and summary; use when asked to commit, prepare a commit message, or finalize staged work.
The English summary is being prepared. Showing the original description.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.
The English summary is being prepared. Showing the original description.
Use Symphony's `linear_graphql` client tool for raw Linear GraphQL operations such as comment editing and upload flows.
The English summary is being prepared. Showing the original description.
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
The English summary is being prepared. Showing the original description.
Push current branch changes to origin and create or update the corresponding pull request; use when asked to push, publish updates, or create pull request.
The English summary is being prepared. Showing the original description.