brainstorming-intent-continuity

Preserves approved brainstorming decisions and rationale in project-local Markdown records.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/GentleJinqi/Brainstorming-Intent-Continuity --skill brainstorming-intent-continuity-gentlejinqi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorming-intent-continuity
Source: https://github.com/GentleJinqi/Brainstorming-Intent-Continuity/tree/main/plugins/brainstorming-intent-continuity/skills/brainstorming-intent-continuity
Command: npx skills add https://github.com/GentleJinqi/Brainstorming-Intent-Continuity --skill brainstorming-intent-continuity-gentlejinqi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? During long brainstorming sessions, approved decisions lose their rationale, rejected directions resurface, and edge cases never reach implementation—especially across context compaction, handoffs, and spec writing. This Skill maintains a small project-owned continuity record so the load-bearing meaning of a Superpowers Brainstorming discussion survives into design and execution. ## Core Features & Use Cases - Intent Record Management: Maintains current.md (effective goals, decisions, prohibitions, proof, edge cases) and history.md (rejected directions, turning points) with synchronized Mermaid diagrams, written only on qualifying semantic events. - Deterministic CLI Mechanics: The scripts/bic.py helper handles apply, validate, read, save-version, bind, migrate, and commit-snapshot operations with revision conflict detection, schema validation, and project-local locking. - Lifecycle and Handoff Control: Supports explicit round ending with user confirmation, pause/cancel/replace/reopen transitions, saved immutable versions for durable handoff pointers, and session binding lookup. - Use Case: A team brainstorms a feature design with Superpowers Brainstorming; BIC records each approved decision and rejected alternative, then supplies that exact intent as input when the native workflow later writes the spec—preventing drift and omitted edge cases. ## Quick Start Start a root session by invoking $superpowers:brainstorming together with $brainstorming-intent-continuity:brainstorming-intent-continuity, then let the record update automatically as decisions are approved.

Frequently Asked Questions about brainstorming-intent-continuity

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

FAQPage Schema
How do I preserve brainstorming decisions across AI context compaction?

Arm a root session by invoking both superpowers:brainstorming and this Skill together. It writes approved decisions, rationale, and edge cases to current.md and history.md only on qualifying semantic events, keeping intent available for later specs and handoffs.

How does brainstorming-intent-continuity work with Superpowers Brainstorming?

It is an explicit companion add-on, not a replacement. Superpowers Brainstorming controls exploration, design, and approvals; BIC only records agreed intent and supplies it as input to the native spec workflow without adding stages or approval gates.

What commands does the bic.py script support?

The CLI supports status, apply, validate, read, save-version, bind, migrate, and commit-snapshot. Apply writes new revisions with expected-revision checks, validate confirms exact revisions, and read retrieves current or saved versions with optional event selection.

Does BIC write records automatically on every conversation turn?

No. Records are created lazily only on qualifying events: outcome-changing approvals or rejections, revisions, accepted non-goals or edge cases, and material open questions. Arming, compaction risk, or agent dispatch never triggers a write.

What happens when a brainstorming round ends in BIC?

The user must explicitly confirm the whole round can be delivered and ended. The confirmation is submitted as an end revision that automatically saves the confirmed version; downstream work consumes the record without reopening it.

Can BIC records be recovered if a saved version is missing?

Recovery works only from a valid explicit pointer or exact binding to the same input. Missing saved versions return version_unavailable; if the exact input is unrecoverable, the user must explicitly accept proceeding without it for that incident.