@outcomeeng/spx 0.4.0 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -62,13 +62,13 @@ All validation commands support `--quiet` for CI and `--json` for machine-readab
62
62
  Manage work sessions for agent handoffs and task queuing:
63
63
 
64
64
  ```bash
65
- # Create a handoff session (reads content with frontmatter from stdin)
66
- cat << 'EOF' | spx session handoff
67
- ---
68
- priority: high
69
- ---
70
- # Implement feature X
71
- EOF
65
+ # Create a handoff session (JSON header at start of stdin, then body bytes verbatim)
66
+ printf '%s\n' \
67
+ '{"priority":"high","goal":"Implement change X","next_step":"Run the focused validation","specs":[],"files":[]}' \
68
+ '# Implement change X' \
69
+ '' \
70
+ 'Body text `#`, `---`, and code fences are literal because the body is not parsed.' \
71
+ | spx session handoff
72
72
 
73
73
  # List all sessions
74
74
  spx session list
@@ -82,7 +82,7 @@ spx session pickup --auto
82
82
  # Release one or more sessions back to the todo queue
83
83
  spx session release [id...]
84
84
 
85
- # Archive a session
85
+ # Archive a session after adding a non-empty result field to its frontmatter
86
86
  spx session archive <session-id>
87
87
 
88
88
  # Show session content
@@ -97,8 +97,6 @@ spx session delete <session-id>
97
97
 
98
98
  Sessions are stored in `.spx/sessions/` with priority-based ordering (high > medium > low) and FIFO within the same priority. Commands output parseable `<PICKUP_ID>`, `<HANDOFF_ID>`, and `<SESSION_FILE>` tags for automation.
99
99
 
100
- See [Session Recipes](docs/how-to/session/common-tasks.md) for detailed usage patterns.
101
-
102
100
  ### Spec Management (deprecated)
103
101
 
104
102
  The `spx spec` and `spx spx` CLI domains are **deprecated**. Spec tree management has moved to the **spec-tree** Claude Code plugin, available at [`outcomeeng/plugins`](https://github.com/outcomeeng/plugins). The plugin provides skills for understanding, authoring, decomposing, contextualizing, testing, refactoring, and aligning specification trees.