Intent System Gaps & Roadmap¶
Last updated: 2026-01-11
This document tracks known gaps in the intent system and planned improvements.
Critical Safety Gaps (P0)¶
1. migrate-schema lacks backup integration¶
Status: Fixed in v1.1.0
Problem: Production migrations could corrupt data with no recovery path.
Solution:
- Added backup_first parameter (default: true for production)
- Integrated with backup-app intent before applying migrations
- Added --dry-run mode to preview changes
2. restore-app lacks pre-validation¶
Status: In Progress
Problem: No validation that backup is valid/compatible before destructive restore.
Solution: - Add backup content listing before restore - Validate backup was created from compatible environment - Check target namespace state more thoroughly
3. No database rollback capability¶
Status: Implemented - database-rollback.yaml
Problem: Can migrate forward but can't roll back failed migrations.
Solution: Created database-rollback intent with:
- Rollback to specific migration version
- Automatic backup before rollback
- Transaction-safe rollback where possible
Missing Intents (P1)¶
Infrastructure Operations¶
| Intent | Description | Priority | Status |
|---|---|---|---|
create-namespace |
Create namespace with RBAC/quotas | Medium | Planned |
manage-pvc |
Create, resize, snapshot PVCs | Medium | Planned |
manage-ingress |
Create/update ingress rules | Medium | Planned |
update-helm-chart |
Update Velero, Authentik, etc. | Low | Planned |
Database Operations¶
| Intent | Description | Priority | Status |
|---|---|---|---|
database-rollback |
Reverse migrations | High | Done |
validate-schema |
Verify schema matches expected | Medium | Planned |
inspect-schema |
Show tables, columns, relationships | Low | Planned |
Debug Operations¶
| Intent | Description | Priority | Status |
|---|---|---|---|
debug-pod |
Exec into pod with structured output | Medium | Planned |
network-diagnose |
DNS, latency, connectivity tests | Low | Planned |
Undercooked Intents (P2)¶
deploy-app.yaml¶
Issues: - Version calculation repeated 4 times (copy-paste fragility) - No git validation before deploy - No automatic rollback on health check failure
Planned fixes:
- [ ] Use step output chaining for version
- [ ] Add git status check in prereqs
- [ ] Add auto_rollback parameter
create-nextjs-app.yaml¶
Issues: - Only checks file existence, not functionality - Doesn't create Supabase schema - K8s manifests not generated
Planned fixes: - [ ] Add Supabase schema creation step - [ ] Generate basic K8s manifest templates - [ ] Add smoke test after scaffold
rollback-app.yaml¶
Issues: - 3 rollback modes (revision/version/previous) are confusing - No validation target version exists
Planned fixes:
- [ ] Simplify to previous and version modes only
- [ ] Add list-versions helper step
- [ ] Validate version exists before attempting
Enhancement Opportunities (P3)¶
DRY Improvements¶
- Create reusable step library for common patterns:
- Version calculation
- Backup name discovery
- Namespace resolution
- Health check polling
Observability¶
- Add structured JSON logging option
- Include timing data for each step
- Better correlation with audit trail
Parameter Validation¶
- Whitelist of valid app names
- Numeric parameter type checking
- Environment validation (production vs sandbox)
Changelog¶
2026-01-11¶
- Created intent-gaps.md
- Fixed migrate-schema.yaml (backup integration)
- Created database-rollback.yaml
- Updated CLAUDE.md with accurate intent list