indigoai-us

Deploy or share generated HQ artifacts through hq-deploy.

Mark a company as HQ Pro cloud-backed and sync its team setup.

Send HQ Sync direct messages, prompts, details, or scheduled notes to teammates.

Run a full bidirectional sync for cloud-backed HQ companies.

Scaffold a new HQ company AND optionally take it all the way to operational — business-discovery interview, seeded knowledge/workers/skills/projects, brand design packs (generated from website/PDF/Drive and bound to deploys via policy), connected integrations, org groups + ACL rules, teammate invites, and optional cloud agents.

Resolve HQ Sync conflicts by choosing local, cloud, or discard.

Manually log a time estimate.

Run hands-on HQ workflow lessons.

Run an HQ-issued Slack bot — arm a per-bot @-mention watcher that spawns an autonomous Claude worker per mention. Pass the bot's slug (e.g. `hassaan`), a scope flag (`-c <company-slug>` or `--personal`), and optionally a workspace (`-w <slack-team-domain>`; auto-derived for `--personal` from SLACK_CREDENTIALS_JSON). The watcher resolves scope/workspace before personUid, using the sole local cache entry or an exact selected-vault bot-token namespace match; pass `-u <prs_…>` to override. It verifies and injects scoped `ANTHROPIC_API_KEY` into detached workers, handles the one-time bypass-permissions gate, resolves `<personUid>/HQ_SLACK_BOT_TOKEN_<NAME>_<WORKSPACE>`, infers the creator's Slack user_id (used as a DM gate), enumerates channels, and dispatches workers. Workers respond in-thread, ignore DMs from non-creators, and never call AskUserQuestion.

Surface architectural friction and propose deepening opportunities — turn shallow modules into deep ones for better testability and AI-navigability. Output: ranked candidate list with deletion-test outcome, leverage/locality scoring, file refs. Never edits code directly; presents candidates and walks the user through grilling-style design decisions for picked candidates. Use when the codebase is hard to change, when /diagnose hands off "no good test seam," or when planning a refactor wave.

Shared vocabulary and discipline for designing deep modules (a lot of behaviour behind a small interface, at a clean seam). Use when designing module boundaries or interfaces, or when another skill needs the deep-module vocabulary. Triggers on "deep module", "interface design", "design it twice".

Disciplined diagnosis loop for hard bugs, performance regressions, and intermittent failures. Build a deterministic feedback loop FIRST, then reproduce → hypothesise (3-5 ranked) → instrument (one variable at a time, tagged probes) → fix at the correct seam → cleanup + post-mortem. Use when the dominant problem is "I cannot reliably reproduce or measure this." For bugs that reproduce reliably with unknown root cause, use /investigate instead.

Actively build and sharpen a project's domain model — challenge fuzzy or overloaded terms against a glossary, stress-test with edge cases, and maintain CONTEXT.md as the source of truth for a ubiquitous language. Use when the user wants to pin down domain terminology, resolve a naming conflict, define a ubiquitous language, or when another skill needs to produce or sharpen the domain model. Triggers on "what should we call this", "domain model", "ubiquitous language", "define these terms", "update CONTEXT.md".

Enforce test-driven development with RED→GREEN→REFACTOR cycle and coverage validation

Break a plan, spec, or conversation into tracer-bullet vertical-slice tickets, each declaring its blocking edges (dependency order). Use when you have a plan/spec/PRD and need it decomposed into independently-executable tickets. Triggers on "break into tickets", "slice this into tasks", "vertical slices", "tracer bullets".

Plan a chunk of work too big for one agent session with a foggy destination — chart a shared map of investigation tickets and resolve them one per session until the path is clear. Use when the effort is too large to hold in one planning pass and the destination is unclear. Triggers on "too big to plan", "chart a map", "investigation tickets", "foggy scope".

Generate ASCII block-art banner images for social posts and OG images. Dark midnight aesthetic with faded {company} text on near-black background. Two sizes — 1080x1080 (social) and 1200x630 (OG). Use for product announcements, project launches, concept visuals, and repo OG images.

Explore approaches and tradeoffs before committing to a PRD. Research HQ context, compare options, surface unknowns, generate brainstorm.md with recommendation.

Post-ship documentation sync — updates README, CLAUDE.md, architecture docs, and INDEX files to match what actually shipped. Use after merging a PR, completing a project, or deploying a release. Triggers on "update docs", "sync documentation", "docs are stale", "document what shipped".

Execute a single PRD story through coordinated worker phases (Ralph pattern). Each worker handles its domain, passes context to the next, with back-pressure (tests/lint/typecheck) keeping code on rails.

Prepare for a new session to continue this work. Captures session learnings, syncs domain knowledge and insights, commits dirty repos, writes a thread file and handoff.json, updates INDEX files, and refreshes the search index. Ensures continuity across sessions.

Capture and classify learnings, route to structured policy files (rules) or insight files (educational knowledge). Deduplicates via qmd (Grep fallback), rebuilds policy digest after policy changes. Callable manually or from /execute-task, /run-project, /handoff, /checkpoint. Use --hard flag for hard-enforcement rules.

Plan a project and generate PRD for execution. Creates prd.json + README.md with full HQ context awareness. Runtime-agnostic — executes identically in Claude Code and Codex. Adapts interview depth to brainstorm context if available.

Project or session retrospective — review what happened, surface patterns, and feed learnings back to /learn. Two modes — PROJECT (completed project arc) and SESSION (recent work session). Triggers on "retro", "retrospective", "what did we ship", "what went well", "lessons learned".

Archive Claude Code chat sessions that haven't been used in the last N days (default 2). Lists sessions, surfaces decisions (open PRs, directory scope), re-pulls fresh IDs, then archives in batches with confirmation. Use when asked to "archive old chats", "clean up unused chats/sessions", or "archive chats not used in X days".