phase-doc

phase-doc is a command for coding agents from valsecchi75/project-scaffolder. It costs 22 tokens per session (336 once invoked), scanned A, original, MIT.

A document that defines how the current project phase will be carried out, including activities, assigned models, token budgets, parallel work, and proof that each activity is complete. A project phase is one bounded stage of a larger plan.

In plain words
What is it for?
Use it to prepare a phase plan from project priorities, a roadmap, and a design specification, then save it as a phase execution document and log the operation.
Why use it?
It makes the work and its completion checks explicit before tasks begin. The workflow also prevents starting tasks when the required execution document is missing.

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-doc
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.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for phase-doc

README.md
[![agentmods](https://agentmods.dev/badge/commands/valsecchi75/project-scaffolder/phase-doc.svg)](https://agentmods.dev/commands/valsecchi75/project-scaffolder/phase-doc)
Your own site
<a href="https://agentmods.dev/commands/valsecchi75/project-scaffolder/phase-doc"><img src="https://agentmods.dev/badge/commands/valsecchi75/project-scaffolder/phase-doc.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 336 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.00022 $0.00336
Opus 5 $0.00011 $0.00168
Sonnet 5 $0.00004 $0.00067
Haiku 4.5 $0.00002 $0.00034

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

Security

Grade A, and why

phase-doc 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 4d 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-doc.md · 28 lines

What it actually says

/phase-doc — Phase Execution Document

Generate docs/phases/PHASE-{N}-execution.md for the current phase. This document is the hard gate: the Cortex refuses /task without it.

Steps

  1. Determine the current phase N from CLAUDE.md ("Current phase") and wiki/product/roadmap.md.
  2. If docs/phases/PHASE-{N}-execution.md already exists → ask: "Update the existing doc or abort?" Never overwrite silently.
  3. Read wiki/priorities.md, wiki/product/roadmap.md, and the design spec in docs/superpowers/specs/.
  4. Draft the Activities table using templates/execution-doc.md (from the plugin root). For every activity:
    • a → VERIFY: criterion (concrete evidence, not "it works")
    • a model assignment following the Model Routing Policy
    • a Parallel flag (yes only if zero dependency on other activities)
    • a token estimate (~Nk)
  5. Fill Assumptions & Unknowns from the phase brief (tag [HYPOTHESIS] anything not explicitly stated).
  6. Present the draft table for confirmation (skip confirmation in Autonomous mode).
  7. Create docs/phases/ if missing, write the document.
  8. Log the operation to logs/pipeline/YYYY-MM-DD.md.

Flags

  • --update — regenerate the doc for the current phase keeping completed activities marked.
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. 4d ago First seen · 28 lines · 22 tokens per session scan A 5da6e177b8b9

Subscribe to this mod's changes

phase-doc is a command published in the GitHub repository valsecchi75/project-scaffolder (9 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 336 once invoked, about $0.0001 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.