Your PRD. Our harness.
Your TUI, now autonomous.
Let's build your MVP. FAST.
Drop your PRD. dsf audits it, composes a Claude-Code harness — disciplines, sub-agents, MCP, CI gates — and opens the PR on your repo. You merge. You build.
AI coding tools without discipline produce expensive demos.
Claude Code, Cursor, Codex write functions in seconds. Turning that into something that ships — with the disciplines, the gates, the specs, the MCP wiring — is where projects stall. dsf is the missing layer between I have a PRD and the harness is building it.
Five steps. No babysitting.
A multi-step Cloudflare Workflow runs the pipeline end to end. You stay in your editor; Atlas streams what dsf is doing.
┌────────────────────┐ │ PRD.md │ │ markdown spec │ └────────────────────┘
01PRDYou write the brief.
You work with Claude Code (or Claude Projects) to produce a thorough PRD from our well-formed template that establishes the full design, architecture, requirements, and specifications.
┌────────────────────┐ │ audit │ │ clean·pause·guide │ └────────────────────┘
02auditdsf checks readiness.
Our system audits the PRD for completeness. dsf names any gaps and cites the section that flagged them for recursive editing until readiness.
┌────────────────────┐ │ match │ │ seed harness │ └────────────────────┘
03matchdsf picks the environment.
dsf identifies the right stack and seed harness for your project, drawn from a corpus that tracks current best practice.
┌────────────────────┐ │ compose │ │ disciplines · mcp │ │ agents · ci gates │ └────────────────────┘
04composedsf builds the factory.
A tailored Claude Code harness — disciplines, sub-agents, MCP servers, hooks, CI gates, slash commands, status line — composed specifically for your Claude Code stack. dsf finalizes any details with you before you hit go.
┌────────────────────┐ │ emit → PR │ │ github · merge it │ └────────────────────┘
05emitClaude Code gets to work.
dsf delivers the finished harness to your repo. You review and merge, and Claude Code starts building inside it — opening its own PRs as it goes. Atlas streams progress.
A harness, not a wrapper.
Everything below ships in the pull request dsf opens against your repo. Nothing is a hosted black box. The harness is yours.
Claude-Code-native harness.
Hooks, sub-agents, slash commands, settings, status line. Composed against your stack — not a generic template.
Disciplines wired in.
TDD, mutation testing, coverage gates, dependency rules, performance budgets. All from the manifesto. Enforced in CI.
MCP servers preconfigured.
Linear, GitHub, Slack, Telegram, Notion. Declared in the harness, ready to run.
Corpus stays current.
dsf tracks IDE releases and community signal. Your harness does not age.
Atlas dashboard.
Every step, every verdict, every PR. No Linear seat required.
UI via claude.ai/design.
dsf hands UI tasks to claude.ai/design and feeds the results back into the harness.
One price. Per project.
Pay when you start a project. The harness it produces is yours to keep.
- →Full pipeline — audit → compose → emit
- →Atlas dashboard included
- →Continuous corpus refresh
- →GitHub + Anthropic API integration
- →No Linear seat required
- →The harness is yours — it lives in your repo
Claude Code subscription you bring. Anthropic API charges pass through at cost.
Multi-project bundles on the roadmap.
Questions worth answering.
Do I need Claude Code?
Where does my code live?
What does dsf actually run?
Is this for enterprise?
What about my data?
Do you sign NDAs?
Can I obtain the projects / issues / tickets?
When is general availability?
Request
private beta
access.
We're onboarding a small first cohort. Tell us about your project; we'll reach out within a week.