Skip to content

Commit eef57e9

Browse files
antonyevansantonyevans
committed
feat: add morning-brief and find-my-business skills
- operations/morning-brief — daily morning brief generator (pulls from goals summary, task board, competitor digest, content pipeline) - product/find-my-business — interactive startup idea discovery skill, PG/YC/Mom Test/JTBD methodology updated for AI era; includes scripts, reference docs, lean canvas and conviction scorecard templates Both skills sanitised: project-specific paths generalised, personal names/session history removed from learnings.md.
1 parent 7a60cf7 commit eef57e9

15 files changed

Lines changed: 1799 additions & 0 deletions

File tree

‎operations/morning-brief/SKILL.md‎

Lines changed: 103 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,103 @@
1+
---
2+
name: morning-brief
3+
description: >
4+
Generates a structured morning brief and writes it to the daily review file.
5+
Pulls from: current priorities (goals summary), active task board, latest competitor
6+
digest, and content pipeline status. Fires automatically on weekdays. Output is
7+
the morning intention section of your daily review file.
8+
argument-hint: "(no arguments needed — runs automatically)"
9+
triggers:
10+
- "run morning brief"
11+
- "morning brief"
12+
- "generate morning brief"
13+
- "/morning-brief"
14+
---
15+
16+
# /morning-brief — Daily Morning Brief
17+
18+
Generate a structured morning brief and write it to today's daily review file.
19+
20+
---
21+
22+
## Instructions
23+
24+
### Step 1 — Establish today's date
25+
26+
```bash
27+
date +%Y-%m-%d
28+
```
29+
30+
Use the output as `TODAY` (format: `YYYY-MM-DD`). Also derive:
31+
- `DAY_NAME` — full weekday name (Monday, Tuesday, etc.)
32+
- `MONTH_NAME` — full month name
33+
- `DAY_NUM` — day of month
34+
35+
---
36+
37+
### Step 2 — Read context sources (run all reads in parallel)
38+
39+
1. **Goals summary** — your goals summary file (e.g. `goals/_summary.md`)
40+
Extract: This Month's Top Priorities list (the numbered items)
41+
42+
2. **Task board** — your task board index (e.g. `tasks/_index.md`)
43+
Extract: All Active Tasks where status is `active` or `in-progress`, priority is `critical` or `high`. Include agent and ID.
44+
45+
3. **Latest competitor digest** — find the most recent file in your competitor digests directory (e.g. `network/competitors/digests/`)
46+
Extract: Top 2–3 signals only. Look for "Key Signals", "Top Signals", or the first substantive section. Skip boilerplate.
47+
48+
4. **Content pipeline** — your content pipeline index (e.g. `content/posts/_posts-index.md`)
49+
Extract: All posts with stage READY or SCHEDULED. Note the next post due if any has a date.
50+
51+
---
52+
53+
### Step 3 — Compose the brief
54+
55+
Build a brief with exactly these sections, in this order:
56+
57+
```markdown
58+
---
59+
date: YYYY-MM-DD
60+
day: DAY_NAME
61+
type: daily-review
62+
---
63+
64+
# Morning Brief — DAY_NAME, MONTH_NAME DAY_NUM, YEAR
65+
66+
## Top Priorities
67+
[Numbered list pulled from monthly priorities in goals summary — max 5 items]
68+
69+
## Active Tasks (High/Critical)
70+
[Table or bullet list: ID | Title | Agent — only critical and high priority active tasks]
71+
72+
## Competitor Signal
73+
[2–3 bullet points from latest digest. Include digest date. If no digest from last 2 days, note it.]
74+
75+
## Content Pipeline
76+
[READY posts: list with IDs and titles]
77+
[SCHEDULED posts: list with IDs, titles, and scheduled dates if known]
78+
[Note: if pipeline is empty or all posts are in IDEA/DRAFT, flag it]
79+
80+
## One Focus
81+
[Single most important thing to do today, derived from priorities + task board. One sentence, direct.]
82+
```
83+
84+
Keep the brief tight. No padding. The goal is to read it in under 2 minutes.
85+
86+
---
87+
88+
### Step 4 — Write to the daily review file
89+
90+
Target path: your daily review directory (e.g. `reviews/daily/YYYY-MM-DD.md`)
91+
92+
- **If the file does not exist:** write the full brief as the file content.
93+
- **If the file already exists:** prepend the brief above any existing content, separated by `---`.
94+
95+
Do not overwrite existing evening reflection or other content.
96+
97+
---
98+
99+
### Step 5 — Confirm
100+
101+
Output to the chat:
102+
- Confirmation that the brief was written, with the file path
103+
- The "One Focus" line so it's visible without opening the file

