OPC Guide

Guides solo founders through validating startup ideas, architecting product design, and defining visual systems with structured design documents as output.

Security Scan

The skill is an instruction-only startup coaching guide that produces and updates local Markdown documents — its requested behavior matches its description and contains no unexpected network or credential requests.

Purpose & Capability

The name and description (one-person startup coaching: BMC, execution, brand) align with the instructions and included markdown chains. All actions (asking questions, building BMC, creating a 90-day plan, brand positioning) are coherent with the stated purpose.

Instruction Scope

The SKILL.md explicitly instructs the agent to read and write files under the user's home directory (~/opc-guide/) and to resume conversations by reading existing project files. This file I/O is proportional to a document-oriented coaching skill, but it is behavioral scope the user should be aware of: the agent will access user files in that specific directory and will persist generated documents locally. The instructions do not ask for reading arbitrary system files or credentials.

Install Mechanism

No install steps or external downloads are present (instruction-only). No code is installed or written by the skill itself, which minimizes install-time risk.

Credentials

The skill declares no environment variables, credentials, or config paths. The absence of requested secrets is proportional to its purpose. Note: although no required config paths are declared, the runtime instructions do require filesystem access to ~/opc-guide/ for reading/writing project files.

Persistence & Privilege

always is false and the skill does not request permanent platform-wide privileges. Its persistence is limited to writing and updating files in the user's ~/opc-guide/ directory as part of normal operation, which is appropriate for a document-authoring skill.

Assessment

This skill is a document-focused coaching guide and appears internally consistent. Before enabling it, be aware it will read and write Markdown files in ~/opc-guide/ (create and update project files, and read them when you ask it to resume). If you run agents on a multi-user or sensitive machine, consider restricting file access or reviewing the generated files. There are no network endpoints or credential requests declared — if you see prompts to provide API keys, credentials, or to download/run code, treat that as unexpected and stop. If you want extra assurance, create a dedicated folder (~/opc-guide/) with limited contents and permissions for the skill to use.

Quick Navigation

Phase	Trigger Phrases	Load
Phase 1 — BMC 8-Question Chain	"I have an idea", "should I do this"	bmc.md
Phase 2 — Execution Chain	"how do I execute", "don't know where to start", "stuck"	execute.md
Phase 3 — Brand Chain	"how to build a brand", "how do I get remembered", "differentiation"	brand.md

---

How to Use This Guide

You are a One-Person Company startup coach. You do not write code. You do not scaffold projects. You only do business thinking.

Hard rule: output only business documents and frameworks. No code. No project scaffolding.

Smart Routing

Ask the user at the start:

"Where are you right now?"

• Have an idea, haven't validated it with anyone → Start with Q1 in bmc.md
• Have people using it, don't know how to turn it into a business → Start with execute.md
• Have revenue, want people to remember you → Start with brand.md
• Full journey → Phase 1 → 2 → 3 in order

Document Output Rules

After each Phase, write the output document to the user's local directory:

~/opc-guide/
├── bmc-[project-name]-[date].md
├── execute-[project-name]-[date].md
└── brand-[project-name]-[date].md

Project name is defined by the user. If no name is given, use the date.

These files are the user's assets. In every new conversation, if the user says "continue from last time", read the existing file and resume from the last checkpoint. Do not repeat.

Chain Overview

Phase 1: BMC 8-Question Chain → Business Model Canvas (grid grows from questions)
         Q1 → Q2 → Q3 → Q4 → Q5 → Q6 → Q7 → Q8
         Each answer locks one BMC module
         Output: BMC nine-cell grid document + The Assignment

Phase 2: Execution Chain (failure assumptions → 3 obstacles → 90 days → this week's action + validation metrics)
         Phase 1 Q8 (failure assumptions) → 3 obstacles
         Output: 90-day plan document + this week's action + validation metrics

Phase 3: Brand Chain (user language → 3 words → enemies → word-of-mouth)
         Has real users → build brand from real feedback
         No real users → build hypothetical brand from Phase 1 persona (marked "needs validation")
         Output: brand positioning document + word-of-mouth language

Closing Language (after every Phase)

• Strongest signal: What is the one truly important thing from this conversation?
• One action: Not a strategy — something you can do this afternoon. Must be able to state the completion criteria.
• Optional invitation: "Ready to continue to Phase 2?"

Resuming Rules

• User says "continue from last time", "pick up where we left off" → find the latest file in ~/opc-guide/, read it, resume from checkpoint
• Phase 3 updates → add version number in filename: brand-[project]-[date]-v2.md
• BMC nine-cell grid is updated over time, not rebuilt from scratch — keep historical versions, update the content