Eastkap

autocomp-tick

Run exactly one tick of the autocomp autonomous company — read state, plan via the CEO role, dispatch role subagents, gate any money/send/destructive action through approvals, record everything to the append-only ledger, report, and reschedule. Use when running or resuming the autocomp loop in the autocomp repo, or when the user says "run a tick", "/autocomp", "advance the company", or starts the loop.

ceo

Work the board like the CEO/CTO — read the ENTIRE kanban, make an educated decision on every open card (do now / unblock / wait / human / stale), then EXECUTE the highest-leverage move immediately, invoking any other skill or tool the move needs. Consume-first — drain existing cards before creating new GTM cards or building anything. Use when the owner says "/ceo", "what's the banger move (and do it)", "work the board", "read the kanban and do something", or an interactive session should act instead of report.

Web & Frontend Listed

fetch-protected

Fetch a page that is behind a bot wall — Cloudflare / Turnstile / hCaptcha / reCAPTCHA / DataDome / Akamai — using a real human-like browser via TRAWL (a FlareSolverr-v2-compatible solver that drives a genuine Camoufox Firefox). Use when WebFetch/curl return a challenge page, 403, "Just a moment…", "Checking your browser", or an empty/blocked body, or when a task says to scrape/verify a site known to block bots. NOT for auth-gated sites (Reddit login, paywalls) — a solver doesn't beat a real login.

initiate-ceo

Run exactly ONE bounded cycle of the persistent CEO orchestrator lane — sweep the whole board + context stream, verdict and route cards by tagging them for cto/qa/gtm, keep approvals and money honest, dream new tasks only within Rule 17, then record and heartbeat. Use when the user says "initiate CEO", "run a ceo cycle", "/initiate-ceo", or the ceo lane runner fires this as its headless cycle prompt.

initiate-cto

Run exactly ONE bounded cycle of the persistent CTO build lane — sweep the cto queue + context stream + ops logs, atomically claim one cto-tagged card, build/test it small, finish into review with the qa tag, then record and heartbeat. The CTO is the ONLY lane that writes to the repo. Use when the user says "initiate CTO", "run a cto cycle", "/initiate-cto", or the cto lane runner fires this as its headless cycle prompt.

initiate-gtm

Run exactly ONE bounded cycle of the persistent GTM distribution lane — sweep the gtm queue + context stream + scoreboard, atomically claim one gtm-tagged card or run one pre-authorized bot-identity distribution step (directories, SEO/GEO, indexing), verify every submission live, stage gated sends as PENDING, then record and heartbeat. Use when the user says "initiate GTM", "run a gtm cycle", "/initiate-gtm", or the gtm lane runner fires this as its headless cycle prompt.

initiate-qa

Run exactly ONE bounded cycle of the persistent QA verification lane — sweep the qa queue + context stream, atomically claim one review-status card, verify it from INDEPENDENT evidence via a matched verifier persona, verdict PASS→done / FAIL→back to the acting lane, then record and heartbeat. QA is the only lane that moves review→done. Use when the user says "initiate QA", "run a qa cycle", "/initiate-qa", or the qa lane runner fires this as its headless cycle prompt.

launch-directories

Launch a product across startup/launch directories (Product Hunt-style listings) by driving the real logged-in boseclaw Camoufox session — one tested, reusable flow script per directory, with proof screenshots + a live-status audit. Use when the user says "launch <product> on the directories", "submit to directories", "run the directory signups", "do the directory launch", or wants to add a directory, re-run a launch, or audit which listings went live.

next-move

Decide the single highest-leverage next thing to build or do — to close the gap to our competitors (Polsia, Pancake, NanoCorp) and reach the next revenue milestone (first signup, first sale, launch). Use when the owner asks "what's next", "what should we build next", "what gets us closer to <rival>", "how do we get our first sale", or when a tick/session needs to re-pick priorities instead of just draining the backlog top-down. Produces ONE pick with a verifiable success criterion + the honest binding constraint, not a list.

API & Backend Listed

solve-captcha

Solve an interactive CAPTCHA (reCAPTCHA v2, hCaptcha, or Cloudflare Turnstile) that a real browser can't clear passively — image challenges, "select all…" grids — by paying 2Captcha for a token and injecting it into the page. Use when a signup/form flow hits a CAPTCHA wall (esp. in the directory-launch flows), when the user says "solve the captcha", "wire in the solver", "use 2captcha", or when Camoufox's fingerprint isn't enough to pass a challenge. NOT for Cloudflare interstitials Camoufox already passes, and NOT a substitute for OAuth login (prefer "Continue with Google" first — it usually skips the CAPTCHA entirely).