Self-enhancing AI software development lifecycle — generates project-specific SDLC instances from meta-definitions
Conversational pipeline manager — add, customize, view, or remove Forge pipelines and their phase commands
Add a new task to an existing sprint mid-flight — mini intake, sequential ID assignment, store write, and collate
Ask Forge anything — project status, config, workflows, commands, version, or how-to questions
Detect drift between the knowledge base and agent definitions, propose surgical regeneration patches, and apply approved patches
Inspect or change Forge project configuration. Owns the mode field — the explicit verb for promoting a fast-mode install to full.
Validate Forge store query results — check completeness, detect low-confidence parses, identify missing relationships, and suggest corrective queries. Invoked after store-query-nlp returns results for high-stakes decisions.
🏮 Tomoshibi (灯) — Forge's concierge. Answers questions about project status, config, version, workflows, and commands. Also invokes forge:refresh-kb-links to update KB and workflow links in agent instruction files.
Refresh Forge KB and workflow links in agent instruction files (CLAUDE.md, AGENTS.md, etc.)
Sole authorized gateway for reading and writing the Forge JSON store (.forge/store/). Use whenever a workflow needs to write sprints, tasks, bugs, features, or events — or read/list/validate/transition them. All store mutations MUST go through store-cli.cjs, never by writing files directly.
Reference for the Forge NLP query grammar — entity synonyms, status synonyms, ordering tokens, FK phrases, and ID patterns. Use when constructing or debugging store-query-nlp queries, or to understand why a query returned unexpected results.
Query the Forge store using natural language. Use when you need to find tasks, bugs, sprints, or features by intent — e.g. 'open bugs in S12', 'blocked tasks', 'tasks implementing the auth feature', 'how many bugs are critical'. Returns structured JSON with entity IDs, titles, statuses, relationships, file refs, and INDEX.md excerpts.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
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.
Uses power tools
Uses power tools
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
⚡ Quick Start · 📦 Install · 🚀 Get Started · 📖 Command Reference · 🗺️ Onboarding Guides · 🔧 Customise · 🐛 Report a Bug
Forge is a Claude Code plugin that turns your codebase into a self-improving AI engineering team. Run it once on any project — it reads your stack, generates a complete set of project-specific agents, workflows, and a structured knowledge base, then deploys them as slash commands. Every sprint, the system learns from what it builds and gets sharper.
One install. One init. A full engineering practice that improves with every task.
1. Install Forge (once, works across all your projects):
# Stable (recommended)
/plugin marketplace add Entelligentsia/skillforge
/plugin install forge@skillforge
# Canary (latest development build)
/plugin marketplace add Entelligentsia/forge
/plugin install forge@forge
2. Bootstrap your project:
cd /path/to/your/project
/forge:init
Forge scans your codebase and generates everything in ~10–15 minutes. No config files to fill in.
3. Run your first sprint:
/sprint-intake # Capture sprint requirements in a structured interview
/sprint-plan # Break requirements into tasks with estimates and dependencies
/run-sprint S01 # Execute — Plan → Review → Implement → Review → Approve → Commit
/retrospective S01 # Close the sprint and feed learnings back
That's it. Forge handles the rest.
Claude Code is capable. But left unstructured, it:
The more complex your project, the worse this gets.
Forge runs once against your codebase and generates a complete, project-specific engineering practice — then deploys it as a multi-agent team 
Forge doesn't ask you to fill in a config file. It reads your codebase — routes, models, tests, CI pipeline, auth patterns — and generates personas, workflows, and review criteria that reflect how your project actually works. The Engineer persona knows your entity names. The Supervisor knows your security patterns. The Architect knows your deployment constraints.
Every completed task feeds the knowledge base. The Supervisor adds new patterns to the review checklist when it catches something worth catching again. The Bug Fixer tags root causes and builds preventive checks. The Retrospective agent promotes what's working and prunes what isn't. By Sprint 3, the system understands your project better than any static prompt ever could — and it keeps improving.
Forge generates everything in your language and adapts to whatever framework you're running. It makes no assumptions about your stack until it reads it. Where popular stacks have well-established best practices — Django migrations, Vue Composition API, Rails conventions — Forge's generated workflows encode those opinions explicitly. Everything else is derived from what it finds.

npx claudepluginhub entelligentsia/forge --plugin forge10 Claude Code skills for production LLM integration — structured generation, RAG, guardrails, prompt engineering, tool use, agent loop, graceful degradation, evaluation harness, and tool synthesis
10 Claude Code skills for Three.js 3D development — scene setup, geometry, materials, lighting, textures, animation, loaders, shaders, post-processing, and interaction
Automatic security scanner for Claude Code plugins — detects newly installed or updated extensions and scans for prompt injection, malicious hook scripts, and data exfiltration
11 Claude Code skills for software design patterns — GoF creational, structural, and behavioural patterns plus enterprise and DDD tactical patterns (Repository, CQRS, Domain Events, Anti-Corruption Layer)
8 Claude Code skills for Meta Quest PWA XR engineering — session lifecycle, rendering, input, passthrough, anchors, layers, RATK, and PWA/Quest packaging
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Access thousands of AI prompts and skills directly in your AI coding assistant. Search prompts, discover skills, save your own, and improve prompts with AI.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Complete developer toolkit for Claude Code