docs(MAX-566): add /ship course outline assets

README.md

@@ -23,6 +23,11 @@ A 9-agent GTM team boots on first run. The coordinator reads your Linear tickets
 
 **The pipeline:** idea → validate → strategy → awareness → lead-capture → nurture → closing → launch → measure
 
+**Aprendé el pipeline completo → curso /ship ($497)**
+
+- Course outline: [`docs/course-outline.md`](docs/course-outline.md)
+- Free sample workbook: [`docs/course-lessons/module-1-lesson-1-workbook.md`](docs/course-lessons/module-1-lesson-1-workbook.md)
+
 **Every deploy is credential-gated.** `check_local.py` covers 30+ integrations. Missing token = blocked run, not a mid-sprint surprise.
 
 ---

docs/course-lessons/module-1-lesson-1-workbook.md

@@ -0,0 +1,119 @@
+# /ship free sample lesson workbook
+
+**Course:** /ship — From idea to shipped product in 2 weeks with AI agents  
+**Module 1, Lesson 1:** Run your idea through `/ship` intake
+
+## Lesson goal
+
+Turn a vague product idea into a one-page launch brief the `/ship` pipeline can execute.
+
+## By the end of this lesson you should have
+
+- A clear problem statement
+- A specific ICP
+- A concrete promised outcome
+- A realistic 2-week launch scope
+- A first-pass success metric
+
+## Part 1 — The product in one sentence
+
+Complete this sentence:
+
+> We help **[specific user]** achieve **[specific outcome]** without **[main friction]**.
+
+## Part 2 — Intake prompts
+
+Answer these in plain language.
+
+### 1) What are you shipping?
+- Product name:
+- Product type:
+- Link or repo:
+- Current stage: idea / prototype / beta / live
+
+### 2) Who is it for?
+- Primary audience:
+- What can they already do well?
+- What do they get stuck on?
+- Why is this painful now?
+
+### 3) What result are you promising?
+- Desired outcome:
+- Timeframe:
+- What becomes easier, faster, or cheaper?
+- What evidence would make this believable?
+
+### 4) What constraints matter?
+- Time available before launch:
+- Team size:
+- Budget:
+- Channels you can actually use:
+- Hard constraints or dependencies:
+
+### 5) What does success look like in 2 weeks?
+- Validation target:
+- Traffic / lead target:
+- Revenue or conversion target:
+- Minimum outcome that still counts as a win:
+
+## Part 3 — Red-flag check
+
+If you answer “no” to any of these, tighten the brief before moving on.
+
+- Do I know exactly who this is for?
+- Can I explain the pain in one sentence?
+- Is the promised outcome concrete?
+- Can this realistically ship in 2 weeks?
+- Do I know what metric I am trying to move first?
+
+## Part 4 — One-page launch brief template
+
+```md
+# /ship launch brief
+
+## Product
+- Name:
+- Type:
+- Current stage:
+
+## ICP
+- Primary audience:
+- Pain:
+- Current alternative:
+
+## Outcome promise
+- We help [audience] get [result] in [timeframe] without [friction].
+
+## Scope
+- What is in this 2-week launch:
+- What is explicitly out:
+
+## Channels
+- Primary:
+- Secondary:
+
+## Proof
+- Existing proof:
+- Missing proof we need before launch:
+
+## Success metric
+- Main KPI:
+- Minimum win threshold:
+```
+
+## Part 5 — Apply now
+
+1. Fill out the brief template.
+2. Delete anything vague.
+3. Highlight the one sentence that best explains the offer.
+4. Share the brief with one real person and ask, “Would you understand what this is and why it matters?”
+
+## Reflection
+
+- What part of the brief was hardest to answer?
+- Where did your idea feel too broad?
+- What would make this easier to launch inside 2 weeks?
+
+## Next lesson bridge
+
+Once the intake is clean, the next step is validation. In Module 2, you will test whether the market actually cares before building more assets.

docs/course-outline.md

