docs: formalize Product Requirements Document workflow

- Add PRD workflow to systemPatterns.md as a standardized development process
- Update .clinerules with instructions to follow the PRD workflow
- Update activeContext.md and progress.md to reference the new workflow

This formalizes the process we used for implementing the server readiness probe feature.

Tool: gitpod/catfood.gitpod.cloud

Author: geropl

memory-bank/.clinerules

@@ -26,6 +26,15 @@ This file captures important patterns, preferences, and project intelligence tha
 
 ## Development Workflow
 
+- **Feature Development Process**:
+  - Follow the Product Requirements Document (PRD) workflow documented in systemPatterns.md under "Development Workflows"
+  - Create PRD documents in the `prd/` directory with naming convention `NNN-featurename.md`
+  - Include standard sections: Overview, Background, Requirements, Implementation Details, Testing, Deployment Considerations, Future Improvements
+  - Use Plan Mode for requirements gathering and planning
+  - Use Act Mode for implementation and documentation updates
+  - Always update memory bank with new knowledge gained during implementation
+  - Reference the PRD in commit messages and documentation
+
 - **Build Approaches**:
   - **In-tree builds** (primary for local development):
     - TypeScript components: Use `yarn` commands defined in package.json

memory-bank/activeContext.md

@@ -10,10 +10,13 @@ Key areas of focus include:
 2. **Component Documentation**: Creating detailed documentation for each component
 3. **Development Workflow**: Understanding how to effectively develop and test changes
 4. **Documentation**: Maintaining a comprehensive memory bank for future reference
+5. **Standardized Workflows**: Establishing and documenting standardized workflows for development activities
 
 ## Recent Changes
 
 - Created the initial memory bank structure with core files
+- Established standardized workflows for development activities:
+  - Product Requirements Document (PRD) workflow for feature development
 - Added a components subdirectory to the memory bank
 - Created detailed documentation for key components:
   - blobserve: Service that provides static assets from OCI images

memory-bank/progress.md

@@ -217,6 +217,10 @@ No specific blockers or dependencies have been identified yet. This section will
     - Documented server architecture patterns and dependency injection
     - Added information about Kubernetes deployment configuration
     - Documented feature flag implementation for readiness probe
+  - Established standardized development workflows:
+    - Created `workflows.md` to document standardized development processes
+    - Documented the Product Requirements Document (PRD) workflow
+    - Updated `activeContext.md` to reference the new workflows
 
 ## Next Evaluation Point
 

memory-bank/systemPatterns.md

@@ -131,3 +131,17 @@ Workspaces are treated as immutable, with changes to configuration resulting in
 7. **Leeway Build System**: Custom build system for managing the complex dependencies between components.
 
 8. **Kubernetes Deployment Configuration**: All code that defines Kubernetes objects for deployable components lives in `install/installer`. This centralized approach ensures consistent deployment patterns across all components.
+
+## Development Workflows
+
+### Product Requirements Document (PRD) Workflow
+Gitpod uses a structured PRD workflow for feature development to ensure proper planning, documentation, and implementation:
+
+1. **Requirements Gathering** (Plan Mode): Understand the problem, explore existing components, gather information
+2. **PRD Creation** (Plan Mode): Create a detailed document in `prd/` with standardized sections
+3. **Implementation Planning** (Plan Mode): Identify files to modify and plan the approach
+4. **Implementation** (Act Mode): Create/modify necessary files following the plan
+5. **Documentation Update** (Act Mode): Update memory bank with new knowledge
+6. **Verification**: Ensure implementation meets requirements and documentation is complete
+
+This workflow ensures thorough planning, clear documentation, and knowledge preservation for all feature development.