peopleforrester

Generate changelog entries following Keep a Changelog format

Generate a well-structured pull request with summary and test plan

Cluster related instincts into skills, commands, or agents

Export instincts for sharing with teammates or backup

Import instincts from teammates or community collections

View learned instincts grouped by domain with confidence levels

Clean up project files, remove cruft, and organize codebase

Fix linting errors systematically across the codebase

Generates data analysis reports with quality summaries, ASCII tables, and methodology notes. Use when creating data analysis output or reports.

Explains code with diagrams and analogies. Use when explaining how code works. Intentionally minimal — contrast with meeting-prep-kit for a richer example.

Transform a raw meeting transcript into a stakeholder-ready prep kit — executive summary, decisions log, action items CSV, follow-up email, and topic-by-topic timeline with sentiment. Use when the user has a meeting transcript file and needs artifacts for attendees, stakeholders who missed the meeting, or downstream execution.

Scaffolds REST API endpoints with input validation, error handling, and tests. Use when creating API endpoints or microservices.

Reviews Dockerfiles and container configs for security and best practices. Use when reviewing or creating Docker configurations.

Generates UI components following vanilla JS, accessible HTML, and CSS custom property conventions. Use when creating frontend components.

Initialize a .brain-spec/ workspace with directory tree, config, steering documents, and optional CLAUDE.md generation.

Spec lifecycle management — create, interview, list, get, update, delete, and archive feature specifications.

Display a quick overview of the Brain Spec workspace with steering doc status, specs, tasks, and progress.

Task management — create, update, list, log, and track progress for spec implementation tasks.

Scaffold a REST API endpoint with input validation, structured error handling, and a passing test before any business logic is written.

Review a Dockerfile against an enterprise best-practice checklist and report concrete issues with line references.

Drive any non-trivial change through write-spec → review-spec → implement-from-spec, instead of jumping to code.