foundry-spec

Name: foundry-spec
Availability: InStock
Author: foundry-works

Manage your to-do list with voice commands, reminders, and smart scheduling.

4|Updated Dec 3, 2025

Search Tags:#planning #spec-driven #verification #LSP #AI-review #task-hierarchy

Ready to run

npx skills add https://github.com/foundry-works/claude-foundry --skill foundry-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: foundry-spec
Source: https://github.com/foundry-works/claude-foundry/tree/main/skills/foundry-spec
Command: npx skills add https://github.com/foundry-works/claude-foundry --skill foundry-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires , and includes references (resource) components.

What problem does it solve?

This Skill defines and enforces a plan-first development workflow by generating structured specifications before coding.

Core Features & Use Cases

Analyze codebase structure using Explore agents and LSP
Design phased implementation approaches
Create JSON specifications with task hierarchies
Define verification steps for each phase
Automatic AI review of specifications
Apply review feedback as modifications
Validate and auto-fix specifications
Integrate with plan-review and fidelity checks for assurance

Quick Start

To begin, create a markdown plan in specs/.plans, run the AI review, obtain explicit approval, then convert the plan to a JSON spec using the MCP tools, and finally apply phase templates or bulk phase adds to implement.

Frequently Asked Questions about foundry-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate structured specifications before coding a complex feature?▼

To generate structured specifications before coding, you create a markdown plan in a designated plans directory, run an AI review, and convert the approved plan into a JSON spec with task hierarchies and verification steps.

What is spec-driven development and how does it enforce a plan-first workflow?▼

Spec-driven development enforces a plan-first workflow by creating structured JSON specifications before implementation, using task hierarchies and verification steps to guide coding and validate adherence to the plan.

Can I analyze my existing codebase structure before designing a phased implementation?▼

You can analyze your existing codebase structure before designing a phased implementation by using Explore agents and Language Server Protocol features to inform the specification generation.

How do I validate and auto-fix specifications after applying AI review modifications?▼

To validate and auto-fix specifications after applying AI review modifications, the workflow integrates fidelity checks to ensure ongoing adherence and automatically corrects structural issues within the JSON spec.

Does this spec generation workflow support complex refactors and API designs?▼

This spec generation workflow supports complex refactors and API designs by analyzing the codebase, designing phased implementation approaches, and defining specific verification steps for each development phase.

When should I not use a plan-first specification approach for my development task?▼

You should avoid a plan-first specification approach for simple, linear tasks where the overhead of creating JSON specs and task hierarchies outweighs the benefit of automated AI review and phased verification.