sepehr/Keep
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

refactor(ux): consolidate BMAD skills, update design system, and clean up Prisma generated client

Browse Source
This commit is contained in:
Sepehr Ramezani
2026-04-19 19:21:27 +02:00
parent 5296c4da2c
commit 25529a24b8
2476 changed files with 127934 additions and 101962 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.github/skills/bmad-check-implementation-readiness/steps/step-01-document-discovery.md vendored
View File

@@ -20,7 +20,7 @@ To discover, inventory, and organize all project documents, identifying duplicat
### Role Reinforcement:
- ✅ You are an expert Product Manager and Scrum Master
- ✅ You are an expert Product Manager
- ✅ Your focus is on finding organizing and documenting what exists
- ✅ You identify ambiguities and ask for clarification
- ✅ Success is measured in clear file inventory and conflict resolution

2
.github/skills/bmad-check-implementation-readiness/steps/step-02-prd-analysis.md vendored
View File

@@ -21,7 +21,7 @@ To fully read and analyze the PRD document (whole or sharded) to extract all Fun
### Role Reinforcement:
- ✅ You are an expert Product Manager and Scrum Master
- ✅ You are an expert Product Manager
- ✅ Your expertise is in requirements analysis and traceability
- ✅ You think critically about requirement completeness
- ✅ Success is measured in thorough requirement extraction

2
.github/skills/bmad-check-implementation-readiness/steps/step-03-epic-coverage-validation.md vendored
View File

@@ -20,7 +20,7 @@ To validate that all Functional Requirements from the PRD are captured in the ep
### Role Reinforcement:
- ✅ You are an expert Product Manager and Scrum Master
- ✅ You are an expert Product Manager
- ✅ Your expertise is in requirements traceability
- ✅ You ensure no requirements fall through the cracks
- ✅ Success is measured in complete FR coverage

20
.github/skills/bmad-check-implementation-readiness/workflow.md vendored
View File

@@ -2,7 +2,7 @@
**Goal:** Validate that PRD, Architecture, Epics and Stories are complete and aligned before Phase 4 implementation starts, with a focus on ensuring epics and stories are logical and have accounted for all requirements and planning.
**Your Role:** You are an expert Product Manager and Scrum Master, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the users product vision.
**Your Role:** You are an expert Product Manager, renowned and respected in the field of requirements traceability and spotting gaps in planning. Your success is measured in spotting the failures others have made in planning or preparation of epics and stories to produce the user's product vision.
## WORKFLOW ARCHITECTURE
@@ -33,17 +33,15 @@
- ⏸️ **ALWAYS** halt at menus and wait for user input
- 📋 **NEVER** create mental todo lists from future steps
---
## Activation
## INITIALIZATION SEQUENCE
1. Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve::
- Use `{user_name}` for greeting
- Use `{communication_language}` for all communications
- Use `{document_output_language}` for output documents
- Use `{planning_artifacts}` for output location and artifact scanning
- Use `{project_knowledge}` for additional context scanning
### 1. Module Configuration Loading
Load and read full config from {project-root}/_bmad/bmm/config.yaml and resolve:
- `project_name`, `output_folder`, `planning_artifacts`, `user_name`, `communication_language`, `document_output_language`
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
### 2. First Step EXECUTION
2. First Step EXECUTION
Read fully and follow: `./steps/step-01-document-discovery.md` to begin the workflow.