Dependency Map
What must exist before this works?
Internal Dependencies
| This PRD Needs | From | Status | Risk |
|---|---|---|---|
| Form atoms (Input, Select, Textarea, Checkbox) | @stackmates/ui lib | Built, L:R 1.4:1 | Low — well-composed |
| FormShell organism | @stackmates/ui lib | Built (only organism) | Medium — only 1 organism exists |
| TanStack Form integration | @stackmates/ui lib | Built, documented | Low |
| Anti-pattern documentation | stackmat.es /patterns/forms/anti-patterns | Built | Low — rare and valuable |
| Accessibility annotations | Form atom stories | Built | Low — thorough |
External Dependencies
| This PRD Needs | From | Status | Risk |
|---|---|---|---|
Tailwind v4.1 with @theme bridge | stackmat.es infra | Working | Low — tokens healthy |
| Docusaurus MDX build | stackmat.es infra | Working | Low |
| shadcn/ui primitives | External | Stable | Low |
Downstream Consumers
| Consumer | Needs | Status |
|---|---|---|
| Meetings PRD (backburner) | Proven form patterns for agenda builder | Blocked until DS-05 proves composition |
| Any future form-heavy feature | Standard process + shipping gate | Blocked until DS-02 + DS-03 exist |
| Venture evaluators | Working examples that prove the team is real | Currently seeing stubs and 404s |
Relationship Declarations
| PRD | Relationship | Direction |
|---|---|---|
| Meetings | depends-on | Meetings consumes form patterns this PRD proves |
| Prompt Deck | Complementary | Design system already showcases PromptDeck |
| Sales CRM | Complementary | CRM pattern rewrite (DS-04) improves CRM form showcase |
Kill Dependencies
If MeetingAgenda form can't be built from existing lib atoms without _components/ local directory, the lib has fundamental gaps. Stop this PRD and fill lib first.
If CRM pattern rewrite reveals >3 missing lib components, prioritize lib atom work over meeting feature.
Questions
Which dependency in the design system app map represents the highest systemic risk — and is there a path to eliminating it?
- If the most critical dependency failed, which capabilities would cascade and which could operate independently?
- Are any dependencies in this map bidirectional — and does that create circular risk that should be decomposed?
- Which dependency was added because of a constraint that no longer exists?