business-plan-context

What problem does it solve?

Prevents inconsistent or ephemeral product, pricing, audience, branding, and go-to-market decisions by centralizing authoritative choices in a single repository folder so agents always read and respect prior decisions before recommending changes.

Core Features & Use Cases

• Read-before-act enforcement: Lists and reads files in business-plan-desicions/ to surface constraints before making recommendations about product scope, pricing, audience, brand, messaging, funnel, or launch strategy.
• Structured decision recording: Provides a filename convention (NNN-topic-name.md) and a standard document structure (title, date, status, decision, rationale, implications, open questions, sources) to record new or revised decisions.
• Conflict detection and traceability: Flags contradictions with existing decisions, requires explicit user approval to change them, and encourages creating superseding documents rather than silent edits.
• When to apply: Use for pricing, SKU definitions, target avatars, brand guides, funnel design, launch plans, and any task that depends on business strategy or financial assumptions.

Quick Start

Read the business-plan-desicions folder, summarize existing decisions relevant to pricing and target audience, and create or update a numbered decision file if the conversation produces a new or revised conclusion.