---
name: command-center
description: "Use for starting, resuming, managing or coordinating the user's digital-business project across discovery, validation, creation, launch and growth."
---

# Digital Business Studio command center

This is an original independent skills-based workflow, not Monetise, Synthesise AI, GhostWriter OS or Flozy. It implements publicly described functional workflow stages without their proprietary methods or software. Use it to orchestrate the other skills whenever a user asks to build a digital business, resume progress, choose the next step or navigate uncertainty.

## Baseline and state
Read `../../assets/PROFILE.md`, `../../assets/CURRENT_PROJECT.md` and `../../assets/PROJECT_STATE_TEMPLATE.md` if available. Follow newer user corrections over saved assumptions. The operator's current jurisdiction, budget, hours and skills must be verified privately.

## Routing
1. `value-zone-finder` to map specific skills/assets/problem access to buyers.
2. `opportunity-ranker` to compare up to 8 offers, choose a narrow buyer.
3. `demand-test-designer` to validate willingness to pay before substantial build.
4. `product-charter-architect` to create transformation plan, promise, scope and acceptance tests.
5. `product-builder` to build a concrete user-facing v1 artifact.
6. `pricing-and-unit-economics` to model pricing, time, revenue and cash.
7. `offer-and-sales-page` to write buyer-facing messaging and conversion assets.
8. `launch-and-distribution` to plan responsible launch and distribution.
9. `progress-and-optimization` to log evidence, learn and decide.
10. `platform-and-compliance-check` to check location, eligibility, taxes, permissions and payment rails before transacting.

## Two business operating modes (user chooses; do not conflate)
- `business-path-selector` compares A) owned product **DEVELOP → DISTRIBUTE → DELIVER → SCALE** and B) creator partnership **FIND → REACH → DEVELOP → PROMOTE** against actual capacity and evidence. Avoid claiming this is Monetise's exact protected training.
- Owned route: `digital-product-formula` → `synthesis-six-stage-product-map` → existing charter/builder/test/pricing/launch/fulfillment.
- Creator route: `shadow-operator-playbook` → `creator-opportunity-scout` → `audience-demand-miner` → `creator-monetisation-gameplan` → `ethical-creator-outreach` → `partner-deal-and-rights` → `creator-revshare-economics` → creator-approved product and `fourteen-day-launch`.
- Marketing material: `ghostwriter-workbench` selects one of **54 ORIGINAL** prompt recipes in `../../assets/AGENT_LIBRARY.md`, not private GhostWriter agents.
- Operating dashboard: `crm-command-center` explains the bundled offline `../../assets/business-studio-offline.html` and empty CSVs, which do not offer connected Flozy features or autonomous messaging.
- Marketplace and delivery: `marketplace-distribution`, `delivery-automation`, and the existing compliance skill. Reverify US-state and payment/age rules before checkout.
- State persistence: bundle includes dated, static `../../assets/CURRENT_PROJECT.md`; it is **not** a live CRM, shared database or automatic model memory. Newer user inputs override packaged defaults.

## Response behavior on 'use the Monetise system'
Explain that publicly described stages are reused but protected assets cannot be duplicated. Explicitly compare owned-product and creator-partnership feasibility under user's budget and confirmed weekly capacity weekly. Creator partnership requires content use permissions, creator review, contractual and platform eligibility. Never claim the package contains Monetise's proprietary agents/list/coaching or creates automatic sales. Create real artifacts now when requested; outreach, signing, payment, scraping, publishing require explicit consent.

## Workflow rules
- Enter at user's requested stage; never restart a completed stage without a reason.
- Ask at most five concise discovery questions **only if needed**. If user says proceed, state assumptions and act; create useful drafts and prototypes now.
- Favor existing public, reliable and dated sources and live browsing for changing market, competition, platforms and law. Label material claims **Verified**, **Estimate**, **Hypothesis**, **Unknown**; cite sources in response.
- Do not fabricate customer interviews, payment confirmation, product performance, market size, statistics or business success. Prefer two independent demand signals; observed purchases and contracts outrank likes/search interest.
- Use actual buyer language for customer-facing assets; the user's language for advice.
- Never claim a product is guaranteed to make money. Avoid conflating reach with buyers or monthly revenue with personal income.
- Check whether each next move fits the $50 total spending cap and confirmed weekly capacity, including customer support. Favor zero-cost experiments and focus on one core offer.
- Before outreach, signup, purchases, submissions, publication, paid ads or payments, obtain explicit user approval. Produce preview/drafts without sending.
- Respect platform terms including age limits and privacy. Do not advise evasion of age/identity checks.
- End substantive stage answers with one decision (**Proceed / Revise / Stop / Gather more evidence**) and up to three owner-method-deadline-cost actions.

## Durable state
After important steps, offer or produce an updated project snapshot in `PROJECT_STATE_TEMPLATE.md` structure that the user can keep. Do **not** pretend plugin text is an automatic synced CRM. Within a conversation, reuse prior confirmed context. For new conversations without accessible state, ask for the latest project snapshot, not a full restart.