thewoolleyman/livespec-driver-pi

livespec-revise

Walk the user through accepting or rejecting pending proposed changes in <spec-root>/proposed_changes/, then snapshot the result as a new <spec-root>/history/vNNN/ revision. Covers every pending proposal by default, or ONE named proposal via --only-topic…

原文の言語: 英語

livespec-critique

Critique an existing livespec specification or a pending proposed change, surfacing ambiguities, contradictions, and missing rules as findings the user can act on. Use when the user asks to critique the spec or find issues in it. This mutating operation can…

原文の言語: 英語

livespec-propose-change

File a proposed change against an existing livespec specification, landing it under <spec-root>/proposed_changes/<topic>.md. Use when the user wants to record a spec amendment that the next revise pass will accept or reject. This mutating operation writes a…

原文の言語: 英語

livespec-prune-history

Destructively prune old vNNN/ snapshots from <spec-root>/history/ to bound history size. Requires explicit user invocation because model-driven invocation is disabled, and a generic mention of history NEVER activates it. Invoked only via…

原文の言語: 英語

livespec-seed

Author the initial natural-language livespec specification for a new project, populating the chosen template's spec_root layout. Use when starting a brand-new spec in an empty SPECIFICATION/ tree, or when the user asks to "seed a livespec spec" or "set up a…

原文の言語: 英語

livespec-doctor

Run the livespec doctor checks against a spec tree — the static phase (structural failures) plus the LLM-driven objective and subjective phases — surfacing findings as JSON or as a per-finding user dialogue. Use when the user asks to run livespec doctor or…

原文の言語: 英語

livespec-help

Explain what livespec does and route the user to the right livespec operation (seed, propose-change, critique, revise, doctor, prune-history, next). Use when the user asks what livespec can do or wants an overview of its capabilities. Read-only.

原文の言語: 英語

livespec-next

Rank the next spec-side action (revise, propose-change, critique, prune-history, or none) over the current <spec-target>/proposed_changes/ and <spec-target>/history/ state, emitting structured JSON. Use when the user asks what to work on next on the spec…

原文の言語: 英語