@@ -0,0 +1,209 @@
+# /ship course outline
+
+**Course:** /ship — From idea to shipped product in 2 weeks with AI agents  
+**Price:** $497  
+**Offer stack:** FREE `/ship` OSS tool → paid implementation course  
+**Delivery format:** mixed (video lessons + text workbooks + cloneable repo templates)
+
+## ICP
+
+Solo founders, indie hackers, and small teams who can code but stall at go-to-market. Built for LATAM and English-speaking operators who want an opinionated end-to-end launch pipeline instead of disconnected prompts.
+
+## Outcome promise
+
+Launch and market a validated product in 2 weeks using the `/ship` agent pipeline, even if you have never shipped before.
+
+## Course entry friction
+
+The buyer can build, but gets stuck when it is time to validate demand, position the product, create the offer, wire capture, and execute launch day without chaos.
+
+## Learning outcomes
+
+By the end of the course, the student will be able to:
+
+1. Turn a vague product idea into a clean `/ship` intake brief
+2. Validate demand and willingness-to-pay before overbuilding
+3. Position the product around a clear ICP, promise, and competitive frame
+4. Build a stronger offer using Hormozi-style value stack logic
+5. Set up awareness, lead capture, nurture, and closing as one GTM system
+6. Prepare launch assets before launch week instead of during it
+7. Run launch day with a command-center mindset across channels
+8. Review funnel data, identify bottlenecks, and plan the next iteration
+
+## Module map
+
+### Module 1 — Intake & Problem Framing
+**Hook:** Why 80% of side projects die before launch  
+**Outcome:** The student turns a messy idea into a brief that downstream agent teams can actually execute.
+
+**Teach lessons:**
+1. What `/ship` is really solving
+2. The intake template and required inputs
+3. Problem interviews and jobs-to-be-done basics
+4. Defining success criteria, constraints, and launch scope
+5. Bad brief vs strong brief teardown
+
+**Apply:**
+- Run your idea through `/ship` intake
+- Produce a one-page launch brief
+
+### Module 2 — Validate (Demand + Willingness-to-Pay)
+**Hook:** The 5 conversations rule  
+**Outcome:** The student gathers enough market signal to decide whether to proceed, re-angle, or kill the idea.
+
+**Teach lessons:**
+1. Validation before building more
+2. Outreach scripts for founder conversations
+3. Landing-page smoke tests in 48 hours
+4. Pricing signals and willingness-to-pay cues
+5. How to interpret weak vs strong demand
+
+**Apply:**
+- Ship a validate-test doc
+- Launch one simple validation page in 48 hours
+
+### Module 3 — Strategy & Positioning
+**Hook:** Why most MVPs have no positioning  
+**Outcome:** The student leaves with a strategic narrative that makes the product legible and differentiated.
+
+**Teach lessons:**
+1. ICP definition for people who can already code
+2. Positioning statement structure
+3. Competitive framing and category choices
+4. Message maps for product, audience, and channel
+5. Translating research into a launch thesis
+
+**Apply:**
+- Produce a strategy one-pager
+- Build a message map for the first launch
+
+### Module 4 — Build the Offer
+**Hook:** Offer math, why offer beats product  
+**Outcome:** The student packages the product into a clearer promise with stronger perceived value.
+
+**Teach lessons:**
+1. Hormozi value equation applied to `/ship`
+2. Building the value stack
+3. Bonuses, guarantees, and risk reversal
+4. Urgency, scarcity, and launch pricing logic
+5. Tiering the offer without bloating it
+
+**Apply:**
+- Write the Grand Slam offer for your product
+- Draft the pricing stack and guarantee section
+
+### Module 5 — Awareness + Lead Capture + Nurture + Closing
+**Hook:** The 4 workstreams that make a launch convert  
+**Outcome:** The student connects top-of-funnel attention to sales without treating every asset as a separate project.
+
+**Teach lessons:**
+1. Awareness content that creates the right kind of demand
+2. Lead magnet and opt-in architecture
+3. Nurture sequencing for belief shifts and trust
+4. Closing assets, objections, and CTA flow
+5. How the 4 workstreams share one conversion goal
+
+**Apply:**
+- Set up the 4 GTM pipelines for your product
+- Draft one awareness asset, one opt-in, one nurture touch, and one closing section
+
+### Module 6 — Pre-Launch Prep
+**Hook:** Launch day is won the week before  
+**Outcome:** The student assembles the launch system before the public announcement starts.
+
+**Teach lessons:**
+1. Pre-launch asset checklist
+2. Announcement cadence and timing
+3. Team mode, owners, and handoffs
+4. QA for links, forms, analytics, and payment
+5. Dry runs and contingency planning
+
+**Apply:**
+- Produce a pre-launch asset pack
+- Build a launch checklist with owners and due dates
+
+### Module 7 — Launch Execution
+**Hook:** Launch day command center  
+**Outcome:** The student can run launch day as an orchestrated operation instead of improvising in public.
+
+**Teach lessons:**
+1. Multi-channel publish sequence
+2. Live monitoring and signal reading
+3. Responding to comments, replies, and objections fast
+4. Updating assets mid-launch without losing focus
+5. When to push harder vs when to hold
+
+**Apply:**
+- Run a live launch-day simulation
+- Fill out the command-center tracker for one launch window
+
+### Module 8 — Measure & Iterate
+**Hook:** What to do on day 2 after launch  
+**Outcome:** The student knows how to read results, diagnose the weakest link, and prepare the next cycle.
+
+**Teach lessons:**
+1. Cohort and funnel review basics
+2. Measuring awareness, capture, nurture, and sales
+3. Finding the real bottleneck
+4. Converting launch learnings into roadmap decisions
+5. Planning the next campaign from evidence, not vibes
+
+**Apply:**
+- Produce a post-launch measure doc
+- Build a next-iteration roadmap
+
+## Approximate lesson count
+
+- 8 modules
+- 5 teach lessons per module = 40 core lessons
+- 1 hook + 1 to 2 apply items per module
+- Total course surface: ~56 lesson moments across video, workbook, and templates
+
+## Sample lessons
+
+### Free public lesson
+**Module 1, Lesson 1:** Run your idea through `/ship` intake  
+**Format:** full video + workbook  
+**Surface:** `/academia/ship/preview`
+
+### Gated preview lesson
+**Module 4, Lesson 3:** The Hormozi value stack applied to your offer  
+**Format:** preview video + workbook excerpt  
+**Gate:** email signup required
+
+## Module-to-friction map
+
+| Student friction | Module | Resolution |
+| --- | --- | --- |
+| “I have an idea, but no launch system.” | Module 1 | Creates a real intake brief and operating model |
+| “I do not know if anyone wants this.” | Module 2 | Validates demand before more effort goes in |
+| “My product is hard to explain.” | Module 3 | Clarifies ICP, positioning, and message hierarchy |
+| “The product is decent, but the offer is weak.” | Module 4 | Improves perceived value, pricing logic, and risk reversal |
+| “I create content, but it does not convert.” | Module 5 | Connects awareness, capture, nurture, and closing |
+| “Launch week feels chaotic.” | Module 6 | Forces launch prep before launch week starts |
+| “I freeze on launch day.” | Module 7 | Gives an execution playbook and monitoring loop |
+| “I do not know what to improve after launch.” | Module 8 | Installs a measurement and iteration system |
+
+## Course CTA copy
+
+### README CTA
+**Aprendé el pipeline completo → curso /ship ($497)**
+
+### Newsletter CTA
+**El curso /ship abre el [date]. Reservá tu lugar.**
+
+### Landing page primary CTA
+**Inscribirme al curso /ship**
+
+### Landing page secondary CTA
+**Ver la lección gratuita**
+
+## Why this course is paid
+
+The OSS repo gives students the system. The course gives them operator judgment, examples, templates, exercises, and a complete launch walkthrough so they can use the system end to end on a real product.
+
+## Repo artifacts included in this PR
+
+- `docs/course-outline.md`
+- `docs/course-lessons/module-1-lesson-1-workbook.md`
+- README CTA update linking the OSS tool to the paid course

docs/proofs/MAX-566/command-output.txt

@@ -0,0 +1 @@
+Generated from docs/course-outline.md for MAX-566 visual proof preview.