‎product/find-my-business/SKILL.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
---
2+
name: find-my-business
3+
description: Guides a founder interactively from "no idea" through idea generation, rapid validation, and commitment to a business — synthesizing PG, YC, Lean Startup, Mom Test, JTBD, and gstack office-hours methodology updated for the AI era. Produces founder profiles, scored idea candidates, validation sprint results, conviction scorecards, and 30-day action plans. Use when the user wants to find a business to start, explore startup ideas, figure out what to build, get unstuck on what to work on, or brainstorm business directions. Do NOT use when the user already has a specific idea to evaluate (use assess-category or stress-test instead), wants a business plan written, or needs a pitch deck reviewed.
4+
argument-hint: "[optional: context about where you are in the search — e.g. 'resuming', 'I have some ideas', 'starting fresh']"
5+
---
6+
7+
# /find-my-business — Startup Idea Discovery
8+
9+
Interactive search process from "I don't know what to build" to "I'm working on this company." Not a business plan generator — a structured conversation that interviews, generates, validates, pushes back, and narrows toward conviction.
10+
11+
## Step 0: Session Initialization
12+
13+
1. Read `references/learnings.md`. Summarize the 3-5 most relevant bullets for this session.
14+
2. Read `references/edge-cases.md` for any factual corrections.
15+
3. Check if `business-search/state.json` exists (adjust path to match your project structure).
16+
- **Exists:** Read state. Present one-paragraph summary of where we left off — current phase, active ideas, what was decided last session. Ask: "Ready to continue, or want to revisit anything?"
17+
- **Does not exist:** First session. Proceed to Step 1.
18+
4. Route by phase in state file:
19+
- `profile` or missing → Step 1
20+
- `ideation` → Step 2
21+
- `validation` → Step 3
22+
- `deep-validation` → Step 4
23+
- `commitment` → Step 5
24+
25+
## Step 1: Founder Profile Mining
26+
27+
1. Read your founder context files — about-me, constraints, anti-goals, and ideal-company (adjust paths to match your project structure).
28+
2. Interview to fill gaps. Ask 3-5 targeted questions, one at a time:
29+
- What problems have you personally experienced that frustrated you enough to complain about them?
30+
- What industries or domains do you know deeply enough to spot what others miss?
31+
- What makes you irrationally excited — even if it seems impractical?
32+
- What do people come to you for help with, unprompted?
33+
- What's an unfair advantage you have that most people don't see?
34+
3. Synthesize into a Founder Profile. Read `references/methodology.md` Section 1 for the profile template.
35+
4. **HUMAN CHECKPOINT:** Present the profile. Flag 2-3 items marked "uncertain — correct me." Get confirmation.
36+
5. Write approved profile to `business-search/founder-profile.md` (adjust path to match your project).
37+
6. Execute `scripts/update_state.py --action init` to create state file.
38+
39+
**Why (PG):** The best ideas live at the intersection of founder identity and market gaps. Generic idea lists fail because they skip this grounding.
40+
41+
## Step 2: Idea Generation (Divergent)
42+
43+
1. Read `references/methodology.md` Section 2 for the seven generation angles.
44+
2. Read your anti-goals file — this is a **hard filter**. Any idea violating an anti-goal is killed immediately with explanation.
45+
3. Generate candidates from all seven angles. For each, note which angle produced it.
46+
4. Score each idea: execute `scripts/score_idea.py` with founder profile, anti-goals, and any market signals.
47+
5. **HUMAN CHECKPOINT:** Present batch of 5-7 ideas, ranked by score. For each: one-line description, score breakdown, which angle generated it, and one honest concern. Ask: "Which of these resonate? Which make you feel something — even discomfort?"
48+
6. Kill ideas that don't resonate (log reason in state). Explore resonant ones deeper.
49+
7. If fewer than 2 survive, generate one more batch. But max 3 rounds — then force convergence: "These are your candidates. Pick 2-3 to validate."
50+
8. Execute `scripts/update_state.py --action update --phase ideation` with surviving ideas.
51+
52+
**Why:** Divergent phase must be wide but time-boxed. Unlimited generation without convergence triggers shiny object syndrome.
53+
54+
## Step 3: Rapid Validation Sprints (Convergent)
55+
56+
1. **Premise Challenge** (before validation): For each surviving idea, challenge 3 premises:
57+
- Is this the right problem, or a symptom of a deeper one?
58+
- What happens if nobody builds this — what do people keep doing?
59+
- What existing thing already solves 80% of this?
60+
2. For each idea (typically 2-3), run a compressed validation sprint. Read `references/methodology.md` Section 3 for the full protocol. Key steps:
61+
- Market research via WebSearch + librarian agent (size, growth, timing)
62+
- Customer evidence: Reddit threads via WebSearch (`site:reddit.com`), review complaints, forum posts showing real pain
63+
- Competitive landscape: who exists, what they miss, where the gap is
64+
- **Landscape Awareness:** Three-layer synthesis — conventional wisdom → current discourse → whether your data contradicts it. If contradiction exists, flag it as a potential insight.
65+
- Apply the Six Forcing Questions from `references/methodology.md` Section 4 to pressure-test each idea
66+
- Draft Lean Canvas using `assets/lean-canvas-template.md`
67+
- Generate Mom Test conversation script (read `references/methodology.md` Section 5)
68+
3. **HUMAN CHECKPOINT:** Present validation results side by side in a comparison table. Include explicit recommendation + dissenting view. Ask: "For each idea — pursue deeper, pivot, or kill?"
69+
4. Execute `scripts/update_state.py --action update --phase validation` with decisions.
70+
71+
**Why (Blank/Fitzpatrick):** Problem-solution fit precedes product-market fit. Evidence from real people beats plausible reasoning.
72+
73+
## Step 4: Deep Validation (1-2 Ideas)
74+
75+
1. Prepare customer conversation guide: who to talk to, where to find them, what to ask (Mom Test rules from `references/methodology.md` Section 5).
76+
2. **HUMAN CHECKPOINT:** "Ready to talk to potential customers? Here are 5 specific people/roles to reach and exactly what to ask."
77+
3. Help the founder process conversation learnings between sessions.
78+
4. Build conviction scorecard: execute `scripts/score_conviction.py` using `assets/conviction-scorecard-template.md` dimensions.
79+
5. Spawn critic agent to stress-test the strongest idea.
80+
6. **Stuck detection:** At every interaction, check for stuck patterns. Read `references/stuck-interventions.md` and apply the matching intervention. Do not wait for the founder to ask for help.
81+
7. **HUMAN CHECKPOINT:** Present conviction scorecard with bull case and bear case. Ask: "What would need to be true for you to commit to this?"
82+
83+
## Step 5: Commitment + Transition
84+
85+
1. **HUMAN CHECKPOINT:** "Based on everything — the evidence, the conversations, your energy — are you ready to commit?"
86+
2. If yes:
87+
- Populate your ideal-company file with the chosen business
88+
- Create a 30-day action plan: specific, concrete, time-boxed next steps
89+
- Present 3 pacing alternatives: aggressive / moderate / conservative
90+
- Execute `scripts/update_state.py --action update --phase committed`
91+
3. If not: Diagnose what's missing. Loop to the appropriate step.
92+
93+
**Why (PG):** "No idea feels great before you start. The initial idea is just a starting point." The skill helps cross the commitment threshold with conviction enough to act, not certainty enough to relax.
94+
95+
## Step 6: Closing Feedback Gate
96+
97+
Ask: "Did this session move you forward? Any corrections or exceptions I should learn from?"
98+
99+
Route response:
100+
- Behavioral ("don't do X", "I prefer Y") → append to `references/learnings.md`
101+
- Factual ("the format is actually Z") → append to `references/edge-cases.md`
102+
- "Never do X again" → add rule to this file
103+
- Approval / "this was perfect" → save output to `assets/approved-examples/`
104+
- No response → do nothing. Never block on feedback.
105+
106+
## Gotchas
107+
108+
- **Symptom:** All ideas sound plausible but founder can't get excited about any. **Cause:** Ideas generated from market gaps only, not grounded in founder's personal pain. **Fix:** Return to Step 1, dig deeper with PG's "what have you complained about?" and "what's broken that you notice because of your unusual experience?"
109+
- **Symptom:** Founder keeps asking for "more research" on ideas already validated across 3+ sessions. **Cause:** Analysis paralysis / fear of commitment. **Fix:** Invoke stuck-pattern intervention — force time-boxed decision: "If you had to pick ONE today, which would it be?" Read `references/stuck-interventions.md`.
110+
- **Symptom:** State file missing when founder has done previous sessions. **Cause:** File deleted, moved, or session opened in a different working directory. **Fix:** Check common paths. If truly lost, reconstruct from conversation history.
111+
- **Symptom:** Anti-goals violated in idea batch (e.g., idea requires 24/7 ops or large low-skilled workforce). **Cause:** Anti-goals not read or not applied as hard filter. **Fix:** Always read your anti-goals file before Step 2. `score_idea.py` includes anti-goal check — run it.
112+
113+
## Rules
114+
115+
1. Reference files are required, not optional — read `references/methodology.md` before generating ideas, `references/stuck-interventions.md` before diagnosing blocks.
116+
2. Multiple options at every human checkpoint — never present a single idea or single recommendation.
117+
3. Explicit approval gate before any irreversible action — populating `ideal-company.md`, recommending the founder contact specific people.
118+
4. Anti-goals are a hard filter — every idea checked against the founder's anti-goals file. Violation = immediate kill with explanation.
119+
5. Evidence over reasoning — cite the evidence for every idea. If there is no evidence, say "this is speculative — I have no market data" rather than making it sound validated.
120+
6. Push toward action — when the founder has been researching the same ideas for 2+ sessions without customer conversations, invoke the stuck-pattern intervention.
121+
7. State file is sacred — every session reads state at start and writes state at end.
122+
8. Never skip Step 1 (Profile) — even if the founder says "I already know my strengths."
123+
9. Anti-sycophancy — never say "that's interesting," "there are many ways," "you might consider," or "could work." Take a position on every answer. State what evidence would change your mind. Push once, then push again.
124+
10. No AI vocabulary — never use "delve," "crucial," "robust," "comprehensive," "leverage," "landscape." Be direct, specific, punchy. Name subreddits, companies, people, numbers.
125+
11. Consolidate `references/learnings.md` at 80 lines; hard cap at 100.
126+
127+
---
128+
<!-- Built with Agent Engineer Master — get your own production-ready skill: www.agentengineermaster.com/skill-engineer -->

