sparv_skill

Overview

This skill implements the SPARV (Specify → Plan → Act → Review → Vault) mini-workflow to take a requirement through verifiable delivery in one session. It enforces a 10-point specify gate, automated journaling, a 3-failure escalation protocol, and EHRB risk checks so outcomes are auditable and safe. The workflow is minimal by design and stores state and a unified journal under a .sparv directory.

How this skill works

The skill guides each session through five fixed phases stored in .sparv/state.yaml: specify, plan, act, review, vault. Specify uses a 0–10 scoring rubric; scores >=9 produce a completion_promise and allow progression. Actions trigger a 2-action save that appends to .sparv/journal.md; three consecutive tool failures halt and escalate. High-risk operations prompt an explicit EHRB confirmation before proceeding.

When to use it

• Delivering small-to-medium engineering tasks with traceable decisions and tests
• When you need a single-pass, auditable delivery from requirements to archive
• Working on production-sensitive or security-critical changes that require explicit confirmations
• Maintaining consistent session history and reusable decisions for teams
• When automated risk detection and enforced test-driven progress are required

Best practices

• Score each Specify dimension honestly; do not enter Plan until score >=9
• Use Context Acquisition to pull existing patterns from .sparv/kb.md or the codebase before scoring
• Break Plan tasks into 2–5 minute atomic items with verifiable outputs
• Run tests before committing production code; enforce TDD: no failing test → no code
• Respect the 3-failure protocol and escalate early to unblock human decision-making

Example use cases

• Implementing a new API endpoint with acceptance tests and documented deployment decisions
• Fixing a critical bug where you must track risk, reproduce steps, and archive the fix rationale
• Adding a feature where decisions and patterns should be added to a shared knowledge base
• Performing security-sensitive changes that require EHRB confirmation before acting
• Running quick fixes using Quick mode for trivial changes that meet the gate and file limits