haytham
Lifecycle control plane for AI-built products. Takes a startup idea and produces a validated, specified, architected, implementation-ready s
Open source Open in the app JSON README (API)
About
Lifecycle control plane for AI-built products. Takes a startup idea and produces a validated, specified, architected, implementation-ready system through four phases: validate the idea with market and competitor research, define MVP scope and capabilities, make architecture and build-vs-buy decisions, and generate implementation-ready OpenSpec files. Orchestrates 10 specialist agents that build a traceable reasoning graph from founder intent to production specs. Every requirement traces to a capability, every capability traces to a user need.
Details
- Kind
- Plugins
- Topic
- AI, RAG & memory
- Publisher
- arslan70
- Origin
- marketplace
- Category
- ferramentas
- Stars
- 13
- Forks
- 1
- Last push
- 2026-07-27T18:50:41Z
- Repository state
- ativo
- Language
- Python
- License
- MIT
- Added
- 2026-08-30 01:48:58
- Updated
- 2026-08-30 01:48:58
- Origin id
arslan70/haytham/haytham
README
# Haytham
[](LICENSE)
> **Status (2026-07):** Haytham is now a personal tool. It is no longer seeking users, contributors, or marketplace adoption. The full product ambition (lifecycle control plane, EVOLUTION and SENTIENCE milestones, telemetry loop) is preserved at the git tag `v0.3.27-full` and in [docs/](docs/). What remains is the part that earns its keep: a fast idea-to-MVP pipeline.
Haytham turns a raw startup idea into an implementation-ready specification inside Claude Code. Run one command. Get market research, a GO/NO-GO verdict, MVP scope, architecture decisions, and an [OpenSpec](https://github.com/Fission-AI/OpenSpec) ready to hand to a coding agent. Every requirement traces to a capability. Every capability traces to a validated need.
## Install
```
/plugin marketplace add arslan70/haytham
/plugin install haytham@haytham
```
No Python. No API keys. No environment variables.
## Try it
```
/haytham "a gym community leaderboard with anonymous handles"
```
Takes ~20 minutes. You'll be asked for approval at each phase boundary. You can stop, correct, or redirect at any point.
## What you get
Four phases, each answering one question. You approve before each phase advances.
```
Phase 1: Should this be built?
→ Market research, competitor analysis, risk scoring
→ GO / NO-GO / PIVOT verdict backed by evidence
→ If it says NO-GO, it tells you why. That's the point.
Phase 2: What exactly?
→ MVP scope with clear in/out boundaries
→ Capability model with full traceability
→ System traits (auth, payments, real-time, etc.)
Phase 3: How to build it?
→ Build-vs-buy analysis per capability
→ Architecture decisions linked to capabilities
→ Cost and effort estimates
Phase 4: What are the specs?
→ OpenSpec with SHALL requirements
→ Gherkin scenarios for acceptance testing
→ Ready to hand to Claude Code or any coding agent
```
## See example output
The [`examples/`](examples/) directory contains complete outputs from real Haytham runs across different idea types:
| Example | Type | Verdict |
|---------|------|---------|
| [Gym Leaderboard](examples/gym-leaderboard/) | B2C consumer app | GO (high risk) |
| [Git Changelog CLI](examples/git-changelog-cli/) | Developer tool | GO |
| [Invoice Reconciler](examples/invoice-reconciler/) | B2B SaaS | PIVOT |
## Output structure
All output lives in `.haytham/session/`:
```
.haytham/session/
├── phase-1-why/
│ ├── idea-analysis.md # Problem analysis, segments, UVP
│ ├── concept-anchor.json # Invariants that prevent idea drift
│ ├── market-research.md # TAM/SAM/SOM, trends, risks
│ ├── competitor-research.md # Who else is doing this
│ ├── research-brief.md # Neutral summary (no scores)
│ └── validation-report.md # GO/NO-GO/PIVOT with evidence
├── phase-2-what/
│ ├── mvp-scope.md # What's in, what's out, core flows
│ ├── capabilities.json # Functional + non-functional capabilities
│ ├── system-traits.json # Auth, deployment, data layer, etc.
│ └── gate-summary.md # What you approve at Gate 2, in prose
├── phase-3-how/
│ ├── build-buy.json # BUILD/BUY/HYBRID per capability
│ ├── architecture-decisions.json
│ ├── research-directives.json # What to investigate before coding
│ └── gate-summary.md # What you approve at Gate 3, in prose
└── phase-4-specs/
└── openspec/
├── config.yaml
├── project.md
└── specs/
├── domain-name/spec.md
└── cross-cutting/spec.md
```
## How it works
Ten specialist agents across four phases. Market research agents run web searches. The report synthesizer weighs evidence and produces an honest verdict. If risks are high, it says so. If the idea doesn't hold up, it recommends NO-GO.
Concept anchors (extracted in Phase 1) are passed unchanged to every downstream agent, preventing the "telephone game" where your specific idea gets genericized into something bland.
Read more: [How It Works](https://arslan70.github.io/haytham/how-it-works/) | [System Evolution](https://arslan70.github.io/haytham/system-evolution/)
## Commands
| Command | Description |
|---------|-------------|
| `/haytham "idea"` | Run all 4 phases end-to-end |
| `/haytham:validate "idea or URL"` | Phase 1: Market research and GO/PIVOT/NO-GO verdict |
| `/haytham:specify` | Phase 2: MVP scope and capability model |
| `/haytham:design` | Phase 3: Build/buy analysis and architecture decisions |
| `/haytham:plan` | Phase 4: Generate implementation-ready OpenSpec |
| `/haytham:build` | Set up a new project from Phase 4 specs |
`/haytham:validate` accepts Reddit post and GitHub repo URLs. Use `--batch` to skip interactive gates (the NO-GO halt still applies).
## License
[MIT License](LICENSE)