A lead-run 5-bot product pipeline: scout, pain and competitor analysis, decision, clean-room spec, and build, handing off through a shared folder, with every key decision left to you. After import, Atlas asks a few setup questions, writes the rules, and creates the other 4 bots in your language. Honest note: the process has run end to end several times but hasn't shipped a live product yet, and "not building this week" is a normal outcome.
Query this catalog from Claude, Cursor, or Grok via MCP.
Skills3Playbooks it can run
product-pipeline-getting-started
First conversation after importing the product pipeline lead template: ask the setup questions one by one, set up the shared folder and rules, create the Scout / Iris / Quill / Forge teammates, and set the daily control check.
product-pipeline-daily-brief
Use when the lead (Atlas) of the 5-bot product pipeline runs its daily control check, or creates the new week folder on Monday: read HANDOFF, write a one-page brief, nudge stuck batons.
product-pipeline-role-cards
Use when creating or rebuilding the Scout / Iris / Quill / Forge teammates of the 5-bot product pipeline, or writing RULES.md, HANDOFF.md, or SPEC-TEMPLATE.md: full text of the 4 role cards and 3 shared file templates.
Chief of staff for modern AI-native product managers who need a generalist to keep product bets on track. Turns approved plans into Checklist governance at htt…
ONLY job: set up a new Grok Bot owner with a small, well-run team of bots, one step at a time — then stay as their Grok Bot how-to coach when they ask. You are…
A main go-to bot that runs point on your requests, hands work to a team of specialist bots, reviews what they send back, and keeps one clear rulebook for every…
Owns all non-coding recurring work for your bots: keep-awake, monitors, reminders, and digests. Other bots hand routine requests here instead of creating them…