English | 中文

Foundry

Forge software from idea to delivery.

An AI-native, spec-driven development suite for coding agents — covering the full lifecycle: greenfield projects, brownfield takeovers, and continuous feature delivery.

Website · Installation · The Three Skills

---

What is Foundry?

Foundry is a set of three reusable Agent Skills that turn an AI coding agent into a disciplined engineering workflow. Instead of jumping straight into code, Foundry enforces:

• Macro design before coding — direction, boundaries, rules, and constraints first.
• Spec-driven development — the Spec is the source of truth for what is correct.
• Test design before implementation — define how correctness is proven, then build.
• UX before UI — user goals and flows before pixels.
• Gated transitions — SPEC READY → UI READY → TEST DESIGN READY → DONE.
• Evidence over assumptions — observed, documented, confirmed, inferred — never silently guessed.
• Controlled design change — L1/L2/L3 impact levels with explicit decision authority.

The Three Skills

Skill	Phase	Role
coding-start	Greenfield · 0 → 1	Discovery interviews, macro design, project docs, Feature Map, DRAFT Specs
project-onboard	Brownfield · unknown → understood	Baseline verification, architecture reconstruction, AS-IS docs, Feature Inventory
feature-dev	Feature · 1 → N	Spec refinement, UX/UI gates, test design, plan, coding, review, delivery

New idea ──▶ coding-start ──▶ feature-dev ──▶ feature-dev ──▶ ...
Existing repo ──▶ project-onboard ──▶ feature-dev ──▶ feature-dev ──▶ ...

Each skill has explicit STOP conditions: no silent business code, no unauthorized writes, no batch Issue creation, no mass refactoring.

Installation

Foundry follows the standard Agent Skills format (SKILL.md + references/ + assets/). Copy the three folders into your agent's skills directory.

OpenCode / Claude-style agents (auto-discovered):

git clone https://github.com/MaoyuanYang/foundry.git
cp -r foundry/skills/coding-start      ~/.agents/skills/
cp -r foundry/skills/project-onboard   ~/.agents/skills/
cp -r foundry/skills/feature-dev       ~/.agents/skills/

Then restart your agent. Verify discovery with opencode debug skill (you should see all three skills listed).

Quick Start

Start a new project:

"Initialize a new greenfield project: a community local-services platform."

coding-start interviews you round by round, runs the Macro Readiness Gate, and produces README, AGENTS.md, docs/*, specs/ROADMAP.md, and DRAFT Specs — then stops with one selected NEXT feature.

Take over an existing repo:

"Take over this repository and build a durable AS-IS baseline."

project-onboard surveys the repo, verifies the baseline, reconstructs architecture and features, and produces AS-IS documentation — then stops with a recommended next item.

Develop a feature:

"Implement feature F001 according to the workflow."

feature-dev drives the full lifecycle: SPEC READY → UI READY (if UI) → TEST DESIGN READY → Plan → Coding → Review → Documentation Sync → delivery.

Design Principles

1. Macro design before coding — but no Big Design Up Front.
2. All Specs can be drafted at once; only the selected one is deepened.
3. The Spec defines correctness; the Issue tracks progress; the PR records changes; the ADR records why.
4. Critical requirements must be verifiable before coding starts.
5. Test behavior, not implementation details.
6. Existing code is evidence, not the standard. Existing UI is evidence, not the design system.
7. Code must not stay ahead of docs.
8. Skills hold the process; AGENTS.md holds the project rules.

Language Policy

Foundry defaults to English for all engineering artifacts (documentation_language = en, engineering_language = en). User-facing product copy follows product requirements. Existing repositories preserve their established language; overrides require explicit decision-authority approval.

Documentation

Full documentation (English & 中文): https://maoyuanyang.github.io/foundry/

License

MIT © MaoyuanYang