livespec-revise

Accepts or rejects pending proposed specification changes and snapshots results as versioned history revisions.

Updated Aug 15, 2026
One-click install
npx skills add https://github.com/thewoolleyman/livespec-driver-pi --skill livespec-revise-thewoolleyman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: livespec-revise
Source: https://github.com/thewoolleyman/livespec-driver-pi/tree/main/skills/livespec-revise
Command: npx skills add https://github.com/thewoolleyman/livespec-driver-pi --skill livespec-revise-thewoolleyman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams governing a living specification accumulate pending proposed changes that must be reviewed, accepted or rejected, and recorded as immutable history revisions; doing this by hand is error-prone and loses auditability. ## Core Features & Use Cases - Proposal review workflow: Walks the user through accepting or rejecting every pending proposal in <spec-root>/proposed_changes/, or a single named proposal via --only-topic <topic>. - Versioned history snapshots: Writes the accepted result as a new <spec-root>/history/vNNN/ revision, preserving a complete audit trail. - Config-driven CLI dispatch: Resolves the revise CLI from the governed project's .livespec.jsonc (spec_clis.revise), falling back to core's reference revise.py script. - Use Case: After teammates submit several proposed spec changes, ask the agent to revise the livespec; it reviews each proposal with you, applies the accepted ones, and records a new history revision. ## Quick Start Ask the agent to revise the livespec and process all pending proposed changes, or to revise only the proposal for a specific topic.

Frequently Asked Questions about livespec-revise

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I revise a livespec specification with pending proposed changes?

Invoke the livespec-revise skill, which reads core's revise prose and walks you through accepting or rejecting each pending proposal in proposed_changes/. Accepted changes are applied to the spec and recorded as a new history/vNNN/ revision.

How do I revise only one proposed change instead of all of them?

Pass the --only-topic <topic> flag to revise a single named proposal while leaving the rest pending in place. This is useful when your authority covers only your own proposal or you want to handle one change at a time.

Why does the revise operation fail under a non-interactive pi run?

Pi's project-trust gate silently ignores project-local packages in non-interactive mode until a trust decision exists, so core resolution fails. Configure trust in ~/.pi/agent/trust.json, set defaultProjectTrust, or pass --approve.

Can I override which revise CLI the skill runs?

Yes. The governed project's .livespec.jsonc names the CLI under spec_clis.revise as an argv array, individually overridable per project. If absent, the skill falls back to core's reference default, python3 <core-root>/scripts/bin/revise.py.

What happens if the footgun-guard extension is not loaded?

Revise mutates the specification tree, so per the driver-shipped-hooks contract it must not run without the tool_call footgun-guard extension loaded. If pi reports extensions are not loaded, the skill stops and tells you rather than proceeding unguarded.