albertpikkop

business-blueprint

Turn a business idea into a plan that survived being attacked, in three kept versions: ten plain questions answered in the person's own words become v0, a ruthless gap attack that scores each area and names what is missing becomes v1, and real answers from real strangers become v2, the Blueprint. Use when someone says "help me plan my business", "mera business plan banao", "business idea hai", "I have an idea", "rate my plan", "attack my plan", "be ruthless", "is this idea any good", "make my v0", "survey banao", and later "a customer told me something", "I want to change the plan", "should I pivot". Also use before any building skill when only an idea exists. Nothing is invented: every guess is labelled Assumption and every unknown stays [PENDING]. Stand down when the ask is a piece of work or a prompt rather than a business (noguess owns it), when a finished Blueprint exists and the ask is to build it, or when the person wants writing help, not a plan.

churn-autopsy

Find why customers leave before deciding how to keep them: build a ledger of every customer who left from the person's own data, score the five suspects (selection, promise, delivery, experience, economics) against that ledger, and rank the causes by how many customers each one explains. Use whenever someone says "clients keep leaving", "100% churn", "customers do not come back", "retention is bad", "nobody renews", "hamare clients ruk nahi rahe", "clients chhod ke ja rahe hain", "is it our quality or our UX", "help me find the root cause of churn", or asks for a retention plan, a loyalty offer, a win-back campaign or a discount before the cause is known. Also use when an owner arrives already certain of the cause ("it is the dashboard", "the team is slow", "our reports are confusing"). Stand down when the ask is a prompt (noguess owns it), a plan for a business with no customers yet (business-blueprint owns it), or a fix to one named thing one customer complained about.

noguess

The TCE + NHA method: turn a raw ask or brain dump into a Task / Context / Expectations prompt where nothing is invented, run a gap analysis before building for a beginner, and check an AI's answer against the prompt that produced it. Use when the user asks for a prompt or a brief for Codex, Claude, ChatGPT or Cursor ("TCE this", "write the prompt for", "prompt likho"), when they describe something they want built and no truth file (BUSINESS-TRUTH.md, AGENTS.md, CLAUDE.md) exists yet ("can you build it for me", "mujhe app banani hai"), or when they paste an AI's answer and ask whether it made anything up ("check this", "ye sahi hai kya"). Stand down when the repo already has a truth file, when the ask names a file and a fix, when it is one small reversible step they want done now, or when the gap analysis already ran in this conversation: then just do the work.

tce

Alias. "TCE this", "tce this" and /tce all mean the noguess skill: the TCE + NHA method (Task / Context / Expectations, nothing invented; the gap analysis at first contact; the check that closes the loop). Read and follow ../noguess/SKILL.md, which is the whole skill. Kept so students who learned the method as TCE keep their command.