What files does Brainstorm Sync modify?

It creates or updates files in the .feat-tree/memories/ directory, including user.md, scope.md, risks.md, and decisions.md, while also updating the project's CONTEXT.md.

Does it capture every detail of a chat session?

No, it is designed to be dense and selective, filtering out generic speculation and implementation details already present in your task list or plan.

How is this different from a technical implementation plan?

While a plan focuses on the 'how' of building features, Brainstorm Sync captures the 'why'—including user pain points, rejected alternatives, and the core assumptions that must be true for the project to succeed.

Why is scope fencing important?

Scope fencing records what you explicitly decided NOT to build, which prevents future scope creep and stops the team from revisiting the same rejected ideas in later sessions.

Brainstorm Sync

Name: Brainstorm Sync
Author: Nothflare

byNothflare

•

Collaboration Tools

Captures the strategic rationale, user insights, and rejected alternatives from brainstorming sessions into persistent project memory.

About

Brainstorm Sync is a specialized Claude Code skill designed to preserve the critical 'thinking' that occurs during project discovery phases but often gets lost in final implementation plans. By systematically extracting user context, scope exclusions, core assumptions, pre-mortem risks, and design trade-offs, it ensures that future development sessions are grounded in the project's original vision and rationale. It automates the maintenance of memory files within the .feat-tree directory, preventing decision fatigue and scope creep by documenting exactly why certain paths were chosen or abandoned.

Key Features

Core assumption tracking with validation methods integrated into CONTEXT.md
Design rationale logging to capture trade-offs and alternative considerations
Automated extraction of user insights and pain points into persistent memory files
Strategic scope fencing to document explicit exclusions and prevent future creep
Pre-mortem risk assessment documentation with early warning signs
1 GitHub stars

Use Cases

Onboarding new AI agents or team members to the project's strategic context
Syncing high-level discovery session outcomes before starting technical implementation
Preventing the re-litigation of previously made design and scope decisions

About

Key Features

Core assumption tracking with validation methods integrated into CONTEXT.md
Design rationale logging to capture trade-offs and alternative considerations
Automated extraction of user insights and pain points into persistent memory files
Strategic scope fencing to document explicit exclusions and prevent future creep
Pre-mortem risk assessment documentation with early warning signs
1 GitHub stars

Use Cases

Onboarding new AI agents or team members to the project's strategic context
Syncing high-level discovery session outcomes before starting technical implementation
Preventing the re-litigation of previously made design and scope decisions