solo-potok
/potok
Interactive wizard that walks any decision through the ПОТОК 6-layer framework. Designed for founders making high-stakes choices under uncertainty.
Steps
-
Parse the decision from
$ARGUMENTS. If empty, ask: "What decision or dilemma do you want to analyze?" -
Load framework context (optional enhancement):
- If MCP
kb_searchavailable:kb_search(query="ПОТОК framework", n_results=3)for full framework details. - Otherwise, the framework is embedded below.
- If MCP
-
Walk through 6 layers interactively. For each layer, explain the concept, ask a clarifying question via AskUserQuestion, then provide assessment.
Layer 1 — Epistemological (Knowledge)
- Is this within your circle of competence?
- What assumptions are unproven?
- What would change your mind?
- Ask: "What do you know for certain about this space? What are you assuming?"
Layer 2 — Temporal (Time)
- What's the time horizon for results?
- Is this Lindy-compliant (will it matter in 10 years)?
- Reversibility: can you undo this in 6 months?
- Ask: "What's your timeline? Is this a 3-month experiment or a 3-year commitment?"
Layer 3 — Action (Minimum Viable)
- What's the smallest possible first step?
- What are second-order effects?
- Can you test this in a weekend?
- Ask: "What's the minimum viable version you could ship in 1-2 weeks?"
Layer 4 — Stakes (Risk/Reward)
- Asymmetric upside? (small downside, large upside)
- Survivable worst case?
- Opportunity cost of NOT doing this?
- Ask: "What's the worst realistic outcome? Can you survive it financially and emotionally?"
Layer 5 — Social (Network)
- Reputation impact on your network?
- Network effects or viral potential?
- Does this build social capital?
- Ask: "Who benefits besides you? Who might be hurt?"
Layer 6 — Meta (Mortality Filter)
- Is this worth your finite time on earth?
- Does this align with your values?
- Will you regret NOT trying this?
- Ask: "If you had only 5 years left, would you still do this?"
-
Synthesize verdict:
- Score each layer 1-10
- Overall ПОТОК score (weighted average)
- GO (score > 7) / PAUSE (5-7) / NO-GO (< 5)
- Key risk to mitigate
- Recommended first action
-
Capture the decision (optional): Offer to save the decision record. If user wants to save:
- Write to
3-opportunities/inbox/(if in solopreneur KB) ordocs/decisions/(any project) - Format: date + decision summary + verdict
- Write to
-
Output structured decision journal:
## Decision: [topic] **Date:** [today] **Framework:** ПОТОК 6-layer ### Analysis Summary | Layer | Score | Key Finding | |-------|-------|-------------| | Epistemological | X/10 | ... | | Temporal | X/10 | ... | | Action | X/10 | ... | | Stakes | X/10 | ... | | Social | X/10 | ... | | Meta | X/10 | ... | **Overall ПОТОК Score: X/10 — GO/PAUSE/NO-GO** ### Recommendation [Clear recommendation with reasoning] ### Next Actions 1. [action] 2. [action] 3. [action]
More from fortunto2/solo-factory
solo-research
Use when "research this idea", "find competitors", "check the market", "domain availability", "market size", "analyze opportunity", or need evidence before validation. Do NOT use for idea scoring (/validate) or SEO auditing (/seo-audit).
43solo-swarm
Use when "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or want faster multi-angle alternative to /research. Do NOT use for solo research (/research) or idea scoring (/validate).
34solo-build
Use when "build it", "start building", "execute plan", "implement tasks", "ship it", track ID referenced, or plan tasks need execution. Do NOT use for planning (/plan) or scaffolding (/scaffold).
33solo-humanize
Use when "humanize this", "make it sound human", "strip AI patterns", "clean up the copy", or text reads like AI-generated output with em dashes and stock phrases.
33solo-audit
Use when "audit KB", "check frontmatter", "find broken links", "tag cleanup", "knowledge base quality", or docs need health check. Do NOT use for SEO audits (/seo-audit) or code reviews (/review).
31solo-scaffold
Use when "scaffold project", "create new project", "start new app", "bootstrap project", "set up from PRD", or need project from PRD + stack template. Do NOT use for planning features (/plan) or PRD generation (/validate).
30