fluid-vs-tricky

SKILLWorkflowcommunity
v0.0.0tedgoldsteinMITUpdated 3mo agoSource →

Build order under uncertainty. Two regimes, two strategies. When requirements and design are *fluid* — still being shaped by what you discover building — build the GUI and the foundation simultaneously, in feedback with each other; the GUI surfaces gaps the foundation didn't anticipate, and the foun

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
3mo agoLast update
Skill
Authortedgoldstein
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

Build order under uncertainty. Two regimes, two strategies. When requirements and design are *fluid* — still being shaped by what you discover building — build the GUI and the foundation simultaneously, in feedback with each other; the GUI surfaces gaps the foundation didn't anticipate, and the foundation forces concrete decisions the GUI was hiding. When the going gets *tricky* — when the layer y

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.