livespec-seed

Authors the initial livespec specification tree for a new project from a chosen template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a new livespec-governed project requires creating a correctly structured SPECIFICATION/ tree from scratch, which is error-prone when done by hand. This Skill automates seeding that initial natural-language specification using the project's chosen template and the livespec core seed CLI. ## Core Features & Use Cases - Template-based spec seeding: Populates the chosen template's spec_root layout into an empty SPECIFICATION/ tree via core's seed.py CLI. - Config-driven CLI dispatch: Reads the governed project's .livespec.jsonc to resolve the configured seed CLI argv, falling back to core's reference default. - Safety-guarded mutation: Enforces the footgun-guard extension precondition before any mutating operation runs under the pi runtime. - Use Case: You have an empty project and want to adopt livespec. Invoke the skill, pick a template, and it writes the initial spec tree ready for the propose-change / critique / revise loop. ## Quick Start Ask the agent to seed a new livespec specification in the current project using the default template. ## Quick Start Say: seed a livespec spec for this project using the default template.

Frequently Asked Questions about livespec-seed

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

FAQPage Schema
How do I seed a new livespec specification for a project?

Invoke the livespec-seed skill in the pi runtime from the project root. It resolves the livespec core installation, reads core's seed prose, and runs the configured seed CLI to populate the SPECIFICATION/ tree from your chosen template.

How does the seed CLI get configured in .livespec.jsonc?

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

Why does the seed skill fail under a non-interactive pi run?

Non-interactive pi invocations silently ignore project-local packages until a trust decision exists, so core resolution fails. Configure trust in ~/.pi/agent/trust.json, set defaultProjectTrust, or pass --approve, then retry.

Can I use livespec-seed without the footgun-guard extension loaded?

No. Seed mutates the specification tree, and the Driver-shipped-hooks contract requires the tool_call footgun-guard extension to be loaded first. If pi reports extensions are not loaded, stop and resolve the trust or install issue.

What is the difference between livespec core and the pi Driver package?

Livespec core ships the harness-neutral prose, reference CLIs, schemas, and templates. The pi Driver package ships only the thin SKILL.md bindings, the core-root resolver, and the footgun-guard extension that wire core's behavior to the pi runtime.