devstack 0.1.0

package/vendor/skills/skills/fundraising/references/RUBRIC.md

@@ -0,0 +1,39 @@
+# Fundraising — Scoring Rubric (1–5)
+
+Score each dimension from 1 (weak) to 5 (excellent). A strong pack is mostly 4–5s, with no 1s.
+
+## 1) Decision quality (raise vs don’t)
+
+1: No real decision; just “raise money” advice.  
+3: Trade-offs listed but recommendation is vague.  
+5: Clear decision criteria, realistic alternatives, and a falsifiable recommendation.
+
+## 2) Round design coherence
+
+1: Amount/timeline/milestone don’t connect.  
+3: Some connection, but assumptions are hidden.  
+5: Amount range ties directly to milestone, runway, and investor profile; assumptions are explicit.
+
+## 3) Narrative clarity + first impression
+
+1: Generic story; unclear ICP/outcome.  
+3: Clear story but weak proof or muddled first slide.  
+5: Crisp one-liner, strong first slide, and evidence-backed narrative that earns the next meeting.
+
+## 4) Investor fit + targeting
+
+1: Random investor list.  
+3: Basic list, limited rationale.  
+5: ICP-driven list with fit reasons, warm paths, and a realistic sequencing strategy.
+
+## 5) Process executability
+
+1: No tracking, no cadence, no next steps.  
+3: Some steps, but not schedulable.  
+5: Pipeline tracker + weekly targets + follow-up SOP + next-14-days plan.
+
+## 6) Risk handling + safety
+
+1: Ignores legal/financial constraints; overshares.  
+3: Mentions constraints but doesn’t operationalize them.  
+5: Clear boundaries, “questions for counsel,” sensitive info guidance, and explicit risks/open questions.

package/vendor/skills/skills/fundraising/references/SOURCE_SUMMARY.md

@@ -0,0 +1,23 @@
+# Source Summary — Fundraising (Refound/Lenny)
+
+Source: `sources/refound/raw/fundraising/SKILL.md`
+
+## What the original skill emphasized
+
+### Insight 1 — “Don’t raise by default” (Ryan Hoover)
+
+- Challenge the assumption that raising VC is always the right move.
+- Make the **why** and **when** explicit.
+- Understand trade-offs of the “venture treadmill” and consider alternatives (bootstrap/delay).
+
+### Insight 2 — “First impressions win meetings” (Uri Levine)
+
+- The first slide is often the most important because it sets the investor’s first impression.
+- Provide tactical advice on pitch deck structure and the psychology of investor attention.
+- Fundraising is a “dance of 100 no’s”; resilience + process matters.
+
+## How this pack transformed the insights
+
+- Converted the “don’t raise by default” insight into a concrete **Raise Decision Memo** deliverable and a Step 2 decision gate.
+- Converted “first slide matters” into a **Pitch Narrative + Deck Outline** with explicit checks (10-second test) and templates.
+- Converted “100 no’s” into a pipeline-driven execution system: tracker, weekly targets, rejection reasons log, and iteration loop.

package/vendor/skills/skills/fundraising/references/TEMPLATES.md

