phase-shift

A command for moving a project from one development phase to the next. It archives the old phase information, updates the roadmap and priorities, and prepares the workspace for the new phase.

In plain words
What is it for?
Use it after a phase is complete to update milestones, preserve old priorities, reset the handoff, and prepare the next phase's execution document.
Why use it?
It prevents phase changes from losing project history or starting the next phase without its required documentation.

Command

Part of the project-scaffolder plugin — 7 skills, 19 commands, 2 hooks shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/valsecchi75/project-scaffolder/phase-shift
Clone the repo
git clone --depth 1 https://github.com/valsecchi75/project-scaffolder

Or install project-scaffolder, the plugin that ships this one along with the rest of its 7 skills, 19 commands, 2 hooks.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00349
Opus 5 $0.00016 $0.00175
Sonnet 5 $0.00007 $0.00070
Haiku 4.5 $0.00003 $0.00035

Measured 3d ago against content hash 1d18dc4afaad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

phase-shift scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/phase-shift.md · 40 lines

What it actually says

/phase-shift

Transition from the current phase to the next. Execute only when the current phase is actually complete.

Usage

/phase-shift <target-phase-number>
/phase-shift <target-phase-number> --force

Examples

/phase-shift 3
/phase-shift 4 --force

Steps

  1. Verify the current phase is complete (every task in priorities.md checked with VERIFY evidence)
  2. If incomplete and no --force flag → STOP and list remaining work
  3. Mark the current phase [COMPLETED] in wiki/product/roadmap.md with completion date
  4. Update CLAUDE.md → "Current phase: [new phase]"
  5. Generate a fresh wiki/priorities.md populated from the new phase in the roadmap
  6. Append a milestone entry to wiki/log.md
  7. Reset wiki/handoff.md for the first session of the new phase
  8. After the transition, run (or recommend) /phase-doc for the new phase — the /task gate refuses to run without an Execution Doc

Rules

  • Refuse to shift if the current phase has unchecked VERIFY criteria, unless --force is passed.
  • Never skip phases (N → N+2) without --force.
  • Preserve old priorities — archive to wiki/product/archive/phase-N-priorities.md before overwriting.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 40 lines · 33 tokens per session scan A 1d18dc4afaad

Subscribe to this mod's changes

phase-shift is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 349 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.