Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
npx claudepluginhub foundry-works/claude-foundry --plugin foundryTask implementation skill for spec-driven workflows. Reads specifications, identifies next actionable tasks, and creates detailed execution plans. Use when ready to implement a task from an existing spec - bridges the gap between planning and coding. TRIGGER when: user explicitly asks to implement, continue work, or pick up the next task from a spec (e.g., "what's next", "continue", "implement"). Never call mcp task/spec tools directly for task workflow operations. DO NOT TRIGGER when: a <command-name> tag is present in the current turn (skill already loaded), called from a subagent, or model decides on its own that implementation should start.
AI-powered research skill with five workflows - chat (single-model conversation), consensus (multi-model synthesis), thinkdeep (systematic investigation), ideate (creative brainstorming), and deep (multi-phase web research). Supports persistent threads and research sessions. TRIGGER when: user asks for research, consultation, brainstorming, investigation, or deep research. Always route through this skill — never call mcp__plugin_foundry_foundry-mcp__research directly. DO NOT TRIGGER when: a <command-name> tag is present in the current turn (skill already loaded), called from a subagent, simple factual questions answerable from context, or codebase exploration (use Explore agent instead).
Review implementation fidelity against specifications by comparing actual code to spec requirements. Identifies deviations, assesses impact, and generates compliance reports for tasks, phases, or entire specs.
First-time setup for the foundry plugin (plugin:foundry@claude-foundry)
Spec-first development methodology that creates detailed specifications before coding. Creates structured specs with phases, file-level details, and verification steps. Includes automatic AI review, modification application, and validation. TRIGGER when: user explicitly asks to create a spec or plan, OR model detects work that would benefit from a spec (new feature, multi-file refactor, API integration, architecture change) — in the latter case, confirm with the user before invoking. Never call mcp authoring/spec/plan tools directly for spec creation workflows. DO NOT TRIGGER when: a <command-name> tag is present in the current turn (skill already loaded), called from a subagent, single-file edits, trivial fixes, or exploratory spikes.
Matches all tools
Hooks run on every tool call, not just specific ones
Executes bash commands
Hook triggers when Bash tool is used
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Autonomous spec-driven development workflow with multi-agent collaboration, specification management, and task orchestration
Specification-driven development workflow: specify → plan → tasks → implement
External tools integration skills for CLI utilities, APIs, and third-party services
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Autonomous spec-driven development loop for Claude Code with behavioral guardrails, knowledge graph integration, and design system support.
Comprehensive Spec-Driven Development toolkit with multi-language support, specialized agents, and integrated security/observability tools
Plan before you code. Verify against the spec. Ship with confidence.
Ad-hoc coding with AI assistants often leads to unclear requirements, untracked progress, and implementation drift. Claude Foundry brings structure to AI-assisted development through spec-driven development (SDD): you create a detailed specification first, then implement against it with granular task tracking and AI-powered verification.
Who it's for: Developers using Claude Code who want traceable, auditable AI-assisted development with clear requirements and verifiable outcomes.
| Requirement | Version | Notes |
|---|---|---|
| Python | 3.10+ | Required for foundry-mcp server |
| Claude Code | Latest | The CLI tool from Anthropic |
| foundry-mcp | Latest | MCP server (installed via pip) |
pip install foundry-mcp
Or with pipx for isolated installation:
pipx install foundry-mcp
Verify installation:
python -m foundry_mcp.server --help
From within Claude Code:
/plugin marketplace add foundry-works/claude-foundry
/plugin install foundry@claude-foundry
Restart Claude Code and trust the repository when prompted.
Note: The MCP server is automatically registered when you install the plugin. Do not manually add it with
claude mcp add.
Run setup - Ask Claude to configure permissions and verify installation:
Please run foundry-setup to configure the workspace.
Research (optional) - Ask Claude to explore the codebase or research best practices:
Research how authentication is currently handled in this codebase.
Do deep research on current best practices for JWT refresh tokens.
Describe what you want - Tell Claude what you want to build:
I want to add user authentication with JWT tokens.
Claude creates a spec with phases, tasks, and verification steps.
Implement - Ask Claude to work through tasks (verification is built into the spec):
Let's implement the next task from the spec.
Ship - Create a PR when the spec is complete:
Create a pull request for this completed spec.
A complete spec-driven development cycle:
# 1. Research (optional): Understand existing patterns
"Research how the current API handles errors"
# Single-model chat, multi-model consensus, or deep web research
# 2. Describe your feature: Claude creates the spec
"I want to add rate limiting to the API endpoints"
# Claude invokes foundry-spec, asks clarifying questions, creates spec
# Spec saved to specs/pending/, then activated after your approval
# 3. Implement: Work through tasks
"Let's implement the next task"
# Shows next task, you implement it, verification tasks auto-dispatch
# When foundry-implement hits a verify task, it runs foundry-review or tests
# 4. Ship: Create PR when spec is complete
"Create a PR for this spec"
# Generates PR from spec metadata, journals, and git history
research → describe intent → implement → (auto-verify) → create PR
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Explore Claude Work on Verify tasks Create PR
codebase creates tasks via auto-dispatch with full
or web spec dependency to review context
order or tests