@vfarcic/dot-ai 0.64.0 → 0.65.0
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/package.json
CHANGED
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: manage-org-data
|
|
3
|
+
description: Manage organizational patterns and cluster resource capabilities
|
|
4
|
+
category: administration
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Manage Organizational Data
|
|
8
|
+
|
|
9
|
+
## Choose what you want to manage:
|
|
10
|
+
|
|
11
|
+
### Organizational Patterns:
|
|
12
|
+
1. Create a new organizational pattern
|
|
13
|
+
2. List existing patterns
|
|
14
|
+
3. Get pattern details
|
|
15
|
+
4. Search patterns
|
|
16
|
+
|
|
17
|
+
### Resource Capabilities:
|
|
18
|
+
5. Scan cluster for resource capabilities
|
|
19
|
+
6. List discovered capabilities
|
|
20
|
+
7. Get capability details
|
|
21
|
+
8. Delete capability data
|
|
22
|
+
9. Delete all capabilities
|
|
23
|
+
10. Check scan progress
|
|
24
|
+
|
|
25
|
+
**Your choice**: [Type the number (1-10) or describe what you want to do]
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
Examples: Type "1" or "Create a new organizational pattern" or "5" or "Scan cluster"
|
|
30
|
+
|
|
31
|
+
Once you make your choice, I'll call the `manageOrgData` tool with the appropriate parameters.
|
|
@@ -10,14 +10,40 @@ Complete the PRD implementation workflow including branch management, pull reque
|
|
|
10
10
|
|
|
11
11
|
## Workflow Steps
|
|
12
12
|
|
|
13
|
+
### 0. Implementation Type Detection
|
|
14
|
+
**FIRST: Determine the type of PRD completion to choose the appropriate workflow**
|
|
15
|
+
|
|
16
|
+
**Documentation-Only Completion** (Skip PR workflow):
|
|
17
|
+
- ✅ Changes are only to PRD files or project management documents
|
|
18
|
+
- ✅ No source code changes
|
|
19
|
+
- ✅ No configuration changes
|
|
20
|
+
- ✅ Feature was already implemented in previous work
|
|
21
|
+
- → **Use Simplified Workflow** (Steps 1, 2-simplified, 5 only)
|
|
22
|
+
|
|
23
|
+
**Code Implementation Completion** (Full PR workflow):
|
|
24
|
+
- ✅ Contains source code changes
|
|
25
|
+
- ✅ Contains configuration changes
|
|
26
|
+
- ✅ Contains new functionality or modifications
|
|
27
|
+
- ✅ Requires testing and integration
|
|
28
|
+
- → **Use Full Workflow** (Steps 1-6)
|
|
29
|
+
|
|
13
30
|
### 1. Pre-Completion Validation
|
|
14
31
|
- [ ] **All PRD checkboxes completed**: Verify every requirement is implemented and tested
|
|
15
|
-
- [ ] **All tests passing**: Run
|
|
32
|
+
- [ ] **All tests passing**: Run project test suite to ensure quality standards (skip if documentation-only)
|
|
16
33
|
- [ ] **Documentation updated**: All user-facing docs reflect implemented functionality
|
|
17
34
|
- [ ] **No outstanding blockers**: All dependencies resolved and technical debt addressed
|
|
18
|
-
- [ ] **Update PRD status**: Mark PRD as "Complete" with completion date
|
|
35
|
+
- [ ] **Update PRD status**: Mark PRD as "Complete" with completion date
|
|
19
36
|
|
|
20
37
|
### 2. Branch and Commit Management
|
|
38
|
+
|
|
39
|
+
**For Documentation-Only Completions:**
|
|
40
|
+
- [ ] **Commit directly to main**: `git add [prd-files]` and commit with skip CI flag
|
|
41
|
+
- [ ] **Use skip CI commit message**: Include CI skip pattern in commit message to avoid unnecessary CI runs
|
|
42
|
+
- Common patterns: `[skip ci]`, `[ci skip]`, `***NO_CI***`, `[skip actions]`
|
|
43
|
+
- Check project's CI configuration for the correct pattern
|
|
44
|
+
- [ ] **Push to remote**: `git push origin main` to sync changes
|
|
45
|
+
|
|
46
|
+
**For Code Implementation Completions:**
|
|
21
47
|
- [ ] **Create feature branch**: `git checkout -b feature/prd-[issue-id]-[feature-name]`
|
|
22
48
|
- [ ] **Commit all changes**: Ensure all implementation work is committed
|
|
23
49
|
- [ ] **Clean commit history**: Squash or organize commits for clear history
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: setup
|
|
3
|
+
description: Setup applications, infrastructure, and services in Kubernetes
|
|
4
|
+
category: deployment
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Setup in Kubernetes
|
|
8
|
+
|
|
9
|
+
What do you want to setup?
|
|
10
|
+
|
|
11
|
+
**Examples:**
|
|
12
|
+
- "Setup a Node.js web application with PostgreSQL database"
|
|
13
|
+
- "Setup Prometheus monitoring with Grafana dashboards"
|
|
14
|
+
- "Setup WordPress with MySQL and persistent storage"
|
|
15
|
+
- "Setup ArgoCD for GitOps workflows"
|
|
16
|
+
- "Setup Redis cluster for caching"
|
|
17
|
+
- "Setup ingress controller with SSL certificates"
|
|
18
|
+
|
|
19
|
+
**Your setup intent**: [Please describe what you want to setup]
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
Once you provide your intent, I'll call the `recommend` tool to generate setup recommendations for your Kubernetes cluster.
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: status
|
|
3
|
+
description: Check system status and health
|
|
4
|
+
category: administration
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# System Status Check
|
|
8
|
+
|
|
9
|
+
I'll check the comprehensive system status including:
|
|
10
|
+
|
|
11
|
+
✅ **Version information**
|
|
12
|
+
✅ **Vector DB connection status**
|
|
13
|
+
✅ **Embedding service capabilities**
|
|
14
|
+
✅ **Anthropic API connectivity**
|
|
15
|
+
✅ **Pattern management health**
|
|
16
|
+
|
|
17
|
+
---
|
|
18
|
+
|
|
19
|
+
Calling the `version` tool to get current system status...
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: validate-docs
|
|
3
|
+
description: Validate documentation files for accuracy and quality
|
|
4
|
+
category: documentation
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Validate Documentation
|
|
8
|
+
|
|
9
|
+
What documentation do you want to validate?
|
|
10
|
+
|
|
11
|
+
**Examples:**
|
|
12
|
+
- "Validate my README.md file"
|
|
13
|
+
- "Validate all markdown files in the docs/ directory"
|
|
14
|
+
- "Validate API documentation for broken links and examples"
|
|
15
|
+
- "Validate installation guide for outdated commands"
|
|
16
|
+
- "Validate tutorial documentation for accuracy"
|
|
17
|
+
|
|
18
|
+
**Your validation request**: [Please specify which documentation files you want to validate]
|
|
19
|
+
|
|
20
|
+
---
|
|
21
|
+
|
|
22
|
+
Once you specify the documentation, I'll call the `testDocs` tool to analyze your files for accuracy, functionality, broken examples, outdated commands, invalid links, and overall quality.
|