Getting Started with Origin Foundry
Set up Claude Code (local or web) or Devin to work on specs. Both run the same Foundry phases from the same files — pick whichever fits your workflow.
Using Claude Code (Local)
1. Install Claude Code
npm install -g @anthropic-ai/claude-code2. Clone the repo
git clone git@github.com:darwin-homes/origin-foundry.git && cd origin-foundry3. Initialize submodules (backend + frontend codebases)
git submodule update --init --recursive4. Open Claude Code
claudeWorking on a spec
Check out your spec branch:
git checkout spec/your-feature-slugRun the spec command:
/update-spec your-feature-slugCC handles the rest — detects the phase, walks you through it step by step.
Works with any CLI that supports Claude Code: Terminal, Cursor, Conductor, etc.
Using Claude Code (Web)
1. Setup
- Go to claude.ai and open a project
- Connect the origin-foundry repository
- Note: submodules (darwin/, client/) need separate access for codebase-grounded phases
2. Working on a spec
- Tell CC which spec to work on:
/update-spec your-feature-slug - CC will check out the right branch and detect the phase automatically
Using Devin
Devin runs the same Foundry phases as Claude Code — it reads AGENTS.md and the phase files from the repo. Nothing is duplicated into Devin; just point a session at the repo.
Option A — paste a prompt into a new Devin session
Run the Origin Foundry <phase> phase for spec <slug>. Clone darwin-homes/origin-foundry, run bash scripts/setup-codebase.sh, then read AGENTS.md and .claude/commands/update-spec.md and follow them; tool mapping in .claude/rules/agent-portability.md. Open a PR on spec/<slug> — do not change the phase: frontmatter field.Option B — from the CLI
DEVIN_API_KEY=cog_... scripts/devin/run-phase.sh your-feature-slug eng-constraintsEvery phase runs on either tool
As of 2026-06-30 the Devin org has the full official Paper MCP, so design-flows (Paper authoring + extraction) runs on Devin too — validated against a Claude-Code reference for token fidelity and craft. A designer in the loop is still recommended for that phase regardless of tool.
Phase Flow
| Phase | What CC does | Output |
|---|---|---|
| draft-refine | Interviews you, writes spec, then refines requirements and ACs in the same session | spec.md |
| eng-constraints | Investigates codebase constraints | enrichment/eng.constraints.md |
| design-flows | Designs UX flows and states | enrichment/design.flows.md |
| eng-tech-requirements | Writes technical requirements | enrichment/eng.tech-requirements/ (folder) |
| product-tracking | Specifies Segment tracking events | enrichment/product.tracking.md |
| review | Multi-domain review | comments/*.comments.md |
| final-sign-off | Merge readiness gate | comments/*.comments.md |