@@ -0,0 +1,201 @@
+# Fundraising — Templates (Copy/Paste)
+
+Use these to produce the **Fundraising Pack** deliverables from `../SKILL.md`.
+
+## 1) Raise Decision Memo (template)
+
+### Context
+
+- Company / product:
+- Stage + current proof:
+- Runway + constraints:
+
+### The decision
+
+- Decision to make:
+- Decision deadline:
+
+### Why raise (VC)
+
+- What VC enables:
+- Why speed matters (why now):
+- Expected trade-offs (dilution, expectations, focus, control):
+
+### Why not raise (alternatives)
+
+- Bootstrapping plan:
+- Delay-then-raise plan:
+- Other sources (angels/strategic/debt/grants):
+
+### Recommendation + criteria
+
+- Recommendation:
+- We raise if:
+- We do not raise if:
+
+### Risks / Open questions / Next steps
+
+- Risks:
+- Open questions:
+- Next steps:
+
+## 2) Round Design Brief (template)
+
+### Round summary
+
+- Round type (pre-seed/seed/etc.):
+- Target close window:
+- Target amount (range):
+- Target investor profile (check size, stage, thesis, geo):
+
+### Milestone this round buys
+
+- End-of-runway milestone (12–18 months):
+- Leading indicators (monthly):
+
+### Use of funds (high-level)
+
+- Headcount plan:
+- Key bets:
+- Buffer/contingency:
+
+### Assumptions + questions for counsel
+
+- Assumptions:
+- Questions for counsel (instrument/options/rights):
+
+## 3) Pitch Narrative + Deck Outline (template)
+
+### One-liner (what/for whom/outcome)
+
+> We are building **[product]** for **[ICP]** so they can **[outcome]**.
+
+### Slide 1 (strongest point)
+
+- Headline:
+- 1–2 proof bullets (metric/proxy/quote):
+- Why now bullet:
+
+### Talk track (2 minutes)
+
+- Hook:
+- Problem:
+- Why now:
+- Solution + wedge:
+- Proof:
+- Ask:
+
+### Deck outline (slide-by-slide)
+
+1. Slide 1 — Strongest point (headline + proof)
+2. Problem (who hurts, how much)
+3. Why now (timing shift)
+4. Solution (what you do, how it works)
+5. Product demo / how it’s used
+6. Traction / proof (or proxies)
+7. GTM (how you reach customers)
+8. Market (size + wedge expansion)
+9. Competition / differentiation
+10. Team (why you)
+11. Financials / unit economics (early-stage friendly)
+12. The ask (round design + milestone)
+
+## 4) Investor Target List + Pipeline Tracker (template)
+
+### Investor ICP (fit filters)
+
+- Stage:
+- Check size:
+- Thesis keywords:
+- Geography:
+- Red flags / avoid list:
+
+### Target list (table)
+
+| Investor | Fund/type | Fit reason | Warm path | Status | Next action | Date |
+| -------- | --------- | ---------- | --------- | ------ | ----------- | ---- |
+|          |           |            |           |        |             |      |
+
+### Pipeline stages + weekly targets
+
+- Stages: intro requested → intro sent → meeting booked → meeting done → 2nd meeting → partner meeting → diligence → term sheet
+- Weekly targets (starting point): new intros requested, meetings completed, follow-ups sent
+
+## 5) Outreach + Follow-up Scripts (templates)
+
+### Warm intro ask (to a connector)
+
+Subject: Intro to [Investor] for [Company]?
+
+Hi [Name] — quick ask. We’re building **[one-liner]** and are raising a **[round]** to reach **[milestone]**.  
+Would you be open to intro’ing us to **[Investor]**? If yes, here’s a short blurb you can forward:
+
+Forwardable blurb:
+
+> [Founder] is building [one-liner]. Proof: [1 metric/proxy]. They’re raising [amount range] to reach [milestone] by [date]. Would love 20 minutes.
+
+### Cold email (if needed)
+
+Subject: [Outcome] for [ICP] — raising [round]
+
+Hi [Investor] — I’m [Name], cofounder of [Company]. We help **[ICP]** achieve **[outcome]**.  
+In the last [time period], we’ve seen **[proof]**. We’re raising a **[round]** to reach **[milestone]**.
+
+Are you open to a 20-minute intro call next week?
+
+### Post-meeting follow-up (within 24h)
+
+Subject: Thanks — [Company] recap + next steps
+
+Thanks for the time today. Quick recap:
+
+- What we do: [one-liner]
+- Proof: [metric/proxy]
+- Raise: [amount range] to reach [milestone] by [date]
+
+Next step: [CTA — partner meeting / deeper dive / send deck + metrics].  
+Attached/linked: [deck/doc/demo].
+
+## 6) Diligence checklist + FAQ (template)
+
+### Lightweight data room index (early-stage)
+
+- Company overview (deck + memo)
+- Product (demo video or link; roadmap)
+- Traction (metrics snapshot; cohort/retention if available)
+- Customer evidence (quotes, case studies, pilots)
+- Financials (simple model; burn + runway; pricing)
+- Team (bios; hiring plan)
+- Legal (incorporation basics; IP assignment status) — _questions for counsel_
+
+### FAQ / objection responses
+
+| Objection          | Best response (evidence-first) | Follow-up artifact |
+| ------------------ | ------------------------------ | ------------------ |
+| “Too early”        |                                |                    |
+| “Market too small” |                                |                    |
+| “GTM unclear”      |                                |                    |
+| “Competition”      |                                |                    |
+
+## 7) Weekly fundraising dashboard (template)
+
+### Activity (this week)
+
+- New intros requested:
+- Intros sent:
+- Meetings completed:
+- Follow-ups sent:
+- Second meetings:
+
+### Funnel notes
+
+- Wins:
+- Losses (“no” reasons):
+- Pitch iterations to make:
+
+### Next 7 days
+
+- [ ] Outreach block #1:
+- [ ] Outreach block #2:
+- [ ] Meeting prep:
+- [ ] Update tracker:

