livespec-critique

Critique livespec specifications to surface ambiguities, contradictions, and missing rules as actionable findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specifications accumulate ambiguities, contradictions, and gaps over time that are hard to spot by reading alone. This Skill runs the livespec critique operation against a governed project's specification or a pending proposed change, producing structured findings the user can act on or land as a proposed change. ## Core Features & Use Cases - Specification critique: Analyzes an existing livespec specification or pending proposed change and reports ambiguities, contradictions, and missing rules as findings. - Config-driven CLI dispatch: Resolves the critique CLI from the governed project's .livespec.jsonc under spec_clis.critique, falling back to core's reference critique.py script. - Guarded mutation: Enforces the footgun-guard extension precondition before mutating the specification tree, and can land findings as a proposed change. - Use Case: A maintainer suspects the spec has drifted after several revisions. They invoke the critique operation, which reads core's driving prose, runs the critique CLI with --findings-json, and presents findings they can convert into a proposed change via the revise or propose-change operations. ## Quick Start Ask the agent to critique the current livespec specification and list any ambiguities or contradictions it finds.

Frequently Asked Questions about livespec-critique

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

FAQPage Schema
How do I critique a livespec specification for issues?▼

Invoke the livespec-critique skill in the pi runtime. It resolves the livespec core root, reads core's critique prose, and runs the critique CLI named in the project's .livespec.jsonc, writing findings to a JSON file you can review or land as a proposed change.

How does the critique CLI get configured in a livespec project?▼

The governed project's .livespec.jsonc names the CLI under spec_clis.critique as an argv array. If the key is absent, the skill falls back to core's reference default: python3 <core-root>/scripts/bin/critique.py with flags like --findings-json and --spec-target.

Why does the critique 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. The skill stops and surfaces the resolver's diagnostic rather than proceeding, since an untrusted run also means the footgun-guard extension is not loaded.

Can critique findings become a proposed spec change?▼

Yes. Critique is a mutating operation that can land its findings as a proposed change. The skill binds to the sibling livespec-revise and livespec-propose-change operations in the same Driver package for that follow-up step.

What must be loaded before running a mutating livespec operation?▼

The Driver's tool_call footgun-guard extension (extensions/livespec-footgun-guard.ts) must be loaded before any mutating operation. If pi reports the package's extensions are not loaded, the skill stops instead of running unguarded.