business-plan-context

Read and update business-plan-desicions folder files before making product or pricing recommendations.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/alexwox/genesis-template --skill business-plan-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: business-plan-context
Source: https://github.com/alexwox/genesis-template/tree/main/.cursor/skills/business-plan-context
Command: npx skills add https://github.com/alexwox/genesis-template --skill business-plan-context

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about business-plan-context

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

FAQPage Schema
How do I keep AI agents consistent with previous business plan decisions?

To keep AI agents consistent with previous business plan decisions, centralize authoritative choices in a dedicated folder so agents must read existing files and surface constraints before recommending pricing, product, or go-to-market changes.

What is the best way to document go-to-market and pricing strategy changes?

The best way to document go-to-market and pricing strategy changes is to record structured decision files using a numbered naming convention, including the date, status, rationale, implications, and sources for full traceability.

How do I track contradictions when updating product strategy documentation?

To track contradictions when updating product strategy documentation, flag conflicts with existing decisions explicitly, require user approval for changes, and create superseding documents rather than applying silent edits to the original files.

When should I record business decisions in a centralized repository?

You should record business decisions in a centralized repository whenever tasks touch product scope, pricing, target audience, branding, funnel, messaging, or financial projections and require referencing or updating prior strategic choices.

Does this approach require a specific folder structure for decision recording?

Yes, this approach requires a specific folder structure where agents list and read files from a designated business decisions directory before acting, ensuring new conclusions are written as structured markdown documents.

Why do AI agents overwrite previous target audience or branding decisions?

AI agents overwrite previous target audience or branding decisions because they lack persistent context; enforcing a read-before-act workflow against a central decision repository prevents ephemeral and contradictory recommendations.