Framework plugin for Grok Build

Community Claude Code plugin, installs in GrokPluginDevelopment

Marketplace Framework AI-Driven Dev : Context Engineering, Plugins, Agents, Skills, Hooks, Templates, SDLC

How to install Framework in Grok Build

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

grok plugin marketplace add ai-driven-dev/framework

2. Install the plugin:

grok plugin install aidd-context@ai-driven-dev/framework --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 9 plugins; we checked aidd-context, aidd-dev, aidd-vcs. Install another the same way: grok plugin install <name>@ai-driven-dev/framework --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 ai-driven-dev/framework, then select aidd-context 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 29 skills, 2 subagents. That's an install check only: we haven't run it in a live Grok session.

What it contains

Skills (29)

  • 00-onboard — Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
  • 01-bootstrap — Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
  • 02-project-memory — Build the project's memory of its architecture, conventions, and decisions, and wire it into your AI tools. Use when the user wants to set up or refresh project memory, or rewire it into a tool. Not for editing one existing memory file.
  • 03-context-generate — Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
  • 04-skill-generate — Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
  • 05-rule-generate — Create, update, publish or delete a coding rule across host AI tools. Use when adding, changing or removing a rule, convention or coding standard. Not for skills, agents or hooks.
  • 06-agent-generate — Generate an agent across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor an agent, subagent or specialized role. Not for other artifacts like skills, rules, commands, hooks.
  • 07-command-generate — Generate a flat slash command across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a one-shot slash command. Not for multi-step skills or other artifacts like rules, agents, hooks.
  • 08-hook-generate — Generate a hook, a handler that runs at a lifecycle event, across the host AI tools. Use when the user wants to create, scaffold, or refactor a hook, or automate an action at a lifecycle point. Not for other artifacts like skills or rules.
  • 09-mermaid — Generate a valid Mermaid diagram from a written source through a plan, generate, review loop. Use when the user wants to turn an architecture, lifecycle, or flow into a Mermaid diagram. Not for other diagram formats or image rendering.
  • 10-learn — Capture durable project learnings. Use when the user wants to remember, record, or formalize a decision, convention, lesson, pitfall, reusable workflow, or review finding. Not for preferences or temporary notes.
  • 11-explore — Explore the current project across its tooling, context, and codebase. Use to survey what is installed, see what is available, or find which skill, agent, or rule fits a goal. Not for choosing the next step or running an item; it only point
  • 12-cook — Manages project recipes and practical guides. Use when the user wants to find a recipe, document a technique, research improvements, follow an existing guide, or check that its steps are usable.
  • 01-plan — Turn a request, ticket, or file into a phased implementation plan. Use to plan a feature before building, or to turn a ticket into phases. Do NOT use to write code or review a diff.
  • 02-implement — Write an existing plan's code, phase by phase, until every acceptance criterion holds. Use when a plan exists and needs implementing. Do NOT use to write a plan, review a diff.
  • 03-assert — Assert the work behaves by iterating the project's coding assertions until they pass, plus optional architecture and frontend facets. Use to validate an implementation. Not for reviewing or writing tests.
  • 04-audit — Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.
  • 05-review — Reviews a change or a diff and says whether it is ready to ship, naming every problem with its fix. Use when the user wants a change checked before it ships. Not for fixing what the review finds, and not for auditing a whole codebase.
  • 06-test — Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use
  • 07-refactor — Improve code across four axes (cleanup, performance, security, architecture) by scanning and fixing, or applying a pushed audit report. Use when the user wants to refactor, optimize, harden, or remove code. Not for read-only diagnosis or ad
  • 08-debug — Reproduce and fix a known bug, or find an unknown root cause by hypothesis validation. Use when the user wants to fix a bug, find why something breaks, or reopen a stuck investigation. Not for building a feature or reviewing a diff.
  • 09-for-sure — Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goal
  • 10-batch — Split a request into independent tasks, execute them in parallel, and summarize each agent's task, status, and result. Use when the user says "batch" or asks to execute a multi-part request in parallel.
  • 00-repo-init — Initialize a project repository with git init, a default branch, a bootstrap commit, CONTRIBUTING.md, and optionally the remote. Use when the user wants to init or set up a new repo, or publish to a remote. Not for committing, opening a PR,
  • 01-commit — Create atomic conventional commits; safely retry scoped hook fixes; optionally push. Use when the user wants to commit changes, optionally pushing the branch. Not for amending, rebasing, opening a pull request, or tagging a release.
  • 02-pull-request — Create a draft pull or merge request from the current branch, in whatever VCS tool the project uses. Use when the user wants to open a pull or merge request. Not for committing, pushing, or merging a branch.
  • 03-release-tag — Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
  • 04-issue-create — Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.
  • resolve-conflict — Resolves deterministic Git conflicts or approved choices. Use when the user wants to resolve a merge, rebase, or cherry-pick conflict. Not for deciding between competing implementations or committing changes.

