zxdxjtu/harness/harness-status

Harness Status

Recover context and determine the current development phase.

Step 1: Check Harness State

test -d .harness && echo "HARNESS_EXISTS" || echo "NO_HARNESS"

If no .harness/ directory exists, tell the user to start with /proposal.

Step 1.5: Check Configuration

test -f .harness/config.yaml && echo "CONFIG_EXISTS" || echo "NO_CONFIG"

If no config exists, suggest running /harness-init first for optimal experience.

Step 2: Read State Files

1. List all specs: ls .harness/specs/ 2>/dev/null
2. Read config: Read .harness/config.yaml (if exists) for project context
3. Read tasks: Read .harness/tasks.md (if exists)
4. Read progress (last 50 lines): Read .harness/progress.md offset from end
5. Check sprint loop: Read .harness/sprint-loop.md (if exists)
6. Read pitfalls: Read .harness/pitfalls.md (if exists) — lightweight project pitfalls
7. Check invariants: Read .harness/invariants.md (if exists) for learned constraints
8. Check traces: Count events in .harness/traces/events.jsonl (if exists)
9. Recent git history: git log --oneline -20

Step 3: Output Summary

For each feature, report:

• Spec status (draft/approved/tests-aligned)
• Test status (how many RED/GREEN)
• Task status (pending/in_progress/completed/failed counts per wave)
• Sprint loop status (active/inactive, iteration count)
• Pitfalls count (N known pitfalls recorded) — list them if ≤ 10, otherwise show count + categories

Step 4: Determine Phase

Step 5: Health Check

• Dependencies installed? (npm ci / pip install / etc.)
• Build passes?
• Core tests green?
• If anything fails → fix regression first

Step 6: Evolution Suggestions

Based on project state, suggest evolution actions:

Step 7: Output Plan

State clearly:

• Current phase
• Project configuration status (initialized? norms? invariants?)
• Specific goal for this session
• Which tasks/waves to work on
• Verification method
• Evolution status (invariants count, last evolution date)