These are neutral output structures. Fill them only with information supplied, verified, or explicitly accepted for the current business. Store them in the business workspace or provide them as downloadable Markdown.
business-context.md
Include:
- Version, update date, and short change history.
- Business offer, delivery model, priority products or services, and relevant scope.
- Best-fit customer, buying situation, geography where relevant, and poor-fit cases.
- Customer problem, existing alternatives, and supported differentiation.
- Key objections and honest responses.
- Brand voice, preferred vocabulary, and language to avoid.
- Proof inventory: claim, evidence, date, and permitted use.
- Primary conversion action, goal, timeframe, baseline, and capacity.
- Confirmed decisions, proposals, assumptions, and unknowns.
Preserve previous facts unless evidence or the user changes them. Do not replace an existing brief with an empty template. Keep client records separate when one operator serves several businesses.
marketing-plan.md
Include:
- Objective and the decision the first cycle should inform.
- Priority audience, offer, message, and next action.
- Chosen channels and content themes.
- Deliverables, formats, quantities, source assets, owners, and timing.
- Draft review, publishing, lead follow-up, and measurement responsibilities.
- Budget categories, resource constraints, dependencies, and review date.
Select a planning period appropriate to the owner's workload. A short learning cycle is a reasonable proposal when no timeframe is given.
setup-status.md
Record the selected host environment, the business workspace, package location, agreed installation scope, verified destination, and relevant existing skills.
For each file installation, distinguish prepared, copied, and discovered. Record conflicts and any approved backup locations. Do not embed an account secret or machine-specific path in the reusable package; private setup records may include the actual local destination when useful.
For each selected tool, record:
- Purpose and reason it is needed.
- Existing subscription or current pricing evidence.
- Installation, configuration, authentication, and verification states.
- Actual operation tested and its result.
- Owner action or blocker, if any.
- Next step and who will perform it.
Document the user's actual authorization and its limits. Technical access is not a substitute for a decision about purchases or publication. Preserve later corrections.
Costs
Show recurring subscriptions, one-time expenses, service labor, advertising, and usage credits separately. State currency, billing cadence, seats, channels, and known taxes or overages. Distinguish total annual cost from additional spending beyond current commitments.
Do not quote old example prices as current. If a cost is unknown, say so and identify where it will be checked. An annualized monthly price is not the same commitment as a prepaid annual plan.
No file access
Provide complete copyable Markdown or use the host's supported downloadable artifact feature. State that the records are prepared for the user to save. Include a short resume prompt naming the records and the next incomplete step.