bicameral-search

Name: bicameral-search
Availability: InStock
Author: BicameralAI

Search past decisions across meetings, PRDs, and Slack threads before coding.

Updated Aug 27, 2026

Search Tags:#decisions #context #search #coding #preflight #bicameral

Ready to run

npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-search

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bicameral-search
Source: https://github.com/BicameralAI/bicameral-mcp/tree/main/.claude/skills/bicameral-search
Command: npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface past decisions before coding by surfacing constraints, prior decisions, and context relevant to a feature or task.

Core Features & Use Cases

Pre-flight surface: surface past decisions relevant to the feature or task.
Drift and pending highlighting: identify drifted and agreed-upon-but-not-implemented decisions.
Source-aware results: include source_ref and meeting_date, and map decisions to code regions.

Quick Start

Call the bicameral.search MCP tool with a descriptive query to surface past decisions before starting implementation.

Frequently Asked Questions about bicameral-search

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

FAQPage Schema

How do I surface past decisions and context before coding a new feature?▼

To surface past decisions before coding, run a pre-flight query against meetings, PRDs, and Slack threads to retrieve constraints, prior decisions, source references, and code mappings.

How do I find drifted or pending decisions that were agreed upon but not implemented?▼

Finding drifted or pending decisions involves querying historical context to highlight agreed-upon-but-not-implemented decisions, returning their status, source excerpts, and meeting dates for actionable follow-up.

Can I trace past meeting decisions directly to specific regions in my codebase?▼

Yes, tracing past meeting decisions to code regions is possible by querying historical context that returns source references, meeting dates, and explicit code mappings alongside the original source excerpt.

What is the best way to search across Slack threads and PRDs for historical project constraints?▼

The best way to search across Slack threads and PRDs for historical constraints is running a descriptive pre-flight query that aggregates relevant context, descriptions, and source excerpts into actionable results.

Do I need to integrate any external dependencies to query past decisions from meetings?▼

No external dependencies are required to query past decisions from meetings. You call the search tool directly with a descriptive query to surface constraints and historical context.