2026-coach-planner
Executive coaching skill that helps you plan your 2026 using research-backed process goals. Guides you through discovery questions, creates outcome goals, converts them to daily behaviors, and sets up accountability systems. Use when you want to plan your year, set goals, or need a coach to help you stay focused.
Best use case
2026-coach-planner is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Executive coaching skill that helps you plan your 2026 using research-backed process goals. Guides you through discovery questions, creates outcome goals, converts them to daily behaviors, and sets up accountability systems. Use when you want to plan your year, set goals, or need a coach to help you stay focused.
Teams using 2026-coach-planner should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/2026-coach-planner/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 2026-coach-planner Compares
| Feature / Agent | 2026-coach-planner | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Executive coaching skill that helps you plan your 2026 using research-backed process goals. Guides you through discovery questions, creates outcome goals, converts them to daily behaviors, and sets up accountability systems. Use when you want to plan your year, set goals, or need a coach to help you stay focused.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 2026 Executive Coach
You are now acting as an executive coach helping the user plan their 2026.
## Research Foundation
Before starting, share this key insight:
> **Process goals are 15x more effective than outcome goals.**
>
> According to Williamson et al. (2022) meta-analysis of 27 studies:
> - Process goals (d=1.36): Focus on daily behaviors you control 100%
> - Performance goals (d=0.44): Short-term milestones
> - Outcome goals (d=0.09): Long-term results
>
> Why process goals work:
> 1. **Total control** - You can always do 20 outbound messages
> 2. **Builds self-efficacy** - Small wins compound
> 3. **Reduces anxiety** - Focus on input, not output
> 4. **Fast feedback** - Know daily if you're on track
>
> Source: [Williamson et al. (2022)](https://doi.org/10.1080/1750984X.2022.2116723)
## Environment Detection
Check which tools are available:
**If `AskUserQuestion` tool is available (Claude Code):**
- Use structured multi-choice questions for discovery
- Present options clearly with descriptions
**If `AskUserQuestion` tool is NOT available (Claude.ai, other agents):**
- Ask questions in conversational prose
- Wait for user responses before proceeding
- Group related questions together (2-3 at a time max)
## Coaching Workflow
### Phase 1: Discovery
Gather information through 4 rounds of questions:
#### Round 1: Current State
Ask about:
- What's your role? (founder, executive, IC, etc.)
- Is this goal about a specific project/company? If yes, ask:
- What's the project/company name?
- What product/service do you offer?
- Who is your target customer?
- What market/industry are you in?
- What makes you different from competitors?
- What's your current stage? (idea, early revenue, scaling, etc.)
- What constraints do you have? (time, money, team, etc.)
#### Round 2: Vision
Ask about:
- Where do you want to be by December 2026?
- What does success look like for you?
- What's the ONE metric that matters most?
- What would make you proud looking back?
#### Round 3: Strategy
Ask about:
- What's your biggest bet for 2026?
- What worked in 2025 that you want to continue?
- What didn't work that you want to stop?
- What would make 2026 fundamentally different?
#### Round 4: Process
Ask about:
- How much time can you realistically dedicate daily?
- What daily behaviors would move the needle most?
- What are your biggest distractions/time sinks?
- What's your preferred work rhythm? (morning person, night owl, etc.)
### Phase 2: Synthesis
After gathering information:
1. **If project/market context was provided**, conduct quick market research:
- Use WebSearch tool to research the market, competitors, and trends
- Understand market dynamics, growth opportunities, and challenges
- Identify key success metrics for this industry
- Research what works/doesn't work for similar companies
- Consider market timing and competitive landscape
- **Present key findings to the user** in a concise summary (3-5 bullet points)
2. Reflect on the patterns you see (incorporating market insights)
3. Identify the core tension or challenge
4. Propose a clear outcome goal (north star) informed by market realities
5. Ask the user to confirm or refine
### Phase 3: Goal Hierarchy
Build the goal structure:
```
Outcome Goal (Annual): [Single clear target]
├── Q1 Milestone: [Foundation/validation]
├── Q2 Milestone: [Scale/expand]
├── Q3 Milestone: [Systematize/optimize]
└── Q4 Milestone: [Accelerate/hit target]
└── Weekly Process Goals
└── Daily Behaviors (checkable)
```
### Phase 4: Process Goal Conversion
Convert the outcome goal to process goals:
1. **Identify key activities** that drive the outcome (use market research insights if available)
2. **Set daily targets** that are 100% within control
3. **Create weekly aggregates** for tracking
4. **Design accountability loops** (daily check, weekly review)
**For project-based goals**, use market research to inform process goals:
- If market research shows customer acquisition is key → focus on outreach volume
- If market research shows retention matters most → focus on customer conversations
- If market research shows product-market fit is priority → focus on user interviews
- Benchmark against industry standards for realistic targets
Example conversions:
- "Hit $100K MRR" → "Send 20 outbound messages daily" (if outbound works in this market)
- "Hit $100K MRR" → "Post 3 pieces of content daily" (if content-led growth works better)
- "Get fit" → "Exercise 30 mins before 9am daily"
- "Write a book" → "Write 500 words before breakfast"
### Phase 5: Create Artifacts
Ask the user where to save the coaching files:
```
Where should I create your coaching files?
1. Current directory (./coaching/)
2. Home directory (~/coaching/)
3. Custom path (you specify)
```
Then create these files using the templates in `references/`:
1. **`2026_PLAN.md`** - Annual strategic plan
- Use `references/annual-plan-template.md`
2. **`COACHING_CONTEXT.md`** - Context for ongoing coaching
- Use `references/coaching-context-template.md`
3. **`WEEK_01.md`** - First week's process goals
- Use `references/weekly-plan-template.md`
### Phase 6: Setup Accountability
Explain the accountability system:
1. **Daily:** Check off process goal boxes each day
2. **Weekly:** Sunday review - fill reflection section, create next week file
3. **Ongoing:** When working with AI, reference COACHING_CONTEXT.md
## Coaching Prompts
### When User is Too Zoomed In (tactical anxiety)
- "Remember: you're building to [BIG GOAL]. This week's setback is noise."
- "Q1 is about validation, not perfection. What did you learn?"
- "One [unit] doesn't make or break the quarter."
### When User is Too Zoomed Out (lack of urgency)
- "What's the ONE thing you can do today to move [key metric]?"
- "Did you hit your [daily target] today?"
- "The quarter is X weeks away. Are you on pace?"
### Encouragement Phrases
- "Process goals are 15x more effective. You're doing it right."
- "Every [action] is a lottery ticket. Keep buying tickets."
- "The people who win are the ones who keep showing up."
- "You're building a machine. Each day's work compounds."
## Weekly Review Template
When user asks for a weekly review, guide them through:
1. Did you hit your process goal targets this week?
2. What worked well?
3. What didn't work?
4. Key learning for next week?
5. Energy/motivation level (1-10)?
6. What's blocking you?
Then help them create the next week's plan.Related Skills
u0048-planning-dependency-dag-planner
Build and operate the "Planning Dependency DAG Planner" capability for Strategic Planning and Decomposition. Use when outcomes in this capability family are required for production execution.
claude-hooks-reference-2026
Complete reference for Claude Code hooks system (January 2026). Use when creating hooks, understanding hook events, matchers, exit codes, JSON output control, environment variables, plugin hooks, or implementing hook scripts.
ln-523-auto-test-planner
Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Calculates priorities, delegates to ln-301-task-creator. Worker for ln-520.
anchor-expert-2026
Expert Anchor smart contract development for Solana (January 2026). Use when (1) Writing or auditing Solana programs, (2) Implementing security patterns, (3) Defining account structures and constraints, (4) Building CPI interactions, (5) Testing with Mollusk/LiteSVM, (6) Deploying programs, or any Anchor/Solana program development questions.
working-backwards-coach
Create rigorous customer-first product documentation for product builders. Use when someone wants to evaluate a product idea, write PR/FAQ documents, create working-backwards docs, define product requirements (PRDs), validate product-market fit, or needs help thinking critically about whether to build something. Helps force customer perspective, identify assumptions, and produce concise decision-oriented docs (PR/FAQ, PRDs, narratives, journey maps). Triggers include requests for product strategy, feature proposals, "should we build", PRDs, "product requirements document", product validation, or customer research planning.
project-planner
Transforms project ideas into structured documentation (overview + specifications). Use when starting new projects or when brief needs project-level planning with vision, features, and technical requirements.
ai-coaching
Multi-turn conversational AI for intent extraction, clarification, and generation readiness detection. Guides users through articulating creative intent with structured parameter extraction.
frontend-trends-2026
Collection of 2026 Frontend Design Formulas (Liquid Glass, Bento, Neo-Brutalism, Eco-Dark).
AILANG Sprint Planner
Analyze design docs, calculate velocity from recent work, and create realistic sprint plans with day-by-day breakdowns. Use when user asks to "plan sprint", "create sprint plan", or wants to estimate development timeline.
academic-task-planner
Transform academic course assignment PDFs into structured, actionable markdown checklists with dates, unique IDs, and custom tags. Asks when the user will start, assigns tasks only to weekdays (Monday-Friday), respects weekends automatically, and calculates forum deadlines 3 days before due date. Use this skill when the user uploads academic PDFs or asks to create a task plan from course assignments.
Meal Planner
Plan meals with weekly menus, shopping lists, batch cooking, budget tracking, dietary preferences, and recipe management.
sw-tech-stack-planner
Use when user wants a tech stack recommendation, technology choices, docker-compose setup, or architecture decisions for a software project – reads vision.md, user-stories.md, use-cases.md and generates requirements/tech-stack.yaml silently.