// Minimal SPARV workflow (Specify→Plan→Act→Review→Vault) with 10-point spec gate, unified journal, 2-action saves, 3-failure protocol, and EHRB risk detection.
| name | sparv |
| description | Minimal SPARV workflow (Specify→Plan→Act→Review→Vault) with 10-point spec gate, unified journal, 2-action saves, 3-failure protocol, and EHRB risk detection. |
Five-phase workflow: Specify → Plan → Act → Review → Vault.
Goal: Complete "requirements → verifiable delivery" in one pass, recording key decisions in external memory instead of relying on assumptions.
0-10; must be >=9 to enter Plan..sparv/journal.md every 2 tool calls.specify|plan|act|review|vault (stored in .sparv/state.yaml:current_phase).When any Specify dimension scores < 2:
UNCERTAIN: <what> | ASSUMPTION: <fallback>Example:
UNCERTAIN: deployment target | ASSUMPTION: Docker container
UNCERTAIN: auth method | OPTIONS: JWT / OAuth2 / Session
| Mode | Condition | Flow |
|---|---|---|
| Quick | score >= 9 AND <= 3 files AND no EHRB | Specify → Act → Review |
| Full | otherwise | Specify → Plan → Act → Review → Vault |
Quick mode skips formal Plan phase but still requires:
Before Specify scoring:
.sparv/kb.md for existing patterns/decisions## ContextSkip if user explicitly provides full context.
During Vault phase, update .sparv/kb.md:
Use during Review or Vault phase for non-trivial changes:
~/.claude/skills/sparv/scripts/changelog-update.sh --type <Added|Changed|Fixed|Removed> --desc "..."
Initialize (run in project root):
~/.claude/skills/sparv/scripts/init-session.sh --force
File conventions:
.sparv/state.yaml: State machine (minimum fields: session_id/current_phase/action_count/consecutive_failures).sparv/journal.md: Unified log (Plan/Progress/Findings all go here).sparv/history/<session_id>/: Archive directoryEach item scores 0/1/2, total 0-10:
score < 9: Keep asking questions; do not enter Plan.
score >= 9: Write a clear completion_promise (verifiable completion commitment), then enter Plan.
.sparv/journal.md (Plan section or append directly).~/.claude/skills/sparv/scripts/failure-tracker.sh fail --note "short blocker"
~/.claude/skills/sparv/scripts/failure-tracker.sh reset
Run 3-question reboot test before session ends:
~/.claude/skills/sparv/scripts/reboot-test.sh --strict
Archive current session:
~/.claude/skills/sparv/scripts/archive-session.sh
| Script | Purpose |
|---|---|
scripts/init-session.sh | Initialize .sparv/, generate state.yaml + journal.md |
scripts/save-progress.sh | Maintain action_count, append to journal.md every 2 actions |
scripts/check-ehrb.sh | Scan diff/text, output (optionally write) ehrb_flags |
scripts/failure-tracker.sh | Maintain consecutive_failures, exit code 3 when reaching 3 |
scripts/reboot-test.sh | 3-question self-check (optional strict mode) |
scripts/archive-session.sh | Archive journal.md + state.yaml to history/ |
hooks/hooks.json:
save-progress.sh (2-Action save)check-ehrb.sh --diff --dry-run (prompt only, no state write)reboot-test.sh --strict (3-question self-check)Quality over speed—iterate until truly complete.
Execute codeagent-wrapper for multi-backend AI code tasks. Supports Codex, Claude, Gemini, and OpenCode backends with agent presets, skill injection, file references (@syntax), worktree isolation, parallel execution, and structured output.
This skill should be used for multi-session autonomous agent work requiring progress checkpointing, failure recovery, and task dependency management. Triggers on '/harness' command, or when a task involves many subtasks needing progress persistence, sleep/resume cycles across context windows, recovery from mid-task failures with partial state, or distributed work across multiple agent sessions. Synthesized from Anthropic and OpenAI engineering practices for long-running agents.
This skill should be used for structured feature development with codebase understanding. Triggers on /do command. Provides a 5-phase workflow (Understand, Clarify, Design, Implement, Complete) using codeagent-wrapper to orchestrate code-explorer, code-architect, code-reviewer, and develop agents in parallel.
Use this skill when you see `/omo`. Multi-agent orchestration for "code analysis / bug investigation / fix planning / implementation". Choose the minimal agent set and order based on task type + risk; recipes below show common patterns.
Extreme lightweight end-to-end development workflow with requirements clarification, intelligent backend selection, parallel codeagent execution, and mandatory 90% test coverage
This skill should be used when generating comprehensive test cases from PRD documents or user requirements. Triggers when users request test case generation, QA planning, test scenario creation, or need structured test documentation. Produces detailed test cases covering functional, edge case, error handling, and state transition scenarios.