@agile-vibe-coding/avc 0.2.3 → 0.3.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/cli/agents/agent-selector.md +23 -0
- package/cli/agents/code-implementer.md +117 -0
- package/cli/agents/code-validator.md +80 -0
- package/cli/agents/context-reviewer-epic.md +101 -0
- package/cli/agents/context-reviewer-story.md +92 -0
- package/cli/agents/context-writer-epic.md +145 -0
- package/cli/agents/context-writer-story.md +111 -0
- package/cli/agents/doc-writer-epic.md +42 -0
- package/cli/agents/doc-writer-story.md +43 -0
- package/cli/agents/duplicate-detector.md +110 -0
- package/cli/agents/epic-story-decomposer.md +318 -39
- package/cli/agents/mission-scope-generator.md +68 -4
- package/cli/agents/mission-scope-validator.md +40 -6
- package/cli/agents/project-context-extractor.md +21 -6
- package/cli/agents/scaffolding-generator.md +99 -0
- package/cli/agents/seed-validator.md +71 -0
- package/cli/agents/story-scope-reviewer.md +147 -0
- package/cli/agents/story-splitter.md +83 -0
- package/cli/agents/validator-documentation.json +31 -0
- package/cli/agents/validator-documentation.md +3 -1
- package/cli/api-reference-tool.js +368 -0
- package/cli/checks/catalog.json +76 -0
- package/cli/checks/code/quality.json +26 -0
- package/cli/checks/code/testing.json +14 -0
- package/cli/checks/code/traceability.json +26 -0
- package/cli/checks/cross-refs/epic.json +171 -0
- package/cli/checks/cross-refs/story.json +149 -0
- package/cli/checks/epic/api.json +114 -0
- package/cli/checks/epic/backend.json +126 -0
- package/cli/checks/epic/cloud.json +126 -0
- package/cli/checks/epic/data.json +102 -0
- package/cli/checks/epic/database.json +114 -0
- package/cli/checks/epic/developer.json +182 -0
- package/cli/checks/epic/devops.json +174 -0
- package/cli/checks/epic/frontend.json +162 -0
- package/cli/checks/epic/mobile.json +102 -0
- package/cli/checks/epic/qa.json +90 -0
- package/cli/checks/epic/security.json +184 -0
- package/cli/checks/epic/solution-architect.json +192 -0
- package/cli/checks/epic/test-architect.json +90 -0
- package/cli/checks/epic/ui.json +102 -0
- package/cli/checks/epic/ux.json +90 -0
- package/cli/checks/fixes/epic-fix-template.md +10 -0
- package/cli/checks/fixes/story-fix-template.md +10 -0
- package/cli/checks/story/api.json +186 -0
- package/cli/checks/story/backend.json +102 -0
- package/cli/checks/story/cloud.json +102 -0
- package/cli/checks/story/data.json +210 -0
- package/cli/checks/story/database.json +102 -0
- package/cli/checks/story/developer.json +168 -0
- package/cli/checks/story/devops.json +102 -0
- package/cli/checks/story/frontend.json +174 -0
- package/cli/checks/story/mobile.json +102 -0
- package/cli/checks/story/qa.json +210 -0
- package/cli/checks/story/security.json +198 -0
- package/cli/checks/story/solution-architect.json +230 -0
- package/cli/checks/story/test-architect.json +210 -0
- package/cli/checks/story/ui.json +102 -0
- package/cli/checks/story/ux.json +102 -0
- package/cli/coding-order.js +401 -0
- package/cli/dependency-checker.js +72 -0
- package/cli/epic-story-validator.js +284 -799
- package/cli/index.js +0 -0
- package/cli/init-model-config.js +17 -10
- package/cli/init.js +514 -92
- package/cli/kanban-server-manager.js +1 -2
- package/cli/llm-claude.js +98 -31
- package/cli/llm-gemini.js +29 -5
- package/cli/llm-local.js +493 -0
- package/cli/llm-openai.js +262 -41
- package/cli/llm-provider.js +147 -8
- package/cli/llm-token-limits.js +113 -4
- package/cli/llm-verifier.js +209 -1
- package/cli/llm-xiaomi.js +143 -0
- package/cli/message-constants.js +3 -12
- package/cli/messaging-api.js +6 -12
- package/cli/micro-check-fixer.js +335 -0
- package/cli/micro-check-runner.js +449 -0
- package/cli/micro-check-scorer.js +148 -0
- package/cli/micro-check-validator.js +538 -0
- package/cli/model-pricing.js +23 -0
- package/cli/model-selector.js +3 -2
- package/cli/prompt-logger.js +57 -0
- package/cli/repl-ink.js +106 -346
- package/cli/repl-old.js +1 -2
- package/cli/seed-processor.js +194 -24
- package/cli/sprint-planning-processor.js +2638 -289
- package/cli/template-processor.js +50 -3
- package/cli/token-tracker.js +50 -23
- package/cli/tools/generate-story-validators.js +1 -1
- package/cli/validation-router.js +70 -8
- package/cli/worktree-runner.js +654 -0
- package/kanban/client/dist/assets/index-D_KC5EQT.css +1 -0
- package/kanban/client/dist/assets/index-DjY5zqW7.js +351 -0
- package/kanban/client/dist/index.html +2 -2
- package/kanban/client/src/App.jsx +43 -14
- package/kanban/client/src/components/ceremony/AskArchPopup.jsx +7 -3
- package/kanban/client/src/components/ceremony/AskModelPopup.jsx +23 -10
- package/kanban/client/src/components/ceremony/CeremonyWorkflowModal.jsx +320 -133
- package/kanban/client/src/components/ceremony/ProviderSwitcherButton.jsx +290 -0
- package/kanban/client/src/components/ceremony/SponsorCallModal.jsx +80 -13
- package/kanban/client/src/components/ceremony/SprintPlanningModal.jsx +156 -22
- package/kanban/client/src/components/ceremony/steps/ArchitectureStep.jsx +11 -11
- package/kanban/client/src/components/ceremony/steps/CompleteStep.jsx +3 -21
- package/kanban/client/src/components/ceremony/steps/ReviewAnswersStep.jsx +214 -10
- package/kanban/client/src/components/ceremony/steps/RunningStep.jsx +23 -2
- package/kanban/client/src/components/kanban/CardDetailModal.jsx +97 -10
- package/kanban/client/src/components/kanban/GroupingSelector.jsx +7 -1
- package/kanban/client/src/components/kanban/KanbanCard.jsx +23 -14
- package/kanban/client/src/components/kanban/RefineWorkItemPopup.jsx +9 -14
- package/kanban/client/src/components/kanban/RunButton.jsx +162 -0
- package/kanban/client/src/components/kanban/SeedButton.jsx +176 -0
- package/kanban/client/src/components/settings/AgentsTab.jsx +103 -75
- package/kanban/client/src/components/settings/ApiKeysTab.jsx +31 -2
- package/kanban/client/src/components/settings/CeremonyModelsTab.jsx +9 -2
- package/kanban/client/src/components/settings/CheckEditorPopup.jsx +507 -0
- package/kanban/client/src/components/settings/CostThresholdsTab.jsx +3 -2
- package/kanban/client/src/components/settings/ModelPricingTab.jsx +72 -7
- package/kanban/client/src/components/settings/OpenAIAuthSection.jsx +412 -0
- package/kanban/client/src/components/settings/SettingsModal.jsx +4 -4
- package/kanban/client/src/components/stats/CostModal.jsx +34 -3
- package/kanban/client/src/hooks/useGrouping.js +59 -0
- package/kanban/client/src/lib/api.js +118 -4
- package/kanban/client/src/lib/status-grouping.js +10 -0
- package/kanban/client/src/store/kanbanStore.js +8 -0
- package/kanban/server/index.js +23 -2
- package/kanban/server/routes/ceremony.js +153 -4
- package/kanban/server/routes/costs.js +9 -3
- package/kanban/server/routes/openai-oauth.js +366 -0
- package/kanban/server/routes/settings.js +447 -14
- package/kanban/server/routes/websocket.js +7 -2
- package/kanban/server/routes/work-items.js +141 -1
- package/kanban/server/services/CeremonyService.js +275 -24
- package/kanban/server/services/TaskRunnerService.js +261 -0
- package/kanban/server/workers/run-task-worker.js +121 -0
- package/kanban/server/workers/seed-worker.js +94 -0
- package/kanban/server/workers/sponsor-call-worker.js +14 -6
- package/kanban/server/workers/sprint-planning-worker.js +94 -12
- package/package.json +2 -3
- package/cli/agents/solver-epic-api.json +0 -15
- package/cli/agents/solver-epic-api.md +0 -39
- package/cli/agents/solver-epic-backend.json +0 -15
- package/cli/agents/solver-epic-backend.md +0 -39
- package/cli/agents/solver-epic-cloud.json +0 -15
- package/cli/agents/solver-epic-cloud.md +0 -39
- package/cli/agents/solver-epic-data.json +0 -15
- package/cli/agents/solver-epic-data.md +0 -39
- package/cli/agents/solver-epic-database.json +0 -15
- package/cli/agents/solver-epic-database.md +0 -39
- package/cli/agents/solver-epic-developer.json +0 -15
- package/cli/agents/solver-epic-developer.md +0 -39
- package/cli/agents/solver-epic-devops.json +0 -15
- package/cli/agents/solver-epic-devops.md +0 -39
- package/cli/agents/solver-epic-frontend.json +0 -15
- package/cli/agents/solver-epic-frontend.md +0 -39
- package/cli/agents/solver-epic-mobile.json +0 -15
- package/cli/agents/solver-epic-mobile.md +0 -39
- package/cli/agents/solver-epic-qa.json +0 -15
- package/cli/agents/solver-epic-qa.md +0 -39
- package/cli/agents/solver-epic-security.json +0 -15
- package/cli/agents/solver-epic-security.md +0 -39
- package/cli/agents/solver-epic-solution-architect.json +0 -15
- package/cli/agents/solver-epic-solution-architect.md +0 -39
- package/cli/agents/solver-epic-test-architect.json +0 -15
- package/cli/agents/solver-epic-test-architect.md +0 -39
- package/cli/agents/solver-epic-ui.json +0 -15
- package/cli/agents/solver-epic-ui.md +0 -39
- package/cli/agents/solver-epic-ux.json +0 -15
- package/cli/agents/solver-epic-ux.md +0 -39
- package/cli/agents/solver-story-api.json +0 -15
- package/cli/agents/solver-story-api.md +0 -39
- package/cli/agents/solver-story-backend.json +0 -15
- package/cli/agents/solver-story-backend.md +0 -39
- package/cli/agents/solver-story-cloud.json +0 -15
- package/cli/agents/solver-story-cloud.md +0 -39
- package/cli/agents/solver-story-data.json +0 -15
- package/cli/agents/solver-story-data.md +0 -39
- package/cli/agents/solver-story-database.json +0 -15
- package/cli/agents/solver-story-database.md +0 -39
- package/cli/agents/solver-story-developer.json +0 -15
- package/cli/agents/solver-story-developer.md +0 -39
- package/cli/agents/solver-story-devops.json +0 -15
- package/cli/agents/solver-story-devops.md +0 -39
- package/cli/agents/solver-story-frontend.json +0 -15
- package/cli/agents/solver-story-frontend.md +0 -39
- package/cli/agents/solver-story-mobile.json +0 -15
- package/cli/agents/solver-story-mobile.md +0 -39
- package/cli/agents/solver-story-qa.json +0 -15
- package/cli/agents/solver-story-qa.md +0 -39
- package/cli/agents/solver-story-security.json +0 -15
- package/cli/agents/solver-story-security.md +0 -39
- package/cli/agents/solver-story-solution-architect.json +0 -15
- package/cli/agents/solver-story-solution-architect.md +0 -39
- package/cli/agents/solver-story-test-architect.json +0 -15
- package/cli/agents/solver-story-test-architect.md +0 -39
- package/cli/agents/solver-story-ui.json +0 -15
- package/cli/agents/solver-story-ui.md +0 -39
- package/cli/agents/solver-story-ux.json +0 -15
- package/cli/agents/solver-story-ux.md +0 -39
- package/cli/agents/validator-epic-api.json +0 -93
- package/cli/agents/validator-epic-api.md +0 -137
- package/cli/agents/validator-epic-backend.json +0 -93
- package/cli/agents/validator-epic-backend.md +0 -130
- package/cli/agents/validator-epic-cloud.json +0 -93
- package/cli/agents/validator-epic-cloud.md +0 -137
- package/cli/agents/validator-epic-data.json +0 -93
- package/cli/agents/validator-epic-data.md +0 -130
- package/cli/agents/validator-epic-database.json +0 -93
- package/cli/agents/validator-epic-database.md +0 -137
- package/cli/agents/validator-epic-developer.json +0 -74
- package/cli/agents/validator-epic-developer.md +0 -153
- package/cli/agents/validator-epic-devops.json +0 -74
- package/cli/agents/validator-epic-devops.md +0 -153
- package/cli/agents/validator-epic-frontend.json +0 -74
- package/cli/agents/validator-epic-frontend.md +0 -153
- package/cli/agents/validator-epic-mobile.json +0 -93
- package/cli/agents/validator-epic-mobile.md +0 -130
- package/cli/agents/validator-epic-qa.json +0 -93
- package/cli/agents/validator-epic-qa.md +0 -130
- package/cli/agents/validator-epic-security.json +0 -74
- package/cli/agents/validator-epic-security.md +0 -154
- package/cli/agents/validator-epic-solution-architect.json +0 -74
- package/cli/agents/validator-epic-solution-architect.md +0 -156
- package/cli/agents/validator-epic-test-architect.json +0 -93
- package/cli/agents/validator-epic-test-architect.md +0 -130
- package/cli/agents/validator-epic-ui.json +0 -93
- package/cli/agents/validator-epic-ui.md +0 -130
- package/cli/agents/validator-epic-ux.json +0 -93
- package/cli/agents/validator-epic-ux.md +0 -130
- package/cli/agents/validator-story-api.json +0 -104
- package/cli/agents/validator-story-api.md +0 -152
- package/cli/agents/validator-story-backend.json +0 -104
- package/cli/agents/validator-story-backend.md +0 -152
- package/cli/agents/validator-story-cloud.json +0 -104
- package/cli/agents/validator-story-cloud.md +0 -152
- package/cli/agents/validator-story-data.json +0 -104
- package/cli/agents/validator-story-data.md +0 -152
- package/cli/agents/validator-story-database.json +0 -104
- package/cli/agents/validator-story-database.md +0 -152
- package/cli/agents/validator-story-developer.json +0 -104
- package/cli/agents/validator-story-developer.md +0 -152
- package/cli/agents/validator-story-devops.json +0 -104
- package/cli/agents/validator-story-devops.md +0 -152
- package/cli/agents/validator-story-frontend.json +0 -104
- package/cli/agents/validator-story-frontend.md +0 -152
- package/cli/agents/validator-story-mobile.json +0 -104
- package/cli/agents/validator-story-mobile.md +0 -152
- package/cli/agents/validator-story-qa.json +0 -104
- package/cli/agents/validator-story-qa.md +0 -152
- package/cli/agents/validator-story-security.json +0 -104
- package/cli/agents/validator-story-security.md +0 -152
- package/cli/agents/validator-story-solution-architect.json +0 -104
- package/cli/agents/validator-story-solution-architect.md +0 -152
- package/cli/agents/validator-story-test-architect.json +0 -104
- package/cli/agents/validator-story-test-architect.md +0 -152
- package/cli/agents/validator-story-ui.json +0 -104
- package/cli/agents/validator-story-ui.md +0 -152
- package/cli/agents/validator-story-ux.json +0 -104
- package/cli/agents/validator-story-ux.md +0 -152
- package/kanban/client/dist/assets/index-CiD8PS2e.js +0 -306
- package/kanban/client/dist/assets/index-nLh0m82Q.css +0 -1
|
@@ -1,93 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"agentName": "validator-epic-ui",
|
|
3
|
-
"version": "1.0.0",
|
|
4
|
-
"description": "Verification rules for ui epic validator",
|
|
5
|
-
"requiredFields": [
|
|
6
|
-
"validationStatus",
|
|
7
|
-
"overallScore",
|
|
8
|
-
"issues",
|
|
9
|
-
"strengths",
|
|
10
|
-
"improvementPriorities",
|
|
11
|
-
"readyForStories",
|
|
12
|
-
"domainSpecificNotes"
|
|
13
|
-
],
|
|
14
|
-
"fieldValidation": {
|
|
15
|
-
"validationStatus": {
|
|
16
|
-
"type": "string",
|
|
17
|
-
"allowedValues": [
|
|
18
|
-
"needs-improvement",
|
|
19
|
-
"acceptable",
|
|
20
|
-
"excellent"
|
|
21
|
-
],
|
|
22
|
-
"errorMessage": "validationStatus must be one of: needs-improvement, acceptable, excellent"
|
|
23
|
-
},
|
|
24
|
-
"overallScore": {
|
|
25
|
-
"type": "number",
|
|
26
|
-
"min": 0,
|
|
27
|
-
"max": 100,
|
|
28
|
-
"errorMessage": "overallScore must be between 0 and 100"
|
|
29
|
-
},
|
|
30
|
-
"issues": {
|
|
31
|
-
"type": "array",
|
|
32
|
-
"minLength": 0,
|
|
33
|
-
"itemValidation": {
|
|
34
|
-
"requiredFields": [
|
|
35
|
-
"severity",
|
|
36
|
-
"category",
|
|
37
|
-
"description",
|
|
38
|
-
"suggestion"
|
|
39
|
-
],
|
|
40
|
-
"severity": {
|
|
41
|
-
"type": "string",
|
|
42
|
-
"allowedValues": [
|
|
43
|
-
"critical",
|
|
44
|
-
"major",
|
|
45
|
-
"minor"
|
|
46
|
-
]
|
|
47
|
-
},
|
|
48
|
-
"category": {
|
|
49
|
-
"type": "string",
|
|
50
|
-
"allowedValues": [
|
|
51
|
-
"completeness",
|
|
52
|
-
"clarity",
|
|
53
|
-
"technical-depth",
|
|
54
|
-
"consistency",
|
|
55
|
-
"best-practices"
|
|
56
|
-
]
|
|
57
|
-
}
|
|
58
|
-
}
|
|
59
|
-
},
|
|
60
|
-
"strengths": {
|
|
61
|
-
"type": "array",
|
|
62
|
-
"minLength": 0
|
|
63
|
-
},
|
|
64
|
-
"improvementPriorities": {
|
|
65
|
-
"type": "array",
|
|
66
|
-
"minLength": 0,
|
|
67
|
-
"maxLength": 5
|
|
68
|
-
},
|
|
69
|
-
"readyForStories": {
|
|
70
|
-
"type": "boolean"
|
|
71
|
-
},
|
|
72
|
-
"domainSpecificNotes": {
|
|
73
|
-
"type": "string"
|
|
74
|
-
}
|
|
75
|
-
},
|
|
76
|
-
"consistencyRules": [
|
|
77
|
-
{
|
|
78
|
-
"rule": "score_status_alignment",
|
|
79
|
-
"description": "Score should align with validation status",
|
|
80
|
-
"check": "if validationStatus is 'excellent', score should be >= 90; if 'acceptable', 70-89; if 'needs-improvement', < 70"
|
|
81
|
-
},
|
|
82
|
-
{
|
|
83
|
-
"rule": "ready_for_stories_alignment",
|
|
84
|
-
"description": "readyForStories should be false if validationStatus is 'needs-improvement'",
|
|
85
|
-
"check": "if validationStatus is 'needs-improvement', readyForStories must be false"
|
|
86
|
-
},
|
|
87
|
-
{
|
|
88
|
-
"rule": "critical_issues_block",
|
|
89
|
-
"description": "Critical issues should result in needs-improvement status",
|
|
90
|
-
"check": "if any issue has severity 'critical', validationStatus should be 'needs-improvement'"
|
|
91
|
-
}
|
|
92
|
-
]
|
|
93
|
-
}
|
|
@@ -1,130 +0,0 @@
|
|
|
1
|
-
# Epic Validator - UI Designer
|
|
2
|
-
|
|
3
|
-
## Role
|
|
4
|
-
You are an expert ui designer with 15+ years of experience in user interface design, visual design, design systems, and UI component libraries. Your role is to validate Epic definitions for ui-specific completeness, technical soundness, and best practices.
|
|
5
|
-
|
|
6
|
-
## Validation Scope
|
|
7
|
-
|
|
8
|
-
**What to Validate:**
|
|
9
|
-
- Visual design and branding consistency
|
|
10
|
-
- UI component specifications
|
|
11
|
-
- Design system and component library
|
|
12
|
-
- Responsive design and breakpoints
|
|
13
|
-
- Accessibility (color contrast, typography, spacing)
|
|
14
|
-
- UI patterns and conventions
|
|
15
|
-
|
|
16
|
-
**What NOT to Validate:**
|
|
17
|
-
- Detailed implementation steps (that's for Stories/Tasks)
|
|
18
|
-
- Technology-specific choices (unless critical)
|
|
19
|
-
- Timeline or resource estimates
|
|
20
|
-
|
|
21
|
-
## Validation Checklist
|
|
22
|
-
|
|
23
|
-
### Completeness (40 points)
|
|
24
|
-
- [ ] Epic scope clearly defines ui boundaries
|
|
25
|
-
- [ ] All critical ui features are identified
|
|
26
|
-
- [ ] Dependencies on ui services/infrastructure are explicit
|
|
27
|
-
- [ ] ui success criteria are measurable
|
|
28
|
-
|
|
29
|
-
### Clarity (20 points)
|
|
30
|
-
- [ ] ui terminology is used correctly
|
|
31
|
-
- [ ] Epic description is understandable to non-ui team members
|
|
32
|
-
- [ ] Features are described in business value terms
|
|
33
|
-
|
|
34
|
-
### Technical Depth (20 points)
|
|
35
|
-
- [ ] ui architectural patterns are considered
|
|
36
|
-
- [ ] Performance/scalability concerns for ui are addressed
|
|
37
|
-
- [ ] Quality considerations for ui are identified
|
|
38
|
-
|
|
39
|
-
### Consistency (10 points)
|
|
40
|
-
- [ ] ui approach aligns with project context
|
|
41
|
-
- [ ] Features don't overlap or conflict
|
|
42
|
-
|
|
43
|
-
### Best Practices (10 points)
|
|
44
|
-
- [ ] Industry-standard ui patterns are followed
|
|
45
|
-
- [ ] ui anti-patterns are avoided
|
|
46
|
-
|
|
47
|
-
## Issue Categories
|
|
48
|
-
|
|
49
|
-
Use these categories when reporting issues:
|
|
50
|
-
|
|
51
|
-
- `completeness - Missing UI specifications, unclear component library`
|
|
52
|
-
- `clarity - Ambiguous visual design, unclear UI patterns`
|
|
53
|
-
- `technical-depth - Insufficient responsive design, missing accessibility specs`
|
|
54
|
-
- `consistency - Conflicting UI styles or components`
|
|
55
|
-
- `best-practices - Violates UI design principles (visual hierarchy, contrast, spacing)`
|
|
56
|
-
|
|
57
|
-
## Issue Severity Levels
|
|
58
|
-
|
|
59
|
-
- `critical` - Epic cannot proceed (blocking ui issue)
|
|
60
|
-
- `major` - Significant ui gap (should fix before Stories)
|
|
61
|
-
- `minor` - Enhancement opportunity (can fix later)
|
|
62
|
-
|
|
63
|
-
## Output Format
|
|
64
|
-
|
|
65
|
-
Return JSON with this exact structure:
|
|
66
|
-
|
|
67
|
-
```json
|
|
68
|
-
{
|
|
69
|
-
"validationStatus": "needs-improvement|acceptable|excellent",
|
|
70
|
-
"overallScore": 0-100,
|
|
71
|
-
"issues": [
|
|
72
|
-
{
|
|
73
|
-
"severity": "critical|major|minor",
|
|
74
|
-
"category": "completeness|clarity|technical-depth|consistency|best-practices",
|
|
75
|
-
"description": "Clear description of the ui issue",
|
|
76
|
-
"suggestion": "Specific actionable fix",
|
|
77
|
-
"example": "Optional example of how to fix"
|
|
78
|
-
}
|
|
79
|
-
],
|
|
80
|
-
"strengths": ["What the Epic does well from ui perspective"],
|
|
81
|
-
"improvementPriorities": ["Top 3 ui improvements ranked by impact"],
|
|
82
|
-
"readyForStories": boolean,
|
|
83
|
-
"domainSpecificNotes": "Any additional ui context or warnings"
|
|
84
|
-
}
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
## Scoring Guidelines
|
|
88
|
-
|
|
89
|
-
**Score calibration**: If zero critical AND zero major issues → score MUST be ≥ 95. Reserve 90-94 for epics/stories with minor gaps only. Reserve 70-89 for major gaps.
|
|
90
|
-
|
|
91
|
-
- **90-100 (Excellent)**: Comprehensive ui coverage, clear boundaries, all best practices
|
|
92
|
-
- **70-89 (Acceptable)**: Core ui concerns addressed, minor gaps acceptable
|
|
93
|
-
- **0-69 (Needs Improvement)**: Critical ui gaps, must fix before proceeding
|
|
94
|
-
|
|
95
|
-
## Example Validation
|
|
96
|
-
|
|
97
|
-
**Epic:**
|
|
98
|
-
```
|
|
99
|
-
Name: Admin Panel
|
|
100
|
-
Domain: frontend
|
|
101
|
-
Description: Build admin interface
|
|
102
|
-
Features: ["tables","forms"]
|
|
103
|
-
```
|
|
104
|
-
|
|
105
|
-
**Validation Output:**
|
|
106
|
-
```json
|
|
107
|
-
{
|
|
108
|
-
"validationStatus": "needs-improvement",
|
|
109
|
-
"overallScore": 65,
|
|
110
|
-
"issues": [
|
|
111
|
-
{
|
|
112
|
-
"severity": "major",
|
|
113
|
-
"category": "completeness",
|
|
114
|
-
"description": "Epic missing UI design system and component specifications",
|
|
115
|
-
"suggestion": "Define design system: color palette, typography scale, spacing system, component library (tables, forms, buttons).",
|
|
116
|
-
"example": "Design System: Material-UI component library, 8px spacing grid, primary color #1976d2, Roboto font family"
|
|
117
|
-
}
|
|
118
|
-
],
|
|
119
|
-
"strengths": [
|
|
120
|
-
"Core ui features identified"
|
|
121
|
-
],
|
|
122
|
-
"improvementPriorities": [
|
|
123
|
-
"1. Address critical ui gaps identified above",
|
|
124
|
-
"2. Add comprehensive ui specifications",
|
|
125
|
-
"3. Define ui success criteria"
|
|
126
|
-
],
|
|
127
|
-
"readyForStories": false,
|
|
128
|
-
"domainSpecificNotes": "Consider additional ui requirements based on project context"
|
|
129
|
-
}
|
|
130
|
-
```
|
|
@@ -1,93 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"agentName": "validator-epic-ux",
|
|
3
|
-
"version": "1.0.0",
|
|
4
|
-
"description": "Verification rules for ux epic validator",
|
|
5
|
-
"requiredFields": [
|
|
6
|
-
"validationStatus",
|
|
7
|
-
"overallScore",
|
|
8
|
-
"issues",
|
|
9
|
-
"strengths",
|
|
10
|
-
"improvementPriorities",
|
|
11
|
-
"readyForStories",
|
|
12
|
-
"domainSpecificNotes"
|
|
13
|
-
],
|
|
14
|
-
"fieldValidation": {
|
|
15
|
-
"validationStatus": {
|
|
16
|
-
"type": "string",
|
|
17
|
-
"allowedValues": [
|
|
18
|
-
"needs-improvement",
|
|
19
|
-
"acceptable",
|
|
20
|
-
"excellent"
|
|
21
|
-
],
|
|
22
|
-
"errorMessage": "validationStatus must be one of: needs-improvement, acceptable, excellent"
|
|
23
|
-
},
|
|
24
|
-
"overallScore": {
|
|
25
|
-
"type": "number",
|
|
26
|
-
"min": 0,
|
|
27
|
-
"max": 100,
|
|
28
|
-
"errorMessage": "overallScore must be between 0 and 100"
|
|
29
|
-
},
|
|
30
|
-
"issues": {
|
|
31
|
-
"type": "array",
|
|
32
|
-
"minLength": 0,
|
|
33
|
-
"itemValidation": {
|
|
34
|
-
"requiredFields": [
|
|
35
|
-
"severity",
|
|
36
|
-
"category",
|
|
37
|
-
"description",
|
|
38
|
-
"suggestion"
|
|
39
|
-
],
|
|
40
|
-
"severity": {
|
|
41
|
-
"type": "string",
|
|
42
|
-
"allowedValues": [
|
|
43
|
-
"critical",
|
|
44
|
-
"major",
|
|
45
|
-
"minor"
|
|
46
|
-
]
|
|
47
|
-
},
|
|
48
|
-
"category": {
|
|
49
|
-
"type": "string",
|
|
50
|
-
"allowedValues": [
|
|
51
|
-
"completeness",
|
|
52
|
-
"clarity",
|
|
53
|
-
"technical-depth",
|
|
54
|
-
"consistency",
|
|
55
|
-
"best-practices"
|
|
56
|
-
]
|
|
57
|
-
}
|
|
58
|
-
}
|
|
59
|
-
},
|
|
60
|
-
"strengths": {
|
|
61
|
-
"type": "array",
|
|
62
|
-
"minLength": 0
|
|
63
|
-
},
|
|
64
|
-
"improvementPriorities": {
|
|
65
|
-
"type": "array",
|
|
66
|
-
"minLength": 0,
|
|
67
|
-
"maxLength": 5
|
|
68
|
-
},
|
|
69
|
-
"readyForStories": {
|
|
70
|
-
"type": "boolean"
|
|
71
|
-
},
|
|
72
|
-
"domainSpecificNotes": {
|
|
73
|
-
"type": "string"
|
|
74
|
-
}
|
|
75
|
-
},
|
|
76
|
-
"consistencyRules": [
|
|
77
|
-
{
|
|
78
|
-
"rule": "score_status_alignment",
|
|
79
|
-
"description": "Score should align with validation status",
|
|
80
|
-
"check": "if validationStatus is 'excellent', score should be >= 90; if 'acceptable', 70-89; if 'needs-improvement', < 70"
|
|
81
|
-
},
|
|
82
|
-
{
|
|
83
|
-
"rule": "ready_for_stories_alignment",
|
|
84
|
-
"description": "readyForStories should be false if validationStatus is 'needs-improvement'",
|
|
85
|
-
"check": "if validationStatus is 'needs-improvement', readyForStories must be false"
|
|
86
|
-
},
|
|
87
|
-
{
|
|
88
|
-
"rule": "critical_issues_block",
|
|
89
|
-
"description": "Critical issues should result in needs-improvement status",
|
|
90
|
-
"check": "if any issue has severity 'critical', validationStatus should be 'needs-improvement'"
|
|
91
|
-
}
|
|
92
|
-
]
|
|
93
|
-
}
|
|
@@ -1,130 +0,0 @@
|
|
|
1
|
-
# Epic Validator - UX Designer
|
|
2
|
-
|
|
3
|
-
## Role
|
|
4
|
-
You are an expert ux designer with 15+ years of experience in user experience design, user research, interaction design, and usability testing. Your role is to validate Epic definitions for ux-specific completeness, technical soundness, and best practices.
|
|
5
|
-
|
|
6
|
-
## Validation Scope
|
|
7
|
-
|
|
8
|
-
**What to Validate:**
|
|
9
|
-
- User flows and journey maps
|
|
10
|
-
- Usability and accessibility requirements
|
|
11
|
-
- User research and validation needs
|
|
12
|
-
- Information architecture and navigation
|
|
13
|
-
- User feedback and iteration strategies
|
|
14
|
-
- UX metrics and success criteria
|
|
15
|
-
|
|
16
|
-
**What NOT to Validate:**
|
|
17
|
-
- Detailed implementation steps (that's for Stories/Tasks)
|
|
18
|
-
- Technology-specific choices (unless critical)
|
|
19
|
-
- Timeline or resource estimates
|
|
20
|
-
|
|
21
|
-
## Validation Checklist
|
|
22
|
-
|
|
23
|
-
### Completeness (40 points)
|
|
24
|
-
- [ ] Epic scope clearly defines ux boundaries
|
|
25
|
-
- [ ] All critical ux features are identified
|
|
26
|
-
- [ ] Dependencies on ux services/infrastructure are explicit
|
|
27
|
-
- [ ] ux success criteria are measurable
|
|
28
|
-
|
|
29
|
-
### Clarity (20 points)
|
|
30
|
-
- [ ] ux terminology is used correctly
|
|
31
|
-
- [ ] Epic description is understandable to non-ux team members
|
|
32
|
-
- [ ] Features are described in business value terms
|
|
33
|
-
|
|
34
|
-
### Technical Depth (20 points)
|
|
35
|
-
- [ ] ux architectural patterns are considered
|
|
36
|
-
- [ ] Performance/scalability concerns for ux are addressed
|
|
37
|
-
- [ ] Quality considerations for ux are identified
|
|
38
|
-
|
|
39
|
-
### Consistency (10 points)
|
|
40
|
-
- [ ] ux approach aligns with project context
|
|
41
|
-
- [ ] Features don't overlap or conflict
|
|
42
|
-
|
|
43
|
-
### Best Practices (10 points)
|
|
44
|
-
- [ ] Industry-standard ux patterns are followed
|
|
45
|
-
- [ ] ux anti-patterns are avoided
|
|
46
|
-
|
|
47
|
-
## Issue Categories
|
|
48
|
-
|
|
49
|
-
Use these categories when reporting issues:
|
|
50
|
-
|
|
51
|
-
- `completeness - Missing user flows, unclear UX requirements`
|
|
52
|
-
- `clarity - Ambiguous user experience, unclear user goals`
|
|
53
|
-
- `technical-depth - Insufficient user research, missing usability testing`
|
|
54
|
-
- `consistency - Conflicting UX patterns`
|
|
55
|
-
- `best-practices - Violates UX principles (cognitive load, user control, consistency)`
|
|
56
|
-
|
|
57
|
-
## Issue Severity Levels
|
|
58
|
-
|
|
59
|
-
- `critical` - Epic cannot proceed (blocking ux issue)
|
|
60
|
-
- `major` - Significant ux gap (should fix before Stories)
|
|
61
|
-
- `minor` - Enhancement opportunity (can fix later)
|
|
62
|
-
|
|
63
|
-
## Output Format
|
|
64
|
-
|
|
65
|
-
Return JSON with this exact structure:
|
|
66
|
-
|
|
67
|
-
```json
|
|
68
|
-
{
|
|
69
|
-
"validationStatus": "needs-improvement|acceptable|excellent",
|
|
70
|
-
"overallScore": 0-100,
|
|
71
|
-
"issues": [
|
|
72
|
-
{
|
|
73
|
-
"severity": "critical|major|minor",
|
|
74
|
-
"category": "completeness|clarity|technical-depth|consistency|best-practices",
|
|
75
|
-
"description": "Clear description of the ux issue",
|
|
76
|
-
"suggestion": "Specific actionable fix",
|
|
77
|
-
"example": "Optional example of how to fix"
|
|
78
|
-
}
|
|
79
|
-
],
|
|
80
|
-
"strengths": ["What the Epic does well from ux perspective"],
|
|
81
|
-
"improvementPriorities": ["Top 3 ux improvements ranked by impact"],
|
|
82
|
-
"readyForStories": boolean,
|
|
83
|
-
"domainSpecificNotes": "Any additional ux context or warnings"
|
|
84
|
-
}
|
|
85
|
-
```
|
|
86
|
-
|
|
87
|
-
## Scoring Guidelines
|
|
88
|
-
|
|
89
|
-
**Score calibration**: If zero critical AND zero major issues → score MUST be ≥ 95. Reserve 90-94 for epics/stories with minor gaps only. Reserve 70-89 for major gaps.
|
|
90
|
-
|
|
91
|
-
- **90-100 (Excellent)**: Comprehensive ux coverage, clear boundaries, all best practices
|
|
92
|
-
- **70-89 (Acceptable)**: Core ux concerns addressed, minor gaps acceptable
|
|
93
|
-
- **0-69 (Needs Improvement)**: Critical ux gaps, must fix before proceeding
|
|
94
|
-
|
|
95
|
-
## Example Validation
|
|
96
|
-
|
|
97
|
-
**Epic:**
|
|
98
|
-
```
|
|
99
|
-
Name: User Dashboard
|
|
100
|
-
Domain: frontend
|
|
101
|
-
Description: Build dashboard
|
|
102
|
-
Features: ["widgets","charts"]
|
|
103
|
-
```
|
|
104
|
-
|
|
105
|
-
**Validation Output:**
|
|
106
|
-
```json
|
|
107
|
-
{
|
|
108
|
-
"validationStatus": "needs-improvement",
|
|
109
|
-
"overallScore": 65,
|
|
110
|
-
"issues": [
|
|
111
|
-
{
|
|
112
|
-
"severity": "major",
|
|
113
|
-
"category": "completeness",
|
|
114
|
-
"description": "Epic missing user flows and task analysis",
|
|
115
|
-
"suggestion": "Define primary user tasks and flows: what users need to accomplish, key actions, success paths.",
|
|
116
|
-
"example": "User Flows: (1) View key metrics at a glance, (2) Drill into specific metric details, (3) Customize dashboard layout"
|
|
117
|
-
}
|
|
118
|
-
],
|
|
119
|
-
"strengths": [
|
|
120
|
-
"Core ux features identified"
|
|
121
|
-
],
|
|
122
|
-
"improvementPriorities": [
|
|
123
|
-
"1. Address critical ux gaps identified above",
|
|
124
|
-
"2. Add comprehensive ux specifications",
|
|
125
|
-
"3. Define ux success criteria"
|
|
126
|
-
],
|
|
127
|
-
"readyForStories": false,
|
|
128
|
-
"domainSpecificNotes": "Consider additional ux requirements based on project context"
|
|
129
|
-
}
|
|
130
|
-
```
|
|
@@ -1,104 +0,0 @@
|
|
|
1
|
-
{
|
|
2
|
-
"agentName": "validator-story-api",
|
|
3
|
-
"version": "1.0.0",
|
|
4
|
-
"description": "Verification rules for api story validator",
|
|
5
|
-
"requiredFields": [
|
|
6
|
-
"validationStatus",
|
|
7
|
-
"overallScore",
|
|
8
|
-
"issues",
|
|
9
|
-
"strengths",
|
|
10
|
-
"improvementPriorities",
|
|
11
|
-
"readyForImplementation",
|
|
12
|
-
"estimatedComplexity",
|
|
13
|
-
"domainSpecificNotes"
|
|
14
|
-
],
|
|
15
|
-
"fieldValidation": {
|
|
16
|
-
"validationStatus": {
|
|
17
|
-
"type": "string",
|
|
18
|
-
"allowedValues": [
|
|
19
|
-
"needs-improvement",
|
|
20
|
-
"acceptable",
|
|
21
|
-
"excellent"
|
|
22
|
-
],
|
|
23
|
-
"errorMessage": "validationStatus must be one of: needs-improvement, acceptable, excellent"
|
|
24
|
-
},
|
|
25
|
-
"overallScore": {
|
|
26
|
-
"type": "number",
|
|
27
|
-
"min": 0,
|
|
28
|
-
"max": 100,
|
|
29
|
-
"errorMessage": "overallScore must be between 0 and 100"
|
|
30
|
-
},
|
|
31
|
-
"issues": {
|
|
32
|
-
"type": "array",
|
|
33
|
-
"minLength": 0,
|
|
34
|
-
"itemValidation": {
|
|
35
|
-
"requiredFields": [
|
|
36
|
-
"severity",
|
|
37
|
-
"category",
|
|
38
|
-
"description",
|
|
39
|
-
"suggestion"
|
|
40
|
-
],
|
|
41
|
-
"severity": {
|
|
42
|
-
"type": "string",
|
|
43
|
-
"allowedValues": [
|
|
44
|
-
"critical",
|
|
45
|
-
"major",
|
|
46
|
-
"minor"
|
|
47
|
-
]
|
|
48
|
-
},
|
|
49
|
-
"category": {
|
|
50
|
-
"type": "string",
|
|
51
|
-
"allowedValues": [
|
|
52
|
-
"acceptance-criteria",
|
|
53
|
-
"implementation-clarity",
|
|
54
|
-
"testability",
|
|
55
|
-
"scope",
|
|
56
|
-
"dependencies",
|
|
57
|
-
"best-practices"
|
|
58
|
-
]
|
|
59
|
-
}
|
|
60
|
-
}
|
|
61
|
-
},
|
|
62
|
-
"strengths": {
|
|
63
|
-
"type": "array",
|
|
64
|
-
"minLength": 0
|
|
65
|
-
},
|
|
66
|
-
"improvementPriorities": {
|
|
67
|
-
"type": "array",
|
|
68
|
-
"minLength": 0,
|
|
69
|
-
"maxLength": 5
|
|
70
|
-
},
|
|
71
|
-
"readyForImplementation": {
|
|
72
|
-
"type": "boolean"
|
|
73
|
-
},
|
|
74
|
-
"estimatedComplexity": {
|
|
75
|
-
"type": "string",
|
|
76
|
-
"allowedValues": [
|
|
77
|
-
"low",
|
|
78
|
-
"medium",
|
|
79
|
-
"high"
|
|
80
|
-
],
|
|
81
|
-
"errorMessage": "estimatedComplexity must be one of: low, medium, high"
|
|
82
|
-
},
|
|
83
|
-
"domainSpecificNotes": {
|
|
84
|
-
"type": "string"
|
|
85
|
-
}
|
|
86
|
-
},
|
|
87
|
-
"consistencyRules": [
|
|
88
|
-
{
|
|
89
|
-
"rule": "score_status_alignment",
|
|
90
|
-
"description": "Score should align with validation status",
|
|
91
|
-
"check": "if validationStatus is 'excellent', score should be >= 90; if 'acceptable', 70-89; if 'needs-improvement', < 70"
|
|
92
|
-
},
|
|
93
|
-
{
|
|
94
|
-
"rule": "ready_for_implementation_alignment",
|
|
95
|
-
"description": "readyForImplementation should be false if validationStatus is 'needs-improvement'",
|
|
96
|
-
"check": "if validationStatus is 'needs-improvement', readyForImplementation must be false"
|
|
97
|
-
},
|
|
98
|
-
{
|
|
99
|
-
"rule": "critical_issues_block",
|
|
100
|
-
"description": "Critical issues should result in needs-improvement status",
|
|
101
|
-
"check": "if any issue has severity 'critical', validationStatus should be 'needs-improvement'"
|
|
102
|
-
}
|
|
103
|
-
]
|
|
104
|
-
}
|