Hooks (1)

  • hooks — SessionStart

Plugins in this marketplace (9)

  • aidd-context — Knowledge production: project bootstrap, project init, generation of context artifacts (skills, agents, rules, commands, hooks), mermaid diagrams, learn, discovery
  • aidd-dev — Code transformation: plan, implement, assert, audit, review, test, refactor, debug, for-sure. Hosts engineering agents.
  • aidd-vcs — External artifacts: commit, pull-request, release-tag, issue-create
  • aidd-pm — Product backlog artifacts, refinement, Product Briefs, Epics, User Stories, Tasks, Spikes, Defects, requirements, and specs.
  • aidd-orchestrator — Orchestration: synchronous SDLC pipeline, async issue-to-PR automation, and product backlog.
  • aidd-refine — Meta-cognition: refine input through brainstorming, refine output through challenge, blind-spot scanning, and fact-checking.
  • aidd-ui — ALPHA, not ready for use. UI and UX concern: design, review, and improve frontend interfaces.
  • aidd-telemetry — Measurement: counts the tokens of Claude Code sessions per task, ticket, model and day, locally. The hooks ask for a task on plain node; its two skills reach the `aidd` CLI to turn it on and answer.
  • aidd-qa — Acceptance QA: validates observable behavior against acceptance criteria and records reviewer evidence. Browser is the only supported interface today.

About this listing

Framework is a community plugin on GitHub by ai-driven-dev, 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 29 skills, 1 hook, 9 plugins in this marketplaces. Its license is MIT. We checked commit 0768b9edc4c3. It's one of 409 listings in the Development category on GrokStacks.

Stacks Weekly: every new Grok Build and Codex plugin, every Tuesday.

One short email for GrokStacks and CodexStacks readers, with each new plugin's install line and what it ships. Subscribe and get the free starter list: 20 Grok Build plugins worth installing first.

You'll get a confirmation email first. Unsubscribe anytime.

Framework FAQ

How do I install Framework in Grok Build?

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

Is Framework an official Grok Build plugin?

No. Framework is a community plugin on GitHub by ai-driven-dev, 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 Framework include?

According to what Grok loaded in our install check, Framework includes 29 skills, 1 hook, 9 plugins in this marketplaces: 00-onboard, 01-bootstrap, 02-project-memory, 03-context-generate, 04-skill-generate, 05-rule-generate….

Details

Type
Plugin
Category
Development
Source
Community Claude Code plugin, installs in Grok
License
MIT
Author
ai-driven-dev
Keywords
agent, agentic, ai, ai-driven-dev, ai-driven-development, commands, context-engineering, harness-engineering, hooks, marketplace, plugins, rules
Source repo
https://github.com/ai-driven-dev/framework
Checked commit
0768b9edc4c3
Homepage
https://www.ai-driven-dev.fr/
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 Framework? Add the badge; it links to this page.

Listed on GrokStacks

Markdown

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

HTML

<a href="https://grokstacks.com/p/framework/"><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:

<a href="https://grokstacks.com/p/framework/" 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">Framework</span><span style="display:block;margin:2px 0 8px;font-size:12px;color:#9aa0b1">Community plugin for Grok Build · 29 skills, 1 hook, 9 plugins in this marketplaces</span><span style="display:block;margin:0 0 10px;color:#c9cdd8">Marketplace Framework AI-Driven Dev : Context Engineering, Plugins, Agents, Skills, Hooks, Templates, SDLC</span><span style="font-size:12px;font-weight:600;color:#7c9cff">View on GrokStacks →</span></a>

Markdown summary

**[Framework on GrokStacks](https://grokstacks.com/p/framework/)**: Community plugin for Grok Build with 29 skills, 1 hook, 9 plugins in this marketplaces. Install: `grok plugin install aidd-context@ai-driven-dev/framework --trust` (after `grok plugin marketplace add ai-driven-dev/framework`)

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

Also in Development

All 409 development listings →