Tech for Non-Technical Founders 2026: Sprint 2 closes Modules 1 + 2 (the 'decide what to build' arc)#340
Conversation
… course infra Sprint 1 deliverables (3 chapters of the 26-post course): - Module 0.1 - Where Are You? + Self-Assessment Worksheet artifact - Module 1.1 - Find 10 People with the Problem (2026 outreach stack) + Outreach Sequence Template - Module 1.2 - The Mom Test + Mom Test Interview Script Course infrastructure: - Stub landing page at /blog/tech-for-non-technical-founders-2026/ (build-in-public mode) - 8 artifacts moved from docs/.../lead-magnets/ to public Hugo URLs at /blog/<slug>/ - Strategy + execution scaffolding under docs/projects/2605-tech-for-non-technical-founders/ Team-mode pipeline that ran: - Writer (general-purpose agent) -> mechanical gates -> voice critic + cold-eyes verifier (parallel where independent) -> editor revisions where needed -> ship - WIP=1 sequential discipline maintained across all 3 Sprint 1 chunks Doctrine in scope (memory feedbacks): - Pure lead magnet (zero JT service CTAs; authorship credit only) - Viral shareability (contrarian hook + tweetable insight + weekly tactic + artifact) - KISS - simplest method on main path; frameworks in Advanced sidebars only - Course-as-journey (input/output/checkpoint/artifact per module) - No length caps; cut test per section - >=3 handmade infographics per post (Mermaid + sketchy SVG mix) - Rails / Django / Laravel default tech stack; no React/Node/Java as lead Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…page module-first framing
S2.1 deliverable:
- /blog/validated-problem-statement-decide-whats-next/ (Module 1.3 post)
- /blog/validated-problem-statement-template/ (companion artifact, public URL)
- 2 inline SVGs + 1 Mermaid diagram
Hook archetype rotated to Reddit-poster (per hook-bank diversity rule applied after S1.3 cold-eyes review flagged "founder we picked up" pattern saturation). 0 em-dashes, 0 banned words, 0 JT service CTAs.
Landing page restructured per user directive (2026-07-22):
- Removed public post-count framing ("X of 26 posts") - too granular for ICP
- Module table now shows status (Complete / Partial / Coming) + approx reading time per module
- ICP cares about modules + time, not chapter-by-chapter granularity
Module 1 is now complete (3 of 3 chapters live: outreach + Mom Test + validated problem statement).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…Module 2 complete)
Sprint 2 deliverables (3 chapters):
- Module 1.3 "Write Down What You Heard, Decide What's Next" + Validated Problem Statement Template artifact
- Module 2.2 "The One-Page Product Brief (Vibe PRD)" + Vibe PRD Template artifact
- Module 2.3 "Stop Specifying Features. Start Specifying Outcomes." (no artifact - inline tactic, KISS doctrine: job-story framework name stays in citations only)
After Sprint 2:
- Module 1 (Validate the Problem) is COMPLETE - 3 of 3 chapters live
- Module 2 (Design the Solution) is COMPLETE - 3 of 3 chapters live
- Reader can now go idea -> validated problem -> Product Brief without external resources
Hook-bank diversity enforced per S1.3 cold-eyes flag:
- S2.1 Reddit-poster archetype
- S2.2 News-pegged ($1,000 Maven cohort vs free)
- S2.3 Direct address ("You asked for a simple admin panel. You got a spaceship.")
- Zero "founder we picked up" leads in Sprint 2
Landing page updated per ICP feedback (2026-07-22):
- Module-first framing (no post counts to readers)
- Reading time per module + status (Complete/Partial/Coming)
All gates clean: 0 em-dashes, 0 banned words, 0 JT service CTAs across all 3 new posts + 2 new artifacts.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…r S2.3 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (17)
📒 Files selected for processing (41)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced May 13, 2026
Closed
Member
Author
|
Consolidated into #345 — single PR for the full Tech for Non-Technical Founders 2026 course (9 modules, 30 chapters, 12 artifacts, 118 files). Per the user's directive to ship the course as one reviewable diff instead of a 7-PR chain. The commits from this branch are linearly preserved on the consolidated branch |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
What's new in this PR
/blog/validated-problem-statement-decide-whats-next//blog/one-page-product-brief-vibe-prd//blog/stop-specifying-features-start-outcomes/Plus 2 new template artifacts at public URLs:
/blog/validated-problem-statement-template//blog/vibe-prd-template/Plus landing page updates: Modules 1 and 2 status flipped from Partial/Coming to Complete; module-first framing reinforced.
Doctrine compliance
Test plan
bin/hugo-buildsucceeds with master + sprint-2bin/test+bin/dtestgreen🤖 Generated with Claude Code