package/vendor/skills/skills/fundraising/references/WORKFLOW.md

@@ -0,0 +1,84 @@
+# Fundraising — Expanded Workflow Notes
+
+This file expands the steps in `../SKILL.md` with practical heuristics. Treat all external fundraising advice as context; always adapt to the user’s constraints.
+
+## A) The “venture treadmill” decision (raise vs don’t)
+
+Use the Raise Decision Memo to make the trade-offs explicit:
+
+- **Raising VC buys speed** (and time) but creates expectations: growth, outcomes, and a future financing path.
+- **Not raising** can preserve optionality (control, pace), but may constrain speed or hiring.
+
+Common decision criteria:
+
+- Can the business reach meaningful milestones without VC? (revenue path, distribution path, founder runway)
+- Is the market “winner-take-most” or timing-sensitive enough to justify VC speed?
+- Does the team have a credible plan to use capital efficiently (specific milestone + hires)?
+
+## B) Round design without pretending to be counsel
+
+Focus on fundable clarity, not legal correctness:
+
+- **Amount range:** “minimum viable raise” (keeps you alive) vs “plan A raise” (buys milestone) vs “maximal” (tempting, but riskier).
+- **Milestone framing:** what must be true by the end of the runway to make the next round (or profitability) plausible.
+- **Use of funds story:** headcount + key bets + buffers, tied to the milestone.
+
+Avoid giving legal advice; instead:
+
+- List **questions for counsel** (instrument, jurisdiction, investor rights).
+- Keep numbers as ranges unless the user provides exact figures.
+
+## C) Pitch narrative: first slide + first impression
+
+The pitch “job” is to earn the next meeting. Build assets in this order:
+
+1. **One-liner** (what, for whom, outcome)
+2. **Slide 1** (strongest point)
+3. **Narrative arc** (why now → why you → why win)
+4. **Proof** (traction, customer quotes, demo, benchmarks, credible proxies)
+
+Slide 1 heuristics (must pass in ~10 seconds):
+
+- A specific category: “AI workflow automation for X”
+- A clear ICP: “for Y teams at Z-sized companies”
+- A concrete outcome: “reduces A by B%” (or proxy)
+
+## D) Pipeline math + “100 no’s”
+
+Treat fundraising like a sales funnel:
+
+- Define a weekly outreach target (e.g., 10–20 new contacts/week) based on time budget.
+- Track outcomes: intro requested, intro sent, meeting booked, meeting done, second meeting, partner meeting, diligence, term sheet.
+
+When the user hears lots of “no”:
+
+- Log the stated reason and categorize it (timing, market, traction, team, thesis mismatch).
+- Look for **repeatable patterns** and adjust (target list, story, proof, pricing, wedge).
+
+## E) Meeting + follow-up system
+
+Standardize the meeting:
+
+- Open: what you do + hook
+- Problem: why it’s painful + why now
+- Solution: wedge + demo
+- Proof: traction/proxies
+- Ask: round design (how much, by when, what milestone)
+- Close: next step + timeline
+
+Follow-up within 24 hours:
+
+- Short recap
+- Any promised artifacts (deck, metrics, memo)
+- Clear CTA (next meeting, partner intro, diligence request)
+
+## F) Diligence prep (lightweight data room)
+
+You don’t need a perfect data room early, but you do need:
+
+- Clean story that matches the numbers
+- Basic financial model (even simple)
+- Customer evidence (quotes, case studies, pilots)
+- Product demo/roadmap clarity
+
+Use the data-room checklist in [TEMPLATES.md](TEMPLATES.md) to avoid missing obvious asks.

package/vendor/skills/skills/fundraising/skillpack.json