‎product/find-my-business/assets/conviction-scorecard-template.md‎

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
# Conviction Scorecard — [Idea Name]
2+
3+
**Date:** YYYY-MM-DD
4+
**Sessions spent on this idea:** N
5+
**Customer conversations completed:** N
6+
7+
---
8+
9+
## Dimensions (Score 1-5)
10+
11+
### 1. Problem Clarity (Weight: 25%)
12+
*Can you state the problem in one sentence that a stranger would understand?*
13+
14+
- **Score:** [1-5]
15+
- **Evidence:** [What you know about the problem — sources, quotes, data]
16+
- **1 =** Vague sense something is broken, no specifics
17+
- **3 =** Clear problem statement with 2-3 evidence sources
18+
- **5 =** Acute, well-defined problem with customer quotes confirming urgency
19+
20+
### 2. Customer Pull (Weight: 25%)
21+
*Are customers pulling toward a solution, or are you pushing one at them?*
22+
23+
- **Score:** [1-5]
24+
- **Evidence:** [Customer signals — commitments, not compliments]
25+
- **1 =** No customer conversations, or only compliments received
26+
- **3 =** 3+ conversations, at least one person asked "when can I use this?"
27+
- **5 =** Deposit, LOI, or someone willing to be a design partner
28+
29+
### 3. Founder Fit (Weight: 20%)
30+
*Does this play to your specific strengths, networks, and energy?*
31+
32+
- **Score:** [1-5]
33+
- **Evidence:** [Which founder advantages apply]
34+
- **1 =** Generic opportunity anyone could pursue; no unique angle
35+
- **3 =** Leverages 1-2 founder advantages (domain knowledge, network)
36+
- **5 =** Deep domain expertise + network access + genuine excitement
37+
38+
### 4. Market Timing (Weight: 15%)
39+
*Why now? What changed that makes this possible/urgent today?*
40+
41+
- **Score:** [1-5]
42+
- **Evidence:** [Timing signals — technology change, regulation, behavior shift]
43+
- **1 =** No clear "why now" — could have been built 5 years ago
44+
- **3 =** Plausible timing story (AI capability, market shift)
45+
- **5 =** Clear inflection point that didn't exist 2 years ago
46+
47+
### 5. Competitive Moat (Weight: 15%)
48+
*What would stop a well-funded competitor from copying this in 6 months?*
49+
50+
- **Score:** [1-5]
51+
- **Evidence:** [Defensibility source]
52+
- **1 =** Thin wrapper, no proprietary asset, easily replicated
53+
- **3 =** One defensible element (domain data, workflow integration, compliance)
54+
- **5 =** Multiple reinforcing moats (network effects + proprietary data + switching costs)
55+
56+
---
57+
58+
## Composite Score
59+
**Weighted score:** [calculated] / 5.0
60+
61+
| Range | Interpretation |
62+
|-------|---------------|
63+
| 4.0+ | Strong conviction — ready to commit |
64+
| 3.0-3.9 | Promising — specific gaps to address before committing |
65+
| 2.0-2.9 | Weak — needs significant validation or pivot |
66+
| <2.0 | Kill — redirect energy elsewhere |
67+
68+
---
69+
70+
## Bull Case
71+
[2-3 sentences: the best realistic scenario if everything goes right]
72+
73+
## Bear Case
74+
[2-3 sentences: the most likely failure mode]
75+
76+
## What Would Change This Score
77+
- To raise Problem Clarity: [specific action]
78+
- To raise Customer Pull: [specific action]
79+
- To raise Founder Fit: [specific action, or "this is fixed — can't be changed"]
80+
- To raise Market Timing: [specific action, or "this is structural — can't be changed"]
81+
- To raise Competitive Moat: [specific action]
82+
83+
## Decision
84+
[ ] Commit — start building
85+
[ ] Continue validating — specific gap to close: [gap]
86+
[ ] Pivot — keep the [element] but change [element]
87+
[ ] Kill — reason: [one sentence]

