The Startup plugin for Grok Build

Name: The Startup
Author: rsmdt

Community Claude Code plugin, installs in GrokPluginDevelopment

The Agentic Startup - A collection of Claude Code commands, skills, and agents.

How to install The Startup in Grok Build

1. Add this repo as a plugin marketplace in Grok Build (once per computer):

grok plugin marketplace add rsmdt/the-startup

2. Install the plugin:

grok plugin install start@rsmdt/the-startup --trust

✓ Install-checked in Grok Buildchecked Oct 18, 2026

Review before you trust it. --trust lets this plugin's hooks, MCP servers and scripts run code on your computer. It's a community repo that neither xAI nor GrokStacks has reviewed, so read its code first.

This repo's marketplace has 2 plugins; we checked start, team. Install another the same way: grok plugin install <name>@rsmdt/the-startup --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Inside Grok Build: type /plugins, open the Marketplace tab, press a and add rsmdt/the-startup, then select start and press i.

Command format: Grok Build's plugin guide

What we checked: on Oct 18, 2026 it installed with grok 1.0.62 and Grok found 36 skills, 1 subagent. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (36)

analyze — Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "wh
brainstorm — You MUST use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.
constitution — Create or update a project constitution with governance rules. Uses discovery-based approach to generate project-specific rules.
debug — Systematically diagnose and resolve bugs through conversational investigation and root cause analysis
document — Generate and maintain documentation for code, APIs, and project components
implement — Implementation entry point. Use to execute a completed specification. Auto-detects the decomposition tier (Direct, Incremental, or Factory) from spec artifacts and dispatches to the matching execution sub-skill.
implement-direct — Lightweight implementation orchestrator for low-complexity work — fixes, refactors, doc changes, or single-AC features that do not warrant a phase plan or factory decomposition.
implement-factory — Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.
implement-incremental — Linear phase-loop orchestrator for single-feature implementation plans. Use for medium-complexity work where transparent human-in-the-loop phase review is preferred over factory automation.
refactor — Refactor, simplify, or clean up code for improved maintainability without changing business logic
review — Multi-agent code review with specialized perspectives (security, performance, patterns, simplification, tests)
specify — Create a comprehensive specification from a brief description. Runs requirements gathering, solution design, and decomposition — routing decomposition to one of three tiers based on a complexity classifier: Direct (no plan), Incremental (li
specify-factory — Decompose a multi-feature or multi-component specification into factory-consumable artifacts. Use this for high-complexity work — multiple features, three or more components, or parallel-eligible workstreams.
specify-incremental — Decompose a single-feature specification into a linear, phase-by-phase implementation plan. Use this for medium-complexity work — single feature, one or two components — where transparent human-in-the-loop phase review is preferred over fac
specify-meta — Scaffold, status-check, and manage specification directories. Use when creating a new spec, reading spec status, transitioning between phases, or logging decisions on a spec in .start/specs/.
specify-requirements — Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/.
specify-solution — Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution.md files in .start/specs/.
test — Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership. Ensures MECE
validate — Validate in any of six modes — spec quality, single-file review, spec-to-implementation drift, constitution rule enforcement, comparison between two artifacts, or sanity-checking your understanding. Use when checking a spec by ID, validatin
writing-skills — Use when creating new skills, editing existing skills, auditing skill quality, converting skills to markdown conventions, or verifying skills before deployment. Triggers include skill authoring requests, skill review needs, or "the skill do
feature-prioritization — RICE, MoSCoW, Kano, and value-effort prioritization frameworks with scoring methodologies and decision documentation. Use when prioritizing features, evaluating competing initiatives, creating roadmaps, or making build vs defer decisions.
pattern-detection — Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.
project-discovery — Unified codebase discovery across structure navigation, tech-stack detection, and documentation extraction. Use when onboarding to a project, locating implementation paths, identifying frameworks/tooling, or validating docs against code rea
requirements-elicitation — Requirement gathering techniques, stakeholder analysis, user story patterns, and specification validation. Use when clarifying vague requirements, resolving conflicting needs, documenting specifications, or validating requirements with stak
user-research — User research and insight synthesis for interviews, usability testing, personas, journey mapping, and actionable product/design recommendations. Use when planning studies, collecting evidence, synthesizing patterns, or converting findings i
agentic-patterns — Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui. Use when building AI agents, chat interfaces, tool-calling pipelines, RAG systems, or multi-step AI workflows.
api-contract-design — REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns. Use when designing APIs, reviewing API contracts, evaluating API technologies, or implementing API endpoints.
architecture-selection — System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria. Use when designing system architectures, evaluating patterns, or plan
domain-modeling — Unified domain and data modeling for business entities, invariants, schema design, aggregate boundaries, and evolution strategy. Use when designing business models, schema changes, bounded contexts, or consistency rules.
frontend-patterns — Context enrichment for frontend UI development using shadcn/ui and Tailwind CSS. Use when building component libraries, implementing UI designs, theming, or working with accessible React components.
technical-writing — Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedure
testing — Writing effective tests and running them successfully. Covers layer-specific mocking rules, test design principles, debugging failures, and flaky test management. Use when writing tests, reviewing test quality, or debugging test failures.
platform-operations — Unified platform operations guidance for CI/CD pipeline design, deployment strategies, observability, SLI/SLOs, and incident-ready rollouts. Use when building release workflows, production monitoring, or reliability controls.
code-quality-review — Unified code review skill for correctness, design, readability, security, performance, testability, accessibility, and error-handling conventions. Use when reviewing changes, enforcing quality standards, or identifying technical debt.
performance-analysis — Measurement approaches, profiling patterns, bottleneck identification, and optimization guidance. Use when diagnosing performance issues, establishing baselines, identifying bottlenecks, or planning for scale. Always measure before optimizi
security-assessment — Vulnerability review, threat modeling, OWASP patterns, and secure coding assessment. Use when reviewing code security, designing secure systems, performing threat analysis, or validating security implementations.

Plugins in this marketplace (2)

start — Core workflow commands with output styles and productivity hooks
team — Team consisting of specialized agents for software development

About this listing

The Startup is a community plugin on GitHub by rsmdt, written as a Claude Code plugin that Grok Build installs. We install-checked it in Grok; we haven't run it in a live session or reviewed its code. When we installed it, Grok found 36 skills, 2 plugins in this marketplaces. Its license is MIT. We checked commit 88d447c7fb84. It's one of 409 listings in the Development category on GrokStacks.

The Startup FAQ

How do I install The Startup in Grok Build?

Add the repo as a marketplace with grok plugin marketplace add rsmdt/the-startup, then run grok plugin install start@rsmdt/the-startup --trust. This repo's marketplace has 2 plugins; we checked start, team. Install another the same way: grok plugin install <name>@rsmdt/the-startup --trust (names under 'What it contains'). Then start a new Grok session, or press r in /plugins, to load it.

Is The Startup an official Grok Build plugin?

No. The Startup is a community plugin on GitHub by rsmdt, not in xAI's official Grok Build marketplace. We checked that it installs and what Grok loads from it, but haven't run it in a live Grok session or reviewed its code.

What does The Startup include?

According to what Grok loaded in our install check, The Startup includes 36 skills, 2 plugins in this marketplaces: analyze, brainstorm, constitution, debug, document, implement….

Details

Type: Plugin
Category: Development
Source: Community Claude Code plugin, installs in Grok
License: MIT
Author: rsmdt
Keywords: claude-code, claude-code-plugin, claude-marketplace, claude-plugin
Source repo: https://github.com/rsmdt/the-startup
Checked commit: 88d447c7fb84
Homepage: https://www.r16t.com/agentic-startup
Checked by GrokStacks: Install-checked in Grok Build on Oct 18, 2026; not run in a live session

Something wrong or missing? Submit or improve this listing. Marketplace listings also refresh automatically every night.

For maintainers: badge and embeds

Maintain The Startup? Add the badge; it links to this page.

Markdown

[![Listed on GrokStacks](https://grokstacks.com/badge.svg)](https://grokstacks.com/p/the-startup/)

HTML

<a href="https://grokstacks.com/p/the-startup/"><img src="https://grokstacks.com/badge.svg" alt="Listed on GrokStacks" width="164" height="28"></a>

Embed card (static HTML and inline CSS, no JavaScript). Preview:

The StartupCommunity plugin for Grok Build · 36 skills, 2 plugins in this marketplacesThe Agentic Startup - A collection of Claude Code commands, skills, and agents.View on GrokStacks →

<a href="https://grokstacks.com/p/the-startup/" style="display:block;max-width:380px;box-sizing:border-box;padding:14px 16px;border:1px solid #2a2e3c;border-radius:12px;background:#0a0b0f;color:#e8eaf0;font:14px/1.45 -apple-system,Segoe UI,Roboto,Helvetica,Arial,sans-serif;text-decoration:none"><span style="display:block;font-size:16px;font-weight:700;color:#e8eaf0">The Startup</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 36 skills, 2 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">The Agentic Startup - A collection of Claude Code commands, skills, and agents.</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[The Startup on GrokStacks](https://grokstacks.com/p/the-startup/)**: Community plugin for Grok Build with 36 skills, 2 plugins in this marketplaces. Install: `grok plugin install start@rsmdt/the-startup --trust` (after `grok plugin marketplace add rsmdt/the-startup`)

More on badges, embeds and keeping your listing up to date: GrokStacks for plugin authors.

Also in Development

Abap2UI5

Build UI5 Apps Purely in ABAP

Community Claude Code plugin, installs in GrokPluginDevelopment

Accessibility Agents

Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating inaccessible code.

Community Claude Code plugin, installs in GrokPluginDevelopment