@@ -0,0 +1,13 @@
+{
+    "authors": ["liqiongyu"],
+    "category": "Career",
+    "contributors": [],
+    "origin": "refound",
+    "schema_version": 1,
+    "skill_slug": "fundraising",
+    "upstream": {
+        "page_url": "https://refoundai.com/lenny-skills/s/fundraising",
+        "skill_md_url": "https://refoundai.com/skills/fundraising/SKILL.md"
+    },
+    "version": "0.1.0"
+}

package/vendor/skills/skills/game-changing-features/README.md

@@ -0,0 +1,230 @@
+# Game-Changing Features
+
+A strategic product thinking skill that helps identify 10x opportunities and high-leverage improvements for your product.
+
+## Purpose
+
+This skill shifts your mindset from incremental improvements to transformative thinking. Instead of asking "what feature should we add next?", it asks "what would make this 10x more valuable?" It's designed for founders, product managers, and teams who want to find the moves that make users unable to live without their product.
+
+## When to Use
+
+Activate this skill when you need:
+
+- Strategic product thinking and prioritization
+- To identify high-impact features that differentiate from competitors
+- To find quick wins with outsized impact
+- To explore what would make your product 10x better
+- Product strategy discussions about "what should we build next?"
+- To validate if you're working on the right things
+
+Trigger phrases include:
+
+- "What would make this 10x better?"
+- "Product strategy"
+- "What should we build next?"
+- "10x opportunities"
+- "Game-changing features"
+- "High-leverage improvements"
+
+## How It Works
+
+### The Approach
+
+This skill follows a structured 5-step workflow:
+
+1. **Understand Current Value** - Deep dive into what the product does today, who uses it, and why
+2. **Find 10x Opportunities** - Think across three scales (Massive, Medium, Small)
+3. **Evaluate Ruthlessly** - Score ideas on impact, reach, frequency, differentiation, defensibility, and feasibility
+4. **Identify Highest-Leverage Moves** - Find quick wins, strategic bets, and compounding features
+5. **Prioritize** - Stack rank into Do Now, Do Next, Explore, and Backlog
+
+### Three Scales of Thinking
+
+**Massive (High effort, transformative)**
+
+- Features that fundamentally expand what the product can do
+- Opens new markets, use cases, or capabilities
+- Makes competitors nervous
+
+**Medium (Moderate effort, high leverage)**
+
+- Significantly enhances the core experience
+- Force multipliers on what already works
+- Turns casual users into power users
+
+**Small Gems (Low effort, disproportionate value)**
+
+- Tiny changes that punch way above their weight
+- Often overlooked because they seem "too simple"
+- Single buttons/shortcuts that save minutes daily
+
+### Evaluation Framework
+
+Each idea is assessed across 6 criteria:
+
+| Criteria        | Question                                            |
+| --------------- | --------------------------------------------------- |
+| Impact          | How much more valuable does this make the product?  |
+| Reach           | What % of users would this affect?                  |
+| Frequency       | How often would users encounter this value?         |
+| Differentiation | Does this set us apart or just match competitors?   |
+| Defensibility   | Is this easy to copy or does it compound over time? |
+| Feasibility     | Can we actually build this?                         |
+
+Scoring:
+
+- 🔥 **Must do** - High impact, clearly worth it
+- 👍 **Strong** - Good impact, should prioritize
+- 🤔 **Maybe** - Interesting but needs more thought
+- ❌ **Pass** - Not worth it right now
+
+## Key Features
+
+### Systematic Exploration
+
+Forces you through 10 idea categories to ensure comprehensive coverage:
+
+- Speed - What takes too long?
+- Automation - What's repetitive?
+- Intelligence - What could be smarter?
+- Integration - What else do users use?
+- Collaboration - How do users work together?
+- Personalization - How is everyone different?
+- Visibility - What's hidden that shouldn't be?
+- Confidence - What creates anxiety?
+- Delight - What could spark joy?
+- Access - Who can't use this yet?
+
+### Documentation-First
+
+All session outputs are saved to `.claude/docs/ai/<product-or-area>/10x/session-N.md`. This ensures:
+
+- Full traceability of strategic thinking
+- Easy sharing with team members
+- Historical record of decisions
+- No chat clutter - pure strategy focus
+
+### Pure Strategy Mode
+
+This skill is **code-free**. No implementation, no prototypes - just strategic thinking. Implementation comes later, after you've identified the right moves.
+
+## Usage Examples
+
+### Example 1: SaaS Dashboard Product
+
+```
+User: I want to think about 10x opportunities for our analytics dashboard
+
+[Skill activates and guides through:]
+1. Understanding current dashboard capabilities
+2. Exploring opportunities like:
+   - Massive: AI-powered anomaly detection that auto-investigates issues
+   - Medium: Collaborative annotations and shared insights
+   - Small: One-click report scheduling from any view
+3. Prioritizing quick wins vs strategic bets
+4. Output saved to `.claude/docs/ai/analytics-dashboard/10x/session-1.md`
+```
+
+### Example 2: Mobile App
+
+```
+User: What would make our fitness app 10x better?
+
+[Skill explores:]
+- Speed: Instant workout logging with voice
+- Automation: Smart rest day recommendations
+- Intelligence: Predictive injury prevention
+- Collaboration: Virtual workout buddies
+- Delight: Achievement celebrations that don't feel gamified
+
+[Result: Prioritized list of 15 opportunities with clear next steps]
+```
+
+### Example 3: Developer Tool
+
+```
+User: Product strategy session for our API testing tool
+
+[Skill identifies:]
+- Do Now: Auto-generate test cases from API docs (2 weeks, huge value)
+- Do Next: Team collaboration with shared test suites (1 month, unlocks enterprise)
+- Explore: AI that writes tests by watching you use the API (3 months, could be transformative)
+
+[Output: Full strategic document with rationale and risk assessment]
+```
+
+## What You Get
+
+After a session, you'll have:
+
+- **Current Value Assessment** - Clear understanding of your product's core value proposition
+- **Categorized Opportunities** - Ideas organized by scale (Massive/Medium/Small)
+- **Scored Ideas** - Each opportunity evaluated on 6 criteria with clear scoring
+- **Prioritized Roadmap** - Stack-ranked into Do Now / Do Next / Explore / Backlog
+- **Evidence-Based Reasoning** - Ideas grounded in codebase research and user behavior
+- **Unblocked Questions** - Clear list of assumptions to validate and decisions to make
+
+## Core Principles
+
+1. **Think Big First** - Don't self-censor with "that's too hard"
+2. **Small Can Be Huge** - Don't dismiss simple ideas; sometimes one button changes everything
+3. **User Value > Feature Count** - 10 features adding 1% each ≠ 1 feature adding 10x
+4. **Be Specific** - "Better UX" is not an idea; "One-click rescheduling from notification" is
+5. **Question Assumptions** - "Users want X" may be wrong
+6. **Compound Thinking** - Prefer features that get better over time
+7. **No Safe Ideas** - If every idea is "obviously good," you're not thinking hard enough
+8. **Cite Evidence** - Reference what you saw in codebase or research
+
+## Tips for Best Results
+
+### Before Starting
+
+Provide context on:
+
+- Product/Area you're thinking about
+- Current state (brief description)
+- Constraints (technical limits, timeline, team size)
+
+### During the Session
+
+- Be open to uncomfortable ideas
+- Push back on assumptions
+- Ask "what would make users tell their friends?"
+- Consider both 10x team size and 1/10th team size scenarios
+
+### After the Session
+
+- Validate key assumptions with users
+- Share the strategic document with your team
+- Pick 1-2 quick wins to test first
+- Revisit and update as you learn
+
+## Output Location
+
+All sessions are saved to:
+
+```
+.claude/docs/ai/<product-or-area>/10x/session-N.md
+```
+
+This keeps your strategic thinking organized, searchable, and shareable with your team.
+
+## Not Included
+
+This skill does NOT:
+
+- Write code or implementation plans (use after strategy is clear)
+- Make final decisions (provides recommendations, you decide)
+- Replace user research (complements it with strategic analysis)
+- Guarantee success (identifies high-potential opportunities to test)
+
+## Related Skills
+
+- `feature-planning` - For breaking down chosen features into implementation plans
+- `implementation-blueprint` - For architecting how to build selected opportunities
+- `dev-spec` - For creating detailed specs after strategy is set
+- `critical-brainstorm` - For stress-testing specific ideas before committing
+
+---
+
+**Remember**: This skill is about finding the moves that matter. Not every idea will work, but the goal is to identify the ones worth testing that could fundamentally change your product's trajectory.