‎product/find-my-business/assets/lean-canvas-template.md‎

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
# Lean Canvas — [Idea Name]
2+
3+
**Date:** YYYY-MM-DD
4+
**Status:** Draft | Validated | Killed
5+
**Confidence:** Low | Medium | High (overall, based on evidence quality)
6+
7+
---
8+
9+
## 1. Problem
10+
Top 3 problems this solves (ordered by severity):
11+
1. [Problem 1] — Evidence: [source]
12+
2. [Problem 2] — Evidence: [source]
13+
3. [Problem 3] — Evidence: [source]
14+
15+
**Existing alternatives:** What are people doing today to solve this? (The real competitor is usually a spreadsheet, manual process, or "just live with it.")
16+
17+
## 2. Customer Segments
18+
**Early adopters** (who has this problem most acutely?):
19+
- [Specific role/title at specific company type]
20+
- [How to find them: subreddit, community, conference, LinkedIn group]
21+
22+
**Broader market** (who else has this problem, less acutely?):
23+
- [Segment description]
24+
25+
## 3. Unique Value Proposition
26+
[One sentence: why this, why now, why you]
27+
28+
**High-level concept:** [X for Y analogy, if it helps — e.g., "Stripe for [domain]"]
29+
30+
## 4. Solution
31+
Top 3 features matching each problem:
32+
1. [Feature] → solves [Problem 1]
33+
2. [Feature] → solves [Problem 2]
34+
3. [Feature] → solves [Problem 3]
35+
36+
**Narrowest wedge:** What's the smallest version someone pays for this week?
37+
38+
## 5. Channels
39+
How do you reach early adopters? (Pick ONE primary channel)
40+
- Primary: [specific channel — e.g., "r/[subreddit] + cold DM to posters"]
41+
- Secondary: [backup channel]
42+
43+
## 6. Revenue Streams
44+
- Pricing model: [subscription / usage / one-time / marketplace cut]
45+
- Price point: $[X]/[period]
46+
- Evidence for willingness to pay: [source, or "untested"]
47+
48+
## 7. Cost Structure
49+
- Fixed costs: [hosting, tools, subscriptions]
50+
- Variable costs: [per-customer costs]
51+
- Break-even: [X customers at $Y/month]
52+
53+
## 8. Key Metrics
54+
What proves this is working? (Not vanity metrics)
55+
- [Metric 1]: [target] — measures [what]
56+
- [Metric 2]: [target] — measures [what]
57+
- [Metric 3]: [target] — measures [what]
58+
59+
## 9. Unfair Advantage
60+
What cannot be easily copied?
61+
- [Advantage] — Why it's defensible: [explanation]
62+
63+
If blank: acknowledge it. "No unfair advantage yet" is honest. Most startups don't have one on day one — it's built over time.
64+
65+
---
66+
67+
## Assumptions to Test (Ordered by Risk)
68+
1. [Riskiest assumption] — How to test: [experiment]
69+
2. [Second riskiest] — How to test: [experiment]
70+
3. [Third] — How to test: [experiment]
71+
72+
## Open Questions
73+
- [Question that could change the canvas significantly]

0 commit comments

Comments
 (0)