/gpd:insert-phase

Prompt file imported from Joe-Heffer-Shef/dark-energy (.claude/commands/gpd/insert-phase.md). Fill in {{arguments}} before use. Copyright stays with the author.

Command Requirements

Command YAML rules. Use this YAML. Closed schema; no extra keys. Strict booleans only; omit empty optional fields. command_policy is the typed additive command-policy wrapper (frontmatter command-policy) with integer schema_version: 1. Its list fields are string lists, suffix lists use dotted suffixes, and context modes use global or projectless or project-aware or project-required. When present, typed command policy controls intake, supporting-context routing, and managed outputs. allowed_tools is a tool-name list. requires supports only files, as a string or string list. agent must match a built-in canonical agent label exactly. project_reentry_capable is boolean and may be true only with context_mode: project-required. Any user-visible completion, checkpoint, blocked return, failed return, retry gate, or stop that expects later action must end with ## > Next Up; include concrete GPD commands and gpd:suggest-next for project-backed recovery.

context_mode: project-required
project_reentry_capable: false
allowed_tools:
- Read
- Write
- Bash
command_policy:
  schema_version: 1
  supporting_context_policy:
    project_context_mode: project-required
    project_reentry_mode: disallowed

Uses decimal numbering (72.1, 72.2, etc.) to preserve the logical sequence of planned phases while accommodating urgent insertions.

Purpose: Handle urgent research tasks discovered during execution without renumbering entire roadmap. Common triggers include:

• A reviewer pointed out a missing limiting case that must be checked before proceeding
• A numerical instability requires an unplanned convergence study
• New literature surfaced that demands an additional comparison
• A sign error or dimensional inconsistency requires re-deriving intermediate results
• An unexpected physical regime requires additional analytical treatment

<execution_context> @/home/joe/code/get-physics-done/.claude/get-physics-done/workflows/insert-phase.md </execution_context>

@GPD/ROADMAP.md @GPD/STATE.md

Execute the included insert-phase workflow end-to-end. Preserve all validation gates (argument parsing, phase verification, decimal calculation, roadmap updates).

Scientific Rigor Guardrails

• Use scientific skepticism and critical thinking by default: look for contradictions, missing anchors, overclaims, and failure modes before endorsing a result.
• Stress-test claims, including the user's preferred interpretation and your own first impression, without framing the user as an opponent.
• Agreement is not evidence. Do not mirror a preferred conclusion or a document's self-description unless the supporting evidence is actually present.
• Ground claims in inspected artifacts, cited sources, executed checks, or explicitly labeled background knowledge.
• If information or artifacts cannot be found, produced, read, verified, or reproduced, report that plainly and keep the status missing, failed, blocked, or inconclusive.
• Never fabricate references, numbers, derivations, files, figures, tables, logs, summaries, proofs, or claimed task completion. Do not use ungrounded fallback content as a substitute for missing evidence or failed execution.
• When certainty is not warranted, narrow the claim, lower confidence, and name the weakest anchor or disconfirming check still needed.