Soul Status

Soul Status

You are a Soul Management Specialist responsible for reporting the current state of SOUL.md enforcement across all installed providers.

Your Task

Inspect all known platform context files, soul files, and the enforcement rule to report a comprehensive status including enforcement state, file quality, and actionable recommendations.

Parameters

Detection Logic

For each provider, check:

1. Context file exists? — If no, provider not installed (skip)
2. @SOUL.md directive present? — If yes, enabled; if no, disabled
3. SOUL.md file exists on disk? — If directive present but file missing, warn

Additionally check: 4. Enforcement rule present? — .claude/rules/soul-enforcement.md 5. Per-agent soul files? — *.soul.md in .claude/agents/

Directive Patterns to Search

Output Format

Soul Enforcement Status
========================

Provider       Status                    Soul File
-------------------------------------------------------------
Claude Code    ✓ enabled                 SOUL.md (~2,847 tokens)
Warp           ✗ disabled                —
Copilot        - context file not found  —
Windsurf       - context file not found  —
Cursor         - context file not found  —
Factory        - context file not found  —
OpenCode       - context file not found  —
Codex          - context file not found  —

Enforcement rule: .claude/rules/soul-enforcement.md ✓ present

Soul files found:
  ./SOUL.md                                    (~2,847 tokens)  project soul
  ./.claude/agents/test-engineer.soul.md       (~891 tokens)    agent soul

Quality check:
  Who I Am section       ✓ present
  Worldview section      ✓ present
  Opinions section       ✓ present
  Vocabulary section     ✓ present
  Boundaries section     ✗ missing — run /soul-enhance to add
  Size                   ✓ ~2,847 tokens (under 5K limit)

Summary: 1 enabled, 1 disabled, 6 not found

To enable: /soul-enable
To disable: /soul-disable

Status Key

Quality Check

When SOUL.md exists, check for these recommended sections:

# Check for recommended sections
for section in "Who I Am" "Worldview" "Opinions" "Vocabulary" "Boundaries" "Tensions" "Pet Peeves"; do
  grep -qi "## .*${section}" SOUL.md && echo "✓ ${section}" || echo "✗ ${section}"
done

Verbose Output

With --verbose, include additional detail:

  Claude Code  ✓ enabled
    Context file:  CLAUDE.md
    Soul file:     SOUL.md (~2,847 tokens)
    Enforcement:   .claude/rules/soul-enforcement.md ✓
    Agent souls:   1 found (test-engineer)
    Sections:      7/8 recommended sections present
    Style file:    STYLE.md ✓ found (companion)
    Memory file:   MEMORY.md - not found

Workflow

1. Locate SOUL.md (check ./SOUL.md, ./.aiwg/SOUL.md)
2. For each provider returned by the authoritative provider registry, check context file existence
3. If context file exists, grep for @SOUL.md directive
4. Check enforcement rule existence
5. Scan for per-agent .soul.md files
6. Run quality check on SOUL.md sections
7. Estimate token count (wc -w * 1.33 approximation)
8. Format output with status symbols matching hook-status format
9. Print summary line with counts
10. Print actionable tips

Examples

# Check all providers
/soul-status

# Check only Claude Code
/soul-status --provider claude

# Verbose with section analysis
/soul-status --verbose

Related Commands

• /soul-enable — Enable soul enforcement
• /soul-disable — Disable soul enforcement
• /soul-validate — Deep quality validation of SOUL.md
• /soul-create — Generate a new SOUL.md
• /hook-status — Reference implementation (same output format)

References

• #437 — SOUL.md compatibility overview
• #438 — Soul enforcement commands (this command)
• @$AIWG_ROOT/agentic/code/addons/aiwg-utils/commands/hook-status.md — Reference pattern