bicameral-status

Name: bicameral-status
Availability: InStock
Author: BicameralAI

Displays tracked decisions grouped by implementation status with mapped locations.

Updated Aug 27, 2026

Search Tags:#decisions #status #drift #sprint #mapping #ledger

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Bicameral Status skill helps teams quickly verify which decisions have been implemented in code versus what was decided, enabling clearer sprint reviews and faster drift detection.

Core Features & Use Cases

Present a consolidated ledger view of all tracked decisions with their current implementation state.
Group items by status (drifted, pending, ungrounded, reflected) and show source and mapped code regions for quick follow-up.
Support decision governance through action-oriented insights that drive reviews and mapping to code.

Quick Start

Call bicameral.status to surface the current decision-to-code alignment for the active sprint.

Frequently Asked Questions about bicameral-status

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

FAQPage Schema

How do I check decision drift during a sprint review?▼

To check decision drift during a sprint review, surface a consolidated ledger that groups tracked decisions by status, showing which requirements are drifted, pending, or reflected in the mapped code regions.

What is the best way to track decisions vs code status?▼

Tracking decisions vs code status involves summarizing the implementation state of all tracked items, providing a structured breakdown with descriptions, sources, and code mappings to verify alignment.

How do I generate a status ledger for pending and ungrounded decisions?▼

Generate a status ledger by applying a status check to your tracked decisions, producing a structured breakdown categorizing items as drifted, pending, ungrounded, or reflected alongside their mapped code regions.

Can I use this for sprint retrospectives to find ungrounded decisions?▼

Yes, you can use this status summary for sprint retrospectives to identify ungrounded decisions and pending work, providing action-oriented insights that drive mapping to code and follow-up.

How does mapped code region tracking work for decision governance?▼

Mapped code region tracking for decision governance works by grouping your decisions by status and displaying the source alongside the specific code mappings, enabling faster drift detection and clearer sprint reviews.