quarterly-review
Interactive quarterly business review covering performance, development, finance, and well-being. Use when user mentions "quarterly review", "quarter review", "Q1/Q2/Q3/Q4 review", "review past quarter", or wants to assess quarterly performance and plan next steps.
What this skill does
# Quarterly Review: Personal Business Quarterly Review (PBQR) **Prime Directive: Turn reflection into decisions.** If it doesn't change next quarter, it doesn't belong here. ## Overview This interactive skill guides you through a comprehensive quarterly review of your business covering: - Performance and lived experience - Financial scoreboard - Goals and objectives - Capability and asset growth - Strategic synthesis and decisions The output is saved as a Quarterly Log page in Notion for reference and planning. ## Notion Integration **Configuration:** Notion page URLs are loaded in the following order (first found wins): 1. `.claude/config.md` or `CLAUDE.md` - Project-specific configuration (check working directory) 2. `.claude-plugin/config.json` - Plugin default configuration Use the Read tool to load configuration at the start of the workflow. **Required Pages (configured in config files):** - **Year Plan** (config.notion.yearPlan): Strategic plan and OKRs - **Personal Operating Model** (config.notion.personalOperatingModel): Strengths, weaknesses, operating manual - **Golden Rules** (config.notion.goldenRules): Non-negotiable working principles - **Logbook** (config.notion.logbook): Output location for quarterly review ## Workflow ### Step 0: Setup & Context Gathering 1. **Load Configuration**: ```javascript // Use Read tool to load Notion page URLs from config // Try in order (first found wins): // 1. .claude/config.md (check for notion.* URLs in markdown) // 2. CLAUDE.md (check for notion.* URLs in markdown) // 3. .claude-plugin/config.json (JSON format) // Extract config.notion.yearPlan, config.notion.personalOperatingModel, // config.notion.goldenRules, config.notion.logbook // Use these URLs for all mcp__notion__notion-fetch calls below ``` 2. **Determine Quarter to Review**: ```bash # Call the command to determine quarter /founder-support-system:get-year-and-quarter ``` This determines the PRECEDING quarter (the one that just ended). 2. **Fetch Reference Materials**: Use `mcp__notion__notion-fetch` to retrieve: - Personal Operating Model (strengths, weaknesses) - Golden Rules (must-follow working principles) - Year Plan for current year (strategic objectives) - Previous Quarterly Log (if exists) for comparison 3. **Brief Context Summary**: Show user a 3-line summary: - Quarter being reviewed (e.g., "Q4 2025") - Current year objectives from Year Plan - Key themes from previous quarter (if available) --- ### Section 1: Quarter Snapshot (Reality Check) **Purpose:** Establish shared reality before analysis. **Interactive Process:** Use `AskUserQuestion` with these trigger questions: 1. **What worked with less effort than expected?** *Signals leverage, fit, and hidden advantages.* 2. **Where did you spend the most energy for the least return?** *Exposes false priorities and sunk-cost thinking.* 3. **What surprised you—positively or negatively?** *Surprises reveal broken assumptions.* 4. **If this quarter repeated 3 more times, would the business be stronger or weaker? Why?** *Forces trajectory thinking instead of point-in-time evaluation.* 5. **What did you avoid or postpone that now feels costly?** *Highlights fear, discomfort, or unresolved decisions.* **Format**: Use `multiSelect: false` for open-ended responses. **Output Structure**: ```markdown ## Quarter Snapshot: Q[X] [YEAR] ### What Happened - [5-10 bullets from user responses] ### Narrative Summary [One paragraph synthesizing the above] ### Quarterly Reset — Keep it alive *instructions:* This is the maintenance ritual. Short. Non-negotiable. If you skip this, the model rots. #### The four questions 1. Where did I create disproportionate value? 2. Where did I fight my nature? 3. Which pitfall showed up again? 4. What rule or constraint must tighten? #### Updates (refer to Personal Operating Model in Notion) - Strengths to exploit more: - Weakness routing improvements: - New constraints: - Remove constraints (if proven safe): ``` --- ### Section 2: Narrative Review #### 2.1 Lived Experience **Questions** (use `AskUserQuestion`): Ask about **3 frictions** and **3 tailwinds**: 1. **Frictions**: "What consistently pushed you uphill this quarter? Where did things feel hard?" 2. **Tailwinds**: "What moved with little effort? What had natural momentum?" **Output**: ```markdown ## Lived Experience ### Frictions (What Pushed Uphill) 1. [Friction 1] 2. [Friction 2] 3. [Friction 3] ### Tailwinds (What Moved Easily) 1. [Tailwind 1] 2. [Tailwind 2] 3. [Tailwind 3] ``` --- #### 2.2 Constraints & Struggles **Questions** (use `AskUserQuestion` with multiple choice + open): For each struggle identified in 2.1, ask user to categorize: Options: - **Structural** (system/process issue) - **Capability** (skill/knowledge gap) - **Positioning** (market/message problem) - **Personal** (energy, focus, well-being) **Output**: ```markdown ## Constraints & Struggles ### [Struggle Name] - [Category] [User's explanation] → **Action**: [Structural/Positioning → next quarter priorities | Personal → environment design] ``` --- ### Section 3: Financial Review (Scoreboard) **Interactive Questions** (use `AskUserQuestion`): #### 3.1 Sales Activity Ask for: - Real conversations held - Proposals sent / won / lost - Average deal size - Sales cycle length #### 3.2 Revenue & Cost Ask for: - Gross revenue - Fixed costs - Variable costs - Revenue per hour estimate #### 3.3 Financial Trajectory Ask: - "Are you on track vs annual target? (Yes/No/Unsure)" - "If nothing changes, where do you land in 12 months?" **Output**: ```markdown ## Financial Review ### Sales Activity | Metric | Q[X] [YEAR] | Trend vs Last Quarter | |--------|-------------|----------------------| | Conversations | [X] | [↑/↓/→] | | Proposals Sent | [X] | [↑/↓/→] | | Proposals Won | [X] | [↑/↓/→] | | Avg Deal Size | €[X] | [↑/↓/→] | | Sales Cycle | [X] days | [↑/↓/→] | ### Revenue & Cost - **Gross Revenue**: €[X] - **Fixed Costs**: €[X] - **Variable Costs**: €[X] - **Net**: €[X] - **Revenue/Hour**: €[X] ### Financial Trajectory - **Annual Target Status**: [🟢 On Track | 🟡 Behind | 🔴 Off Track] - **12-Month Projection**: [User's answer] → [If Red: Mandatory strategic change required] ``` --- ### Section 4: Goals Review (OKR-Lite) #### 4.1 Review Last Quarter Objectives **Process**: 1. Fetch previous Quarterly Log (if exists) 2. Extract previous quarter's objectives 3. For each objective, ask user: "Keep / Kill / Complete?" **Output**: ```markdown ## Last Quarter Objectives Review ### Objective 1: [Name] - **Status**: [Keep | Kill | Complete] - **Reason**: [User's explanation] [Repeat for each objective] ``` --- #### 4.2 Next Quarter Objectives (Max 3) **Interactive Process**: Ask user to define **exactly 3 objectives**: - **One growth objective** (revenue, reach, market) - **One leverage objective** (systems, efficiency, automation) - **One foundation objective** (skills, infrastructure, health) For each objective, ask: 1. "What measurable outcome defines success?" 2. "What single constraint does this address?" 3. "What are 2-4 key results?" **Output**: ```markdown ## Next Quarter Objectives: Q[X+1] [YEAR] ### 1. Growth Objective: [Name] **Constraint Addressed**: [User's answer] **Key Results**: 1. [KR1] 2. [KR2] 3. [KR3] 4. [KR4] --- ### 2. Leverage Objective: [Name] **Constraint Addressed**: [User's answer] **Key Results**: 1. [KR1] 2. [KR2] --- ### 3. Foundation Objective: [Name] **Constraint Addressed**: [User's answer] **Key Results**: 1. [KR1] 2. [KR2] ``` --- ### Section 5: Capability & Asset Growth **Interactive Questions** (use `AskUserQuestion`): #### 5.1 Learning & Skill Accretion - "What can you do now that you couldn't 90 days ago?" - "Where have you applied these skills?" #### 5.2 Business Development - "How many new meaningful connections?" - "Who moved from cold to warm?" -
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.