spec-refresh-from-brainstorm

Syncs brainstorm lifecycle events into LiveSpec feature specs via an interactive Impact Report.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-refresh-from-brainstorm-julien-m
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-refresh-from-brainstorm
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-refresh-from-brainstorm
Command: npx skills add https://github.com/julien-m/livespec --skill spec-refresh-from-brainstorm-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Brainstorming sessions produce lifecycle events (features added, cancelled, deprecated) that drift out of sync with the project's specification files. This Skill detects those deltas and reconciles them into LiveSpec specs without ever modifying specs without explicit human confirmation. ## Core Features & Use Cases - Delta Detection with Integrity Validation: Reads the brainstorm lifecycle NDJSON log after a stored cursor and validates the SHA-256 prev_hash chain before any action. - Interactive Impact Report: Presents proposed actions (feature-add, cancel, deprecate) one by one, applying each only after an explicit 'o' confirmation, with deferral support. - Cursor-Based Incremental Sync: Advances a .refresh-cursor file so subsequent runs only process new events. - Use Case: After a brainstorm session marks a feature as deprecated, run the command to see an Impact Report, confirm the deprecation, and have the corresponding .specs/features spec updated with status and evidence notes. ## Quick Start Run /spec-refresh-from-brainstorm to review new brainstorm lifecycle events and confirm which spec changes to apply.

Frequently Asked Questions about spec-refresh-from-brainstorm

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

FAQPage Schema
How do I sync brainstorm lifecycle events into LiveSpec specs?

Run /spec-refresh-from-brainstorm with a brainstorm symlink in the project root. It reads lifecycle events after the stored cursor, displays an Impact Report of proposed actions, and applies only the actions you explicitly confirm with 'o'.

How does the refresh cursor work in spec-refresh-from-brainstorm?

The cursor is a single-line JSON file (.refresh-cursor) storing the last processed event_id, timestamp, and hash. On each run, only events strictly after the cursor are processed; after completion, the cursor advances to the last validated event.

What happens if the brainstorm lifecycle log is corrupted?

The skill validates the prev_hash chain by canonicalizing each event as JSON and comparing SHA-256 hashes. On any divergence it stops immediately with a BLOCKED error reporting the event id and both hash values, before touching any spec files.

Can spec-refresh-from-brainstorm modify specs without confirmation?

No. Every applicable action is presented individually with an apply/skip/defer prompt. Nothing under .specs/ changes without an explicit 'o' response, and deferred actions are recorded in .refresh-deferred.yaml.

Why does spec-refresh-from-brainstorm report a missing symlink error?

The skill requires ./brainstorm to be a symlink to a brainstorm project containing a lifecycle log. If the symlink is absent or broken, it blocks at step 0 and instructs you to create it with ln -s pointing to your brainstorm project directory.