← Về thư mục

---

name: startup-kit-walkthrough description: Walk a CEO/founder through the Startup Kit (Idea Canvas, Customer Persona, Value Prop, BMC, Customer Journey, Validate) using lib/startup_kit.py — save, validate, resume. Conversational, one-block-at-a-time, Vietnamese.

---

Skill: Startup Kit Walkthrough

Guide the CEO through filling the structured business frameworks (Startup Kit) in company_kb/business/. The engine is lib/startup_kit.py — a deterministic CLI that saves blocks and tracks status.

When to trigger

• User finishes onboarding and has tier >= starter_plus
• User says "bắt đầu startup kit", "làm khung doanh nghiệp", "điền BMC / Idea Canvas"
• User has an incomplete startup_kit from a previous session (status shows next block)

Sequence

0. Check status first

Always start with:

python3 lib/startup_kit.py status

This shows: total blocks, filled/validated counts, next block, and per-framework progress.

If filled_pct > 0 → resume from next, do NOT start over. Explain what was already done.

1. Get the next block

python3 lib/startup_kit.py next

Returns: framework, block, title, question, hint, examples.

Present ONLY the question + hint (shorten examples to 1-2). Do NOT dump the full JSON. Use natural Vietnamese.

2. Save the answer

User provides their answer. Synthesize/restructure it into clear sections BEFORE saving:

export HERMES_SESSION_USER_ID="<user_id>"
export HERMES_SESSION_PLATFORM="telegram"
BODY="<structured answer>"
python3 lib/startup_kit.py save <framework> <block> "$BODY"

IMPORTANT: The env vars HERMES_SESSION_USER_ID and HERMES_SESSION_PLATFORM MUST be set in the terminal environment for startup_kit.py to resolve the user as admin. The user_id format is tg_<number> (without any prefix stripping). If the save returns admin_only, the env vars are wrong or the user's org_role is not 'ceo'.

3. Offer validation

After each successful save (status=draft), ask: "Chốt luôn ô này không?" or offer to go to the next.

If user agrees → validate:

python3 lib/startup_kit.py validate <framework> <block>

If user says "để sau" → just move to next.

4. Show progress periodically

Every 3-5 blocks saved, run status again and give the user a summary: - "Đã điền X/Y ô (Z%): khung A (W% hoàn thành), khung B (V%...)"

Important: env var persistence

Each terminal() call is a new shell. You MUST re-export HERMES_SESSION_USER_ID and HERMES_SESSION_PLATFORM in every terminal() call where you run startup_kit.py. If you save to a shell variable in one call and reference it in the next, it will be empty.

Pitfalls

• Dashboard > file browsing: When the user asks "where do I see this?", NEVER suggest the /files/ route. The SPA Dashboard at https://dash.<domain>.sslip.io/ is the canonical visual experience — it renders Idea Canvas, BMC, and all frameworks with status dots and percentages. Only use startup_kit.py show <fw> <block> to read content inline if user asks for details. File browsing (/files/) looks like unfinished work to the CEO.
• Login failure with Dashboard: If the user can't log in to the Dashboard HTTPS URL despite the password being correct, guide them to: (a) open an incognito/private window; (b) try URL-embedded credentials https://user:password@domain/; (c) verify the server is alive via local curl yourself. Browser caching of old credentials is the most common cause — do not assume a password reset is needed.
• Admin check fails: save returns {"ok":false,"reason":"admin_only"} means the user's org_role is not ceo in users/_index.json, OR the env vars got lost between terminal calls. Fix: re-check both.
• User gives verbose answer: always restructure into clean sections before saving. Use **bold** headers, bullet lists, and explicit "Giả định:" labels for assumptions.
• "Chưa rõ" on a block: the user may not have enough info to fill a block (e.g. revenue model). Save the tentative answer with a ⚠️ Cần nghiên cứu thêm note rather than skipping the block. The draft status lets them come back.
• Session context matters: the startup_kit.py save call needs the user in _index.json. Since Nhi onboarded via Telegram, the entry is already there. For other users (Slack, Discord), verify the registry entry exists.
• Framework order matters: the frameworks have a fixed order (order field). Always proceed in order — later frameworks reference earlier ones (BMC draws from Value Prop, which draws from Persona...).
• Git backup: company_kb/business/ is git-tracked. Every save produces a draft file. Changes are reversible via git.

frameworks reference

framework_id	title	blocks
idea_canvas	Idea Canvas	name, problem, solution, users, revenue
customer_persona	Customer Persona	identity, personal, work, goals, where, values, avoid
problem_statement	Problem Statement	problem, context, alternatives, users, emotional_impact, quantifiable_impact, alt_shortcomings, statement
strategy_pyramid	Strategy Pyramid	vision, mission, goals, strategies, tactics, values, why
value_prop	Value Proposition	job, pain_reliever, gain_creator, products_services, gains, pains, statement
bmc	Business Model Canvas	customers, value, channels, relationships, revenue, resources, activities, partners, costs
customer_journey	Customer Journey	awareness, consideration, purchase, experience, loyalty
validate	Validate	riskiest_assumption, smallest_test, learning_to_revise
market_type	Market Type	type, basis, implication
competitive	Competitive Analysis	alternatives, their_strength, their_weak, our_edge
customer_interview	Customer Interview	targets, script, learnings, decision