process-document

Hyper-Process-Document

Write a process document that captures the how of this session — the problem, approach, decisions, and steps taken — so that someone reading it cold can understand and reproduce the results.

This is distinct from /hyper-handoff, which is forward-looking (context for a new agent to continue). This document is retrospective and human-readable: institutional knowledge capture.

---

Step 1 — Determine Output Path

Create the output directory if it does not exist:

mkdir -p spec/process

Name the file: process_<YYYYMMDD>_<slug>.md

• Use the current date for <YYYYMMDD> (date only — no time component)
• Derive <slug> from $ARGUMENTS by lowercasing and replacing spaces/special characters with hyphens (e.g., "Dynamic Workflow Engine" → dynamic-workflow-engine)
• If no $ARGUMENTS provided, use session as the slug

Disambiguate same-day documents with a version suffix. If a file with that exact name already exists (e.g. more than one process document is written on the same date), append _v2, _v3, … to the end of the filename — before the .md extension — using the next unused number. The first document of the day carries no suffix:

base="spec/process/process_$(date +%Y%m%d)_<slug>"   # substitute the real <slug>
path="${base}.md"
n=2
while [ -e "$path" ]; do
  path="${base}_v${n}.md"
  n=$((n + 1))
done
# $path is now collision-free, e.g.
#   spec/process/process_20260616_dynamic-workflow-engine.md      (first of the day)
#   spec/process/process_20260616_dynamic-workflow-engine_v2.md   (second of the day)

---

Step 2 — Gather Context

Before writing, read and recall the following to reconstruct an accurate picture:

git log --oneline -20

git diff HEAD~5..HEAD --name-only

• Read .agents/memory/activeContext.md — current sprint state and recent decisions
• List spec/active/ — any in-progress PRDs or artifacts touched this session
• Recall the conversation: what problems were raised, what approaches were tried, what choices were made and why