Inspect a single phase's artifacts, status, and results
Codex shell compatibility:
gpd on PATH.GPD_ACTIVE_RUNTIME=codex uv run gpd ....
</codex_runtime_notes>Use this when you want a deep look at one specific phase rather than overall project progress. </objective>
<execution_context>
<!-- [included: show-phase.md] --> <purpose> Inspect a single research phase in detail. Shows artifacts, completion status, key results, verification state, convention changes, and file listing. Produces a structured ASCII report for quick situational awareness of one phase. </purpose><required_reading> Read all files referenced by the invoking prompt's execution_context before starting. </required_reading>
<process> <step name="init"> **Initialize phase context:** <step name="load_directory"> **List all files in the phase directory:** <step name="parse_roadmap"> **Extract phase info from ROADMAP.md:** <step name="plan_completion"> **Check plan completion status:** </step> <step name="key_results"> **Extract key results from completed plans:** <step name="verification_status"> **Check verification and validation files:** <step name="convention_changes"> **Check for convention changes introduced in this phase:** <step name="file_listing"> **List all files produced:** </step> <step name="present_report"> **Assemble the full report:** </step> </process> <!-- [end included] --> <context> Phase: $ARGUMENTS (required) - Phase number to inspect (e.g., "3", "2.1") <process> Execute the show-phase workflow from @./.codex/get-physics-done/workflows/show-phase.md end-to-end. Preserve all report sections and formatting.INIT=$(/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local init phase-op "$PHASE")
if [ $? -ne 0 ]; then
echo "ERROR: gpd initialization failed: $INIT"
# STOP — display the error to the user and do not proceed.
fi
Extract from init JSON: phase_dir, phase_number, phase_name, phase_found, phase_slug, padded_phase.
If phase_found is false:
Phase not found. Available phases:
[list from roadmap]
Usage: $gpd-show-phase <phase-number>
Exit. </step>
ls -la "${phase_dir}/" 2>/dev/null
Categorize files into:
*-PLAN.md*-SUMMARY.md*-CONTEXT.md*-RESEARCH.mdDISCOVERY.md*-VERIFICATION.md*-VALIDATION.md*.py, *.jl, *.m, *.nb*.csv, *.json, *.dat, *.h5, *.hdf5PHASE_INFO=$(/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local roadmap get-phase "${phase_number}")
Extract: phase_name, goal, dependencies, status (from disk analysis).
Also get overall roadmap context:
ROADMAP=$(/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local roadmap analyze)
Find this phase in the phases array to get disk_status (complete/partial/planned/empty/no_directory), plan_count, summary_count.
</step>
For each PLAN.md file found:
Present as table:
## Plan Completion
| # | Plan Name | Status |
|---|----------------------------------|-----------|
| 1 | Derive effective Hamiltonian | Completed |
| 2 | Numerical diagonalization | Completed |
| 3 | Finite-size scaling analysis | Pending |
For each SUMMARY.md:
/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local summary-extract <path> --field one_liner --field key_results --field equations
Collect:
Present:
## Key Results
### Plan 01: [Name]
- [one_liner]
- Key: [key result 1]
- Key: [key result 2]
- Eq: [equation if any]
### Plan 02: [Name]
- [one_liner]
- Key: [key result 1]
If no SUMMARYs exist: "No results yet (no plans executed)." </step>
Look for:
*-VERIFICATION.md — automated physics checks*-VALIDATION.md — researcher-reviewed validationFor each file found, read frontmatter to extract status. Automated verification uses passed/gaps_found/human_needed; interactive validation uses validating/completed/diagnosed.
Present:
## Verification Status
| Type | File | Status | Checks | Passed | Issues |
|--------------|--------------------------|----------|--------|--------|--------|
| Verification | 04-VERIFICATION.md | complete | 8 | 7 | 1 |
| Validation | 04-VALIDATION.md | complete | 5 | 5 | 0 |
If no verification files: "No verification performed yet. Run $gpd-verify-work {phase} to validate results." </step>
For each SUMMARY.md, check frontmatter for affects field.
The affects field lists conventions or definitions that were established or changed:
Present:
## Convention Changes
- [Plan 01]: Adopted (-,+,+,+) metric signature (affects all subsequent phases)
- [Plan 02]: Defined dimensionless coupling g = lambda / (4*pi)^2
If no affects fields found: "No convention changes recorded in this phase."
</step>
ls -lhS "${phase_dir}/" 2>/dev/null
Present with human-readable sizes:
## Files
| File | Size | Modified |
|-------------------------------|-------|------------|
| 04-01-PLAN.md | 4.2K | 2026-03-15 |
| 04-01-SUMMARY.md | 8.1K | 2026-03-15 |
| 04-02-PLAN.md | 3.8K | 2026-03-15 |
| dispersion_relation.py | 2.1K | 2026-03-15 |
| 04-VERIFICATION.md | 5.4K | 2026-03-15 |
================================================================
PHASE {N}: {Name}
================================================================
**Status:** {complete/partial/planned/empty}
**Goal:** {goal from ROADMAP.md}
**Dependencies:** {deps or "none"}
{Plan Completion table from step 4}
{Key Results from step 5}
{Verification Status from step 6}
{Convention Changes from step 7}
{File Listing from step 8}
----------------------------------------------------------------
**Also available:**
- $gpd-verify-work {N} -- run physics validation checks
- $gpd-execute-phase {N} -- execute pending plans
- $gpd-plan-phase {N} -- create new plans
----------------------------------------------------------------
<success_criteria>
affects fields listed</success_criteria>
</execution_context>
@.gpd/STATE.md @.gpd/ROADMAP.md </context>
INIT=$(/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local init phase-op "$ARGUMENTS")
Extract from init JSON: phase_dir, phase_number, phase_name, phase_found, phase_slug, padded_phase.
If phase_found is false: Error with available phases and exit.
List all files in the phase directory and categorize them (PLANs, SUMMARYs, CONTEXT, RESEARCH, DISCOVERY, VERIFICATION, VALIDATION, scripts, data).
Read ROADMAP.md to extract this phase's description, goal, dependencies, and current status indicator.
For each PLAN.md, check if a matching SUMMARY.md exists. Present as completion table.
Extract key results from SUMMARY.md files using summary-extract:
/home/qol/.gpd/venv/bin/python -m gpd.runtime_cli --runtime codex --config-dir ./.codex --install-scope local summary-extract <path> --field one_liner --field key_results --field equations
Check for VERIFICATION.md and VALIDATION.md files. Report their status (passed, issues found, pending).
Check SUMMARY.md frontmatter for affects fields that indicate convention changes introduced in this phase.
List all files produced with sizes and modification dates.
Present everything as a structured ASCII report. </process>
<success_criteria>