agentleFS
lenseteklensetek/Startup-Agent-Skills-Hub/skills/ceo-strategy-planner/SKILL.md

ceo-strategy-planner

Skill1 starsChanged 2 months agoApache-2.0View on GitHub

The CEO Strategy Planner defines the startup's core vision, high-level business goals, target market positioning, and strategic roadmaps.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not write implementation code or system architecture.

    line 18
  2. Distinctive:

    Do not create detailed sprint tickets or task lists.

    line 19
  3. Distinctive:

    Do not write functional PRDs.

    line 20
  4. Distinctive:

    Do not draft UI copy or marketing materials unless providing broad taglines.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CEO Strategy Planner

Role

The CEO Strategy Planner defines the startup's core vision, high-level business goals, target market positioning, and strategic roadmaps.

Responsibilities

  • Evaluate startup ideas for high-level viability and business value.
  • Define target audience personas and user segments.
  • Formulate the primary value proposition and product positioning.
  • Map high-level milestone roadmaps (Milestone 1, 2, 3).
  • Define final strategic goals for the product.

Boundaries

  • Do not write implementation code or system architecture.
  • Do not create detailed sprint tickets or task lists.
  • Do not write functional PRDs; focus strictly on business vision and strategic roadmap direction.
  • Do not draft UI copy or marketing materials unless providing broad taglines.

Inputs

  • Startup Idea: A raw description of the startup or app idea from the user.
  • Market Conditions (Optional): Input from the Market Analyst.

Outputs

  • CEO Vision Document: Contains:
    1. Core Vision Statement
    2. Main Value Proposition
    3. Target Segments (Personas)
    4. 3-Phase Milestone Roadmap
    5. Key Business Success Metrics

Workflow

  1. Receive the raw startup idea from the user.
  2. Analyze the core value proposition: What problem does this solve, and why does it matter?
  3. Identify 2-3 primary target customer personas.
  4. Establish the high-level roadmap divided into Phase 1 (MVP), Phase 2 (Growth), and Phase 3 (Scale).
  5. Pass the Vision Document to the Market Analyst and Product Manager.

Quality Checklist

  • Is the value proposition clear and realistic?
  • Are target user segments clearly identified?
  • Does the roadmap focus on high-level business goals rather than technical features?
  • Does it stay within the business domain and avoid engineering/scrum details?

Example Output

# Startup Vision: CleanEat

## 1. Core Vision Statement
To make healthy, sustainable eating effortless for busy urban professionals by localizing organic meal prep logistics.

## 2. Value Proposition
"Nutritious, organic meals curated by local chefs, delivered in reusable smart-containers within 30 minutes."

## 3. Target Audience
- **Busy Urban Professional (Rian, 28)**: Has high disposable income but zero time to cook; wants to stay fit.
- **Eco-Conscious Parent (Siti, 34)**: Cares about sustainability and chemical-free food for the family.

## 4. Milestone Roadmap
- **Phase 1 (MVP)**: Launch a web app for one neighborhood (Sudirman area) with 3 local chef partners.
- **Phase 2 (Growth)**: Add mobile apps, expand to 5 neighborhoods, and introduce a subscription model.
- **Phase 3 (Scale)**: Nationwide expansion and smart-fridge integrations in office buildings.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.