docs(course): add ICP journey SIPOC, operational dependency map, voice/placeholder standardization#368
Conversation
|
Warning Review limit reached
Next review available in: 11 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (17)
📝 WalkthroughWalkthroughThe PR adds course journey and dependency architecture documents, centralizes Junie skills through symbolic links, records skill metadata, and standardizes bracketed placeholders across course lessons and reference templates. ChangesRepository support
Course system
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
…tream sources, HOW to obtain every input, original-inputs principle
…or all 2.6 prototype blanks
…okf/validate/visualize + 37signals-rails, copywriting, blog, git-commit, hugo, social-media-trends-research)
…se UPPERCASE for [CUSTOMER] to match sibling blanks
…F architecture bundle
… Google/GitHub best practice (SCREAMING_SNAKE_CASE)
…REAMING_SNAKE_CASE) per Google/GitHub best practice
a6c631a to
b8f9c56
Compare
There was a problem hiding this comment.
Actionable comments posted: 20
🧹 Nitpick comments (2)
content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md (1)
35-35: 📐 Maintainability & Code Quality | 🔵 TrivialRun the required content-page validation gates before committing.
Run visual regression and Chrome DevTools validation for the changed Markdown pages, then investigate any console errors or 404s before merge.
content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md: validate the updated lesson rendering and links.content/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.md: validate the worksheet rendering.content/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.md: validate the prompt block and links.content/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.md: validate prompt formatting and message rendering.content/course/tech-for-non-technical-founders-2026/reference/channel-selection-full/index.md: validate the reference page.content/course/tech-for-non-technical-founders-2026/reference/find-10-people-full/index.md: validate inline code and quote rendering.content/course/tech-for-non-technical-founders-2026/reference/hypothesis-sprint-full/index.md: validate prompt code blocks.content/course/tech-for-non-technical-founders-2026/reference/mom-test-full/index.md: validate the Mermaid/content rendering.content/course/tech-for-non-technical-founders-2026/reference/must-have-survey-full/index.md: validate the email blockquote formatting.content/course/tech-for-non-technical-founders-2026/reference/mvp-build-phases-full/index.md: validate the outreach quote rendering.content/course/tech-for-non-technical-founders-2026/reference/outbound-full/index.md: validate the diagnostic section and links.As per coding guidelines, “For HTML, CSS, JavaScript, template, and content-page changes, run the required visual regression and Chrome DevTools validation gates before committing; investigate zero-console-error and zero-404 failures.”
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md` at line 35, Run the required visual regression and Chrome DevTools validation for all affected content pages: content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md:35-35, build-path-decision-worksheet/index.md:164-164, channel-selection-before-outbound/index.md:67-67, clickable-prototype-validation-2-hour-lovable/index.md:78-78, reference/channel-selection-full/index.md:68-68, reference/find-10-people-full/index.md:22-22, reference/hypothesis-sprint-full/index.md:66-66, reference/mom-test-full/index.md:19-19, reference/must-have-survey-full/index.md:32-38, reference/mvp-build-phases-full/index.md:70-70, and reference/outbound-full/index.md:154-154. Verify each page’s specified rendering, links, prompts, or formatting, and investigate and resolve any console errors or 404s before committing.Source: Coding guidelines
content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md (1)
167-177: 📐 Maintainability & Code Quality | 🔵 TrivialRun the required content-page validation gates before merge.
As per coding guidelines, content-page changes require visual regression and Chrome DevTools validation, including zero-console-error and zero-404 checks.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md` around lines 167 - 177, Run the required content-page validation gates for the updated churn-triage page before merging: complete visual regression testing and Chrome DevTools validation, confirming zero console errors and zero 404 responses.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@content/course/tech-for-non-technical-founders-2026/fake-stripe-pre-sale-pieter-levels/index.md`:
- Around line 60-63: The FTC compliance guidance in the pre-sale refund section
overstates the sufficiency of the landing-page and thank-you-page disclosure.
Update the text around the “FTC compliance” bullet to state that sellers must
ship within the required timeframe or provide timely written delay notice,
obtain buyer consent, and offer cancellation/refund options; do not claim the
existing blanket disclosure alone covers compliance.
In
`@content/course/tech-for-non-technical-founders-2026/friday-demo-template/index.md`:
- Line 114: Add the [DATE] and [ONE_LINE_SUMMARY] placeholders to the dependency
map in 30.06-operational-dependency-map.md, documenting the upstream source for
each while preserving the existing Friday demo template references.
In
`@content/course/tech-for-non-technical-founders-2026/how-this-course-works/index.md`:
- Around line 122-123: Remove the blank line within the blockquote containing
“Mia's Module 4” in the course overview, or replace it with a `>` marker so the
blockquote remains continuous and satisfies Markdownlint MD028.
In
`@content/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.md`:
- Line 106: Update the inner prompt occurrences of the lowercase [channel]
placeholder near the referenced ad-writing instructions to use the same
uppercase [CHANNEL] token described in the surrounding guidance. Ensure both
occurrences share the single consistent placeholder contract.
In
`@content/course/tech-for-non-technical-founders-2026/reference/stripe-price-test-full/index.md`:
- Line 120: Update the failure-response placeholder in the prompt text to use
uppercase “[ITEM]”, changing “NOT FOUND - [item]” to “NOT FOUND - [ITEM]” while
preserving the surrounding instructions.
In
`@content/course/tech-for-non-technical-founders-2026/slopsquatting-ai-supply-chain-attack/index.md`:
- Line 85: Update the defense description around the dependency gate to match
the implemented workflow: remove the undocumented `dep-approved` label and
`[SKIP_DEP_GATE]` commit-message override claims, unless the workflow is also
changed to implement a trusted, auditable override. Preserve the documented
behavior that changed lockfiles are checked and new dependencies block the PR by
default.
In
`@content/course/tech-for-non-technical-founders-2026/where-to-hire-developer-2026-map/index.md`:
- Line 161: Standardize the placeholders in the changed hiring templates:
replace “[specific reason about your scope]” with “[SCOPE_REASON]” and replace
“[date + 5 days]” with “[FIRST_SLATE_DATE]” or equivalent plain instructional
text. Preserve the surrounding template wording.
In
`@docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.05-icp-journey-sipoc.md`:
- Around line 1-5: Move both new documents, 30.05-icp-journey-sipoc.md and
30.06-operational-dependency-map.md, under docs/workflows/, or obtain an
explicit repository-rule exception before keeping them in their current
location.
- Around line 153-154: Update the Mermaid flow around M5_FixProduct to add an
edge from M5_FixProduct to M4_4, ensuring the PMF failure recovery path
re-enters the build phases as indicated by the node label.
- Around line 50-54: Update the M1_4Gate conversion-rate branches so the Iterate
condition covers 3% through values below 6% (for example, 3%–<6%), while the
Promising branch remains ≥6%; ensure the labels are mutually exclusive.
- Line 9: Normalize the schedule basis throughout the document, including the
headline total, M2 schedule label, and later timeline total. Choose either
evenings-and-weekends or full-time as the sole basis, then update all stated
durations so the phase totals and overall total agree consistently.
- Around line 88-91: Update the M2.6 flow around M2_6 and M2_Out in
docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.05-icp-journey-sipoc.md:
replace the gate-only label with an explicit decision node and add a
failure/rework edge back to the prototype or observation step while preserving
the passing path to M2_Out. Then refresh the corresponding summary in
.okf/architecture/icp-journey-sipoc.md so it accurately reflects the decision
and recovery path.
- Around line 134-141: The optional M4.5 detour must be reachable only after
successful M4.4 completion: update the M4_4Gate flow so its optional edge
originates from the Yes path or an equivalent success node, never from the
unresolved gate. Also update the M5 completion flow at
docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.05-icp-journey-sipoc.md
lines 169-176 so M5 can reach completion only after the paid-deposit condition
succeeds; preserve failure paths without allowing them to bypass the mandatory
gates.
In
`@docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.06-operational-dependency-map.md`:
- Around line 306-310: Update the Domain ownership check in the operational
dependency map to use registrar ownership evidence rather than requiring Sam’s
name in public WHOIS. Verify the registrar account, registrant email, billing
record, and transfer lock, while retaining the existing transfer-to-Porkbun
action for domains held by the page builder.
- Around line 499-579: Label the fenced dependency-chain block containing the
rough-idea-to-paid-pilot map with an appropriate language identifier, preferably
text, so the Markdown fence satisfies MD040 while preserving its diagram
content.
- Around line 386-388: Update the “4.4 onramp waitlist” dependency description
to avoid hard-coding Mixo’s “Subscribers” tab; reference the selected builder
and export method established in the 1.2/1.4 waitlist flow, or use a generic
waitlist export artifact that works for either builder.
- Around line 90-95: Update the ad-account setup entry in
docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.06-operational-dependency-map.md
at lines 90-95 to list exact signup URLs for Meta, Google, LinkedIn, and Reddit,
along with the credential and payment-method requirements. In
.okf/architecture/operational-dependency-map.md at lines 30-33, retain the
exact-URL coverage claim only after the canonical map includes these details.
- Around line 397-399: Update the PMF gate and “Plan B” guidance around the 40%
threshold so every result below 40% has an explicit next step; either broaden
Plan B to cover all <40% outcomes or add a distinct path for the 25–39% range,
while preserving the existing ≥40% success path.
- Around line 474-481: The deposit guidance in
docs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.06-operational-dependency-map.md:474-481
must use one rule consistent with the cleared $500+ completion gate: remove or
revise the sub-$500 first-month fallback and ensure the detailed deposit math
requires at least $500. Update the corresponding summary in
.okf/architecture/operational-dependency-map.md:48-50 to mirror the resolved
$500+ deposit rule.
- Around line 4-5: Update the purpose description in the document metadata to
list the browser alongside the rough idea and Gmail address as Sam’s original
inputs, keeping the rest of the dependency-map description unchanged.
---
Nitpick comments:
In
`@content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md`:
- Line 35: Run the required visual regression and Chrome DevTools validation for
all affected content pages:
content/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.md:35-35,
build-path-decision-worksheet/index.md:164-164,
channel-selection-before-outbound/index.md:67-67,
clickable-prototype-validation-2-hour-lovable/index.md:78-78,
reference/channel-selection-full/index.md:68-68,
reference/find-10-people-full/index.md:22-22,
reference/hypothesis-sprint-full/index.md:66-66,
reference/mom-test-full/index.md:19-19,
reference/must-have-survey-full/index.md:32-38,
reference/mvp-build-phases-full/index.md:70-70, and
reference/outbound-full/index.md:154-154. Verify each page’s specified
rendering, links, prompts, or formatting, and investigate and resolve any
console errors or 404s before committing.
In
`@content/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.md`:
- Around line 167-177: Run the required content-page validation gates for the
updated churn-triage page before merging: complete visual regression testing and
Chrome DevTools validation, confirming zero console errors and zero 404
responses.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 66512b5c-2590-4a46-88f4-00a244e00523
📒 Files selected for processing (62)
.junie/skills/37signals-rails.junie/skills/blog.junie/skills/copywriting.junie/skills/git-commit.junie/skills/hugo.junie/skills/okf.junie/skills/social-media-trends-research.junie/skills/validate.junie/skills/visualize.okf/architecture/icp-journey-sipoc.md.okf/architecture/index.md.okf/architecture/operational-dependency-map.md.okf/log.mdcontent/course/tech-for-non-technical-founders-2026/ai-persona-pre-validation-mom-test-prep/index.mdcontent/course/tech-for-non-technical-founders-2026/build-path-decision-worksheet/index.mdcontent/course/tech-for-non-technical-founders-2026/channel-selection-before-outbound/index.mdcontent/course/tech-for-non-technical-founders-2026/clickable-prototype-validation-2-hour-lovable/index.mdcontent/course/tech-for-non-technical-founders-2026/customers-leaving-churn-triage-not-acquisition/index.mdcontent/course/tech-for-non-technical-founders-2026/fake-stripe-pre-sale-pieter-levels/index.mdcontent/course/tech-for-non-technical-founders-2026/faq/index.mdcontent/course/tech-for-non-technical-founders-2026/find-10-people-where-to-look/index.mdcontent/course/tech-for-non-technical-founders-2026/find-10-people-with-problem-outreach-2026/index.mdcontent/course/tech-for-non-technical-founders-2026/first-paying-customer-operating-kit/index.mdcontent/course/tech-for-non-technical-founders-2026/first-ten-customers-outreach-message/index.mdcontent/course/tech-for-non-technical-founders-2026/form-your-founding-hypothesis-90-minute-sprint/index.mdcontent/course/tech-for-non-technical-founders-2026/friday-demo-template/index.mdcontent/course/tech-for-non-technical-founders-2026/hire-track-supplementary-reference/index.mdcontent/course/tech-for-non-technical-founders-2026/hiring-interview-script/index.mdcontent/course/tech-for-non-technical-founders-2026/how-this-course-works/index.mdcontent/course/tech-for-non-technical-founders-2026/module-1-walkthrough-mia/index.mdcontent/course/tech-for-non-technical-founders-2026/mom-test-ask-about-past-not-future/index.mdcontent/course/tech-for-non-technical-founders-2026/mom-test-interview-script/index.mdcontent/course/tech-for-non-technical-founders-2026/mom-test-synthesis-build-pivot-kill/index.mdcontent/course/tech-for-non-technical-founders-2026/must-have-segment-pmf-test/index.mdcontent/course/tech-for-non-technical-founders-2026/one-page-product-brief-vibe-prd/index.mdcontent/course/tech-for-non-technical-founders-2026/outreach-sequence-template/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/ceiling-signals-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/channel-selection-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/find-10-people-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/hypothesis-sprint-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/mom-test-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/must-have-survey-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/mvp-build-phases-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/outbound-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/paid-pilot-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/persona-rehearsal-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/prototype-build-full/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/smoke-test-channel-guide/index.mdcontent/course/tech-for-non-technical-founders-2026/reference/stripe-price-test-full/index.mdcontent/course/tech-for-non-technical-founders-2026/self-serve-mvp-stack-build-phases/index.mdcontent/course/tech-for-non-technical-founders-2026/self-serve-stack-walkthrough/index.mdcontent/course/tech-for-non-technical-founders-2026/slopsquatting-ai-supply-chain-attack/index.mdcontent/course/tech-for-non-technical-founders-2026/smoke-test-build-page/index.mdcontent/course/tech-for-non-technical-founders-2026/smoke-test-landing-page-7-day-demand-test/index.mdcontent/course/tech-for-non-technical-founders-2026/sow-reading-guide/index.mdcontent/course/tech-for-non-technical-founders-2026/stop-specifying-features-start-outcomes/index.mdcontent/course/tech-for-non-technical-founders-2026/validation-tools-field-guide/index.mdcontent/course/tech-for-non-technical-founders-2026/where-to-hire-developer-2026-map/index.mddocs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.05-icp-journey-sipoc.mddocs/projects/2605-tech-for-non-technical-founders/30-39-architecture-design/30.06-operational-dependency-map.mddocs/projects/2605-tech-for-non-technical-founders/PROJECT-INDEX.mdskills-lock.json
…dd mcpServers to package.json
…gate, optional detour routing, M5 recovery edge
…lan B tiers, deposit rule clarity
…SE in where-to-hire-dev-map
…Friday Demo follow-up email
…el, WHOIS→registrar, MD040 code fence
Summary by CodeRabbit
Documentation
Improvements