Open PRDs
What would you build if you believed it would work?
Building is the fastest way to break a vicious cycle. Not thinking about building. Not planning to build. Building. The feedback from making something real changes the picture in your head faster than any amount of reflection.
The Process
This repo is the specification layer. The engineering repo is the execution layer. The team that builds it never validates it.
DREAM REPO (this) ENGINEERING REPO (stackmates)
───────────────── ─────────────────────────────
1. Write PRD spec → RFP → 2. Architecture + build
3. Ship feature
4. Commission (validate) ← DELIVERY ← "Ready for inspection"
Agent reads spec
Agent opens browser
Agent checks features,
functions, outcomes
against PRD criteria
5. Pass / Fail + evidence
| Stage | Where | What Happens |
|---|---|---|
| Spec | Here — /open-prds/ | Define features, functions, outcomes, success criteria |
| Methodology | Here — /docs/products/ | JTBD, Shape Up, Flow Engineering, Type-First |
| Architecture | Engineering repo | DB plans, schemas, service boundaries, implementation |
| Build | Engineering repo | Code, tests, deployment |
| Commission | Here — PRD commissioning table | Independent verification against spec |
Why Separate
In factory engineering, the team that builds a system is never the team that commissions it. The builder knows what they intended. The commissioner checks what actually shipped. Independent verification catches what good intentions miss.
A seed phrase got deleted because nobody independently verified the destructive operation against a safety spec. The spec didn't exist. The verification didn't happen. The Sui Wallet PRD exists so that won't happen again.
What Lives Where
| This Repo (Dream) | Engineering Repo (Build) |
|---|---|
| PRD specs with success criteria | Architecture docs, DB schemas |
| Domain analysis and context | Implementation plans |
| Best practice methodology | Code, tests, deployment |
| Commissioning verification | Build state reporting |
| 1,200+ pages of linked domain knowledge | Feature branches and PRs |
PRDs here link into /docs/ for depth — standards, product design, JTBD, industry analysis. A PRD in the engineering repo can't access this context. A PRD here can't access the codebase. Each repo does what it's good at.
Open PRDs
Active
| Venture | PRD | Status | What It Trains |
|---|---|---|---|
| stackmates | Sui Wallet Safety Patterns | Spec complete | Move, wallet UX, cross-chain safety |
| dreamineering | Prompt Deck | Spec + prototype | Alignment instrument, Tight Five as product |
| stackmates | Sales CRM & RFP | Build in progress | Vertical CRM, RFP auto-fill, JTBD demand-driven sales |
Backlog
| Venture | PRD | Difficulty | What It Trains |
|---|---|---|---|
| betterpractice | Sleep protocol content page | Starter | Research, writing, validation |
| betterpractice | Morning intention practice | Starter | Practice design, measurement |
| betterpractice | Optimism daily protocol tracker | Starter | Product design, feedback loops |
| stackmates | Builder onboarding flow | Medium | UX, empathy, systems thinking |
| prettymint | Minting page MVP | Medium | Frontend, crypto, design |
| berleytrails | Trail recommendation engine | Advanced | Data, AI, product |
| dreamineering | Mental model search | Advanced | Knowledge architecture, AI |
PRD Standard
Each PRD documents features, functions, and required outcomes. The engineering team builds against the spec. Validation checks the outcomes, not the code.
| PRD Section | What It Defines | Who Uses It |
|---|---|---|
| The Job | What progress the user is making | Engineering — to understand intent |
| Patterns / Features | What gets built | Engineering — the RFP |
| Success Criteria | How to verify it works | Commissioning — the checklist |
| Commissioning Table | Component-by-component status | Both — shared progress tracker |
| Context Links | Domain knowledge that grounds decisions | Engineering — to understand why |
The Knowledge Stack
Every PRD follows the Knowledge Stack:
| Stage | What It Is | Example |
|---|---|---|
| Pain | Real problem, observed | Seed phrase deleted, $10K lost |
| Protocol | Specific rules that prevent it | Five safety patterns |
| Standard | Proven across contexts | Chain-agnostic principles any wallet can adopt |
| Platform | Shared infrastructure | Open components across ventures |
The Displacement
Millions of people are losing jobs that defined their identity. The intention vacuum opens. Negative thought patterns fill it — permanent, personal, pervasive.
The antidote isn't advice. It's action with feedback.
| The Problem | The Bridge | The Training |
|---|---|---|
| Lost job, lost identity | Pick a PRD, join a team | Building restores agency |
| Isolation compounds | Shared intention coordinates | Collective luck emerges |
| "Nothing works" | Ship something, measure | Evidence replaces belief |
| The loop spirals down | The loop spirals up | Optimism compounds |
This is the pit of success. You don't climb to prove yourself. You fall in and find your place.
Starting Today
- Pick a PRD that pulls you — Wallet Safety or Prompt Deck if you want a challenge, a Starter from the backlog if you want to ease in
- Read the spec — understand the job, the patterns, the success criteria
- Build — follow the spec, ship something
- Verify — does what shipped match what was specified?
- Feed back — update the commissioning table, update the PRD with learnings
Not positive thinking. Positive doing. Optimism is a muscle. Building is the gym.
Context
- Products — Best practice methodology for what we build
- Jobs To Be Done — Demand validation framework
- Flow Engineering — Maps that produce code artifacts
- Standards — Where safety patterns graduate to
- Mycelium Ventures — The ventures that need builders
- Business Flow — Idea → Strategy → Operations → Growth