Menu
Update and review beanies.family launch plan status in Notion — progress, dates, karma level, and next actions
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | launch-status |
| description | Update and review beanies.family launch plan status in Notion — progress, dates, karma level, and next actions |
Review and update the beanies.family launch plan in Notion. Provides a concise status report and clear next steps.
/launch-statusCollect the following information:
Notion page IDs:
32c247d9-a99f-8188-b169-eacfdc48c05732c247d9-a99f-810b-8d5d-ded0c2579b4332c247d9-a99f-81f8-8100-da43f1e4c21632c247d9-a99f-8118-8f92-d254e752253632c247d9-a99f-8133-979c-c7b9ce6ebf0a32c247d9-a99f-8170-bfce-de833424661732c247d9-a99f-81a6-bb13-dd999197e9f832c247d9-a99f-8127-9335-fa73c32b93f732f247d9-a99f-81cf-8b2d-f336b80f422a32f247d9-a99f-8000-9be4-c939bb1ef690 (data source: 32f247d9-a99f-805b-928a-000b52e0de73)Current phase structure (as of Apr 3, 2026):
| Phase | Description | Gate |
|---|---|---|
| Phase 0 | Karma Building via Daily Karma Runs | Until 100+ karma |
| Phase 1 | First Feedback Posts (r/daddit, r/Parenting, r/SideProject) + Quora prep | Until engagement reviewed |
| Phase 2 | Launch Week (Blog, HN, Reddit, Quora) | After Phase 1 checkpoint |
| Phase 3 | Product Hunt + Amplify | After Phase 2 |
| Phase 4 | Engage & Iterate (incl. weekly Quora answers) | Ongoing |
Key account assets:
Determine:
ALWAYS update the Launch HQ page on every /launch-status run. This is the user's at-a-glance dashboard — it must reflect the latest status, metrics, and next actions. Never skip this step, even for minor updates.
First, read the current Launch HQ page to get all block IDs:
mcp__notion__API-get-block-children(block_id: "32c247d9-a99f-8188-b169-eacfdc48c057")
Then update ALL of the following sections. Use the block IDs from the page read — do not hardcode IDs (they may change if the page is reorganized).
Update Last updated: [today's date].
Block 32c247d9-a99f-8195-b127-e0d0901b6f97 — update with current target dates and phase status.
Update every block in this section:
Update each phase line with:
Update the Reddit karma bullet with current karma level and gate status.
Replace with current, actionable next steps organized by timeframe:
Update the summary paragraph with current karma status and strategy.
Block 32e247d9-a99f-8181-95e0-e5534a53d7a2 — update with [DATE] latest strategy note.
Block 336247d9-a99f-81ea-9ec3-c6e75ed250ed — update current karma level and gate status.
API format: Use mcp__notion__API-update-a-block with the block type at the top level (NOT nested in type):
# For paragraphs:
paragraph: {"rich_text": [{"type": "text", "text": {"content": "..."}}]}
# For bold labels:
paragraph: {"rich_text": [
{"type": "text", "text": {"content": "Label: "}, "annotations": {"bold": true}},
{"type": "text", "text": {"content": "value"}}
]}
# For bulleted lists:
bulleted_list_item: {"rich_text": [...]}
Output a concise status report in this format:
## Launch Status — [DATE]
**Current phase:** Phase N — [Name]
**Reddit karma:** X / 100 target
**Account age:** ~N weeks
**Days in current phase:** N
### Progress
- [x] Completed item
- [x] Completed item
- [ ] Pending item
### Blockers
- [Any blockers or risks]
### Next Steps (this week)
1. [Specific, actionable next step]
2. [Specific, actionable next step]
3. [Specific, actionable next step]
### Key Dates
| Phase | Est. Date | Status |
|-------|-----------|--------|
| Phase 0 complete | Apr 27 | [On track / At risk / Blocked] |
| Phase 1 start | Apr 28 | [Pending Phase 0] |
| Phase 2 (Launch) | May 12 | [Pending] |
| Phase 3 (PH) | May 19 | [Pending] |
If the launch timeline has shifted significantly or a phase gate has been reached, update the project memory at /home/greg/.claude/projects/-home-greg-projects-beanies-family/memory/project_launch_plan.md with the new status.
Track these across phases — report on uncompleted items:
Content (Phase 1 prep):
Technical (Phase 2 prep — Claude tasks):
Accounts (Phase 2 prep):
Quora (Phase 1 prep — leverage 10-year account):
Post Drafts (Phase 1 prep):
get-block-children on Launch HQ first to get current block IDs and see what needs changing.docs/launch/, docs/plans/ for launch items, or anywhere else) containing launch or marketing content. The repo is for code and product docs only.Auto-approved commit, push, CI monitor, and deploy to production
Auto-approved commit, push, and deploy to production — skips the CI/Security gate for fast, locally-verified deploys. Classifies what changed and deploys the Vue app and/or the Astro marketing site as needed (same target-classification as deploy-prod-auto, minus the remote-CI wait).
Turn a scattered, half-formed idea, bug report, or feature request into a complete, well-researched row in the "Beanies Main Issue Tracker" Notion DB — researching the codebase, recent commits, docs, and the web to fill every field, asking only about genuine gaps, checking for duplicates, showing the full proposed issue for approval, and then creating it as a "Not started" row that /beanies-pre-plan can pick up. Use this WHENEVER the user wants to capture, log, file, raise, open, add, or jot down an issue / bug / feature / idea / ticket / tracker item / TODO for beanies — even when they just describe a problem or wish ("the calendar feels cramped on mobile", "we should let users export their data", "remember to fix the flaky sync toast") without saying the word "issue". It is the front door to the tracker and the step BEFORE /beanies-pre-plan.
Standardized requirements-intake step that runs BEFORE beanies-plan. Collects complete, well-structured intent (via a copy/paste template or a Notion issue row), reviews EVERY field, asks the user to resolve anything missing/unclear/TBC (writing resolved values back to the tracker) before building, and — when a mockup is requested — generates a CIG-clamped UI mockup via the frontend-design skill, gets it approved, and stores it on the tracker. Only after explicit user approval does it hand a fully-populated initial prompt (plus any approved mockup) to beanies-plan. Use when the user says "pre-plan this", "intake this issue", "prep a plan for X", or invokes /beanies-pre-plan.
Create standardized plans (and optionally GitHub issues) using a mandatory 4-pass review discipline — initial draft, DRY/error-handling, sustainability/maintainability, and fresh-eyes final sweep — with full context preservation.
Review, prepare and publish a beanies.family "beanstalk" blog post that lives in the Notion Blog Posts database. Use this skill whenever greg mentions the blog, the beanstalk, a Friday post, publishing or reviewing a post, a post ID or Notion blog row, blog images, Substack cross-posting, or says anything like "it's blog day", "review my post", "is post 12 ready", "ship the blog", or "time for this week's post" — even if he doesn't name the skill. Also use it when asked to check a draft's tone, grammar, SEO, or images before publication, or to sync a Notion post into the repo.