Skip to main content
Two things keep Skarmy grounded in your company rather than a generic one: the business plan it writes once and you own from then on, and the memory it keeps of what you have told it.

The business plan

Your company has one plan document, plan.md. Skarmy drafts it once — around your first build — and from that moment it is yours: no model ever rewrites it. You edit it in place from Files. The plan runs through eleven sections:
  1. Foundation
  2. Offer
  3. Customer
  4. Market & competition
  5. Brand & voice
  6. Go-to-market
  7. Money
  8. Legal & risk
  9. Metrics
  10. Execution plan
  11. Assumptions & open questions

Why it matters

The plan is the primary grounding for your daily task suggestions. A plan that says who your customer is and what you charge produces tasks about reaching that customer at that price. A vague plan produces vague tasks. The fastest way to a real plan is the first item on your get-started checklist: Let Skarmy interview you. The interview asks the questions; the answers become the draft.
Treat the plan like a working document, not homework. When something changes — the price, the audience, what you learned from the first ten users — change the plan, and the daily suggestions follow.

What Skarmy remembers

Skarmy keeps three layers of memory about your company, in strict order of trust:
  1. What you said about yourself — facts you stated to the coach about you, the founder.
  2. What you said about the company — facts you stated about the business.
  3. What Skarmy pieced together — a daily distillation of what actually happened.
Your own words always win. Nothing Skarmy infers can override something you stated, and no model ever rewrites your stated facts. To add to memory, just tell the coach — remember that we only fire on weekends — and it saves the fact, scoped to the company or to you.
There is no page yet where you can see or edit stated memory. The correction channel today is the same as the entry channel: tell the coach. If it remembered something wrong, say so and state the correction.

Where memory reaches

Verify

  • Your plan exists in Files as plan.md after the interview or your first build.
  • An edit you make to the plan is still there tomorrow.
  • A fact you asked the coach to remember comes back correctly when you ask about it later.

Next

Daily tasks

What the plan feeds.

Find your files

Where the plan lives.