By exerias21
Cross-tool (Claude Code + GitHub Copilot) skills for brainstorming, SDLC, eval-driven development, and repo onboarding. Single AGENTS.md and TASKS.md source of truth for both agents.
You run end-to-end tests in a fix loop, mirroring `/eval-harness`'s shape but for
Orchestrates a network-security audit by fanning out the four stages of the
Autonomous feature implementation pipeline. Takes a plan file, implements it,
You are a dedicated validation agent that checks whether a feature implementation
Clarification-heavy ideation skill for ambiguous or high-stakes ideas. Runs a three-pass loop (understand → saturate-by-questioning → plan-with-alternates) and dispatches perspective-frame sub-agents (inversion, pre-mortem, steelman, adjacent-reuse) before plan freeze. Output ends with an explicit expectation contract block. Invoke when the user says /brainstorm-deep, "I'm not sure what I want", "this is vague", "high stakes", "really important to get right", or asks for more rigor than /brainstorm provides. Use /brainstorm for fast cases and /brainstorm-team for autonomous multi-persona product strategy.
Launches a coordinated multi-agent team (5 agents in parallel) to produce a complete product strategy document: competitive research, codebase mapping, UX critique, ranked feature list, and detailed implementation blueprints. Use when the user wants heavy autonomous product research or says "brainstorm team", "what should we build next", "competitive analysis", "product review", or invokes /brainstorm-team. For conversational ideation with the user in-session, use /brainstorm instead.
Interactive brainstorming and feature ideation skill. Enters Plan mode to guide the user through structured creative exploration: clarifying the idea, exploring codebase context, generating multiple approaches, evaluating tradeoffs, and producing a concrete action plan. Use this skill whenever the user says /brainstorm, mentions "brainstorm", "let's think through", "I have an idea", "what if we", "how should we approach", "let's explore", or otherwise wants to ideate on a feature, improvement, or architectural change before jumping into code. This is the conversational planning companion — for heavy autonomous multi-agent product research, use /brainstorm-team instead.
Print a one-page guide to every brainstorm-toolkit skill installed in this repo, grouped by category, with the typical command chains. Use this when the user says /cheatsheet, asks "what skills do I have?", "what can the toolkit do?", "remind me the commands", or is onboarding a teammate to the toolkit. Also covers `/cheatsheet --brief` for a one-line-per-skill listing and `/cheatsheet <name>` for a deep-dive on a specific skill.
Pattern guide for ingesting external data (web scrapes, third-party APIs, file imports, user-generated content) into a project's database. Covers the three ingestion patterns (discovery pipeline, seed script, direct API), plus how to author a per-source web-discovery skill: WebSearch vs headless browser, the session-cookie pattern for authenticated sites, source trust tiers, and dedup-upsert. Use when adding a new scraper, import script, or automated data-collection job — or "how do I scrape X into the DB?".
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Cross-tool plugin for Claude Code + GitHub Copilot: focused, low-token skills for brainstorming, SDLC, eval-driven development, and repo onboarding. Single AGENTS.md and TASKS.md contract so both agents work from the same source of truth.
Most AI-agent task systems bolt on heavyweight task databases, multi-agent orchestrators, and inline templates that balloon every command to hundreds of lines. brainstorm-toolkit goes the other direction:
AGENTS.md, TASKS.md, GOTCHAS.md, .claude/project.json — so Claude Code, GitHub Copilot, Cursor, and friends all read the same files./sdlc is the heaviest thing in here and it's still one file.If you use the Claude Code plugin system, add this repo as a marketplace source or install directly:
# In Claude Code:
/plugin marketplace add <this-repo-url>
/plugin install brainstorm-toolkit
setup.sh (Claude, Copilot, or both)For Copilot users, or if you prefer file-based installs:
# Clone this repo once, anywhere
git clone <this-repo-url> ~/brainstorm-toolkit
# Inside any target repo:
bash ~/brainstorm-toolkit/setup.sh --target . --tools both
setup.sh copies:
skills/* → <target>/.claude/skills/<name>/ (Claude), <target>/.github/skills/<name>/ (Copilot), and <target>/.agents/skills/<name>/ (Codex), for skills whose metadata.brainstorm-toolkit-applies-to includes that tool. When a Copilot-optimized override exists in copilot/skills/<name>/, that version is installed for Copilot instead of the canonical one; Codex prefers a codex/skills/<name>/ override, then the Copilot overlay, then the canonical. The full skill directory is copied so bundled scripts, assets, and references stay available.disable-model-invocation: true, which keeps them available as slash commands without making them auto-load on semantic matching..github/prompts/*.prompt.md files from older installs are removed during Copilot installs so the workspace stops advertising prompt-file shims.agents/* → <target>/.claude/agents/ (Claude-only helper agents; VS Code can also discover Claude-format agents from .claude/agents/ when needed).scripts/* → <target>/scripts/.templates/AGENTS.md.template → <target>/AGENTS.md if missing. Symlinks CLAUDE.md → AGENTS.md on POSIX, else copies.templates/TASKS.md.template → <target>/TASKS.md if missing.templates/CHEATSHEET.md.template → <target>/CHEATSHEET.md if missing. This is the printable companion to /cheatsheet; once present, setup leaves user edits alone.templates/project.json.example → <target>/.claude/project.json.example (left for you to rename and edit).Re-running setup.sh is safe — it skips existing files unless you pass --force. Install only for one tool with --tools claude or --tools copilot.
setup.sh is bash; run it under WSL, Linux, or macOS. Windows-native git handles symlinks inconsistently, so the CLAUDE.md → AGENTS.md link falls back to a copy outside POSIX environments.
Every consumer repo gets four shared files:
| File | Purpose | Read by |
|---|---|---|
AGENTS.md | Architecture + agent conventions | Claude Code (via CLAUDE.md copy/symlink), Copilot, Cursor, Codex |
TASKS.md | Markdown checkbox task queue | All agents, humans, GitHub UI |
GOTCHAS.md | Project-specific pitfalls | /gotcha, /sdlc sanity check |
.claude/project.json | Runner config (tests, logs, eval) | /test-check, /eval-harness, /sdlc |
Every project.json key is optional — skills skip steps gracefully when config is missing. A repo with no project.json still gets useful behavior from /brainstorm, /task, /gotcha, etc.
npx claudepluginhub exerias21/brainstorm-toolkit --plugin brainstorm-toolkitAccess thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Complete developer toolkit for Claude Code
Intelligent draw.io diagramming plugin with AI-powered diagram generation, multi-platform embedding (GitHub, Confluence, Azure DevOps, Notion, Teams, Harness), conditional formatting, live data binding, and MCP server integration for programmatic diagram creation and management.
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.