livespec-propose-change

Files a proposed change against a livespec specification under the proposed_changes directory.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recording amendments to a governed livespec specification requires a structured, reviewable artifact rather than ad-hoc edits. This Skill files a proposed change under <spec-root>/proposed_changes/<topic>.md so the next revise pass can formally accept or reject it. ## Core Features & Use Cases - Structured change filing: Invokes the config-named propose-change CLI to write a proposed-change markdown file with findings, author, and optional spec target. - Core prose delegation: Resolves the livespec core root via the shared resolver script and executes core's harness-neutral propose-change prose end-to-end. - Guarded mutation: Enforces the footgun-guard extension precondition before any mutating operation runs, surfacing pi project-trust gate failures instead of proceeding unguarded. - Use Case: While reviewing a governed spec you notice a requirement gap; invoke this Skill to record the amendment as a proposed change that the next revise pass will adjudicate. ## Quick Start Ask the agent to file a proposed change against the livespec specification for a given topic, providing your findings so it lands under proposed_changes for the next revise pass.

Frequently Asked Questions about livespec-propose-change

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

FAQPage Schema
How do I propose a change to a livespec specification?▼

Invoke the livespec-propose-change skill with a topic and findings. It resolves the livespec core root, reads core's propose-change prose, and runs the propose_change CLI to write the proposal under <spec-root>/proposed_changes/<topic>.md.

How does the propose-change CLI get configured?▼

The CLI is named in the governed project's .livespec.jsonc under spec_clis.propose_change as an argv array. If absent, the skill falls back to core's reference default: python3 <core-root>/scripts/bin/propose_change.py.

Why does propose-change fail silently in non-interactive pi runs?▼

Pi's project-trust gate silently ignores project-local packages in non-interactive mode until a trust decision exists. The skill stops and surfaces the resolver's diagnostic rather than improvising a path or running an install.

What happens to a proposed change after it is filed?▼

The proposal sits under proposed_changes until the next revise pass, which accepts or rejects it. The revise operation is available as the livespec-revise skill in the same Driver package.

Can propose-change run without the footgun-guard extension?▼

No. Because propose-change mutates the specification tree, the Driver-shipped-hooks contract requires the tool_call footgun-guard extension to be loaded. If pi reports extensions are not loaded, the skill stops instead of proceeding unguarded.