systematic-planning
Systematic Planning Skill
Transform complex feature requests into structured, executable plans.
When to Use
- Complex features requiring multiple components
- Features touching backend + frontend + infrastructure
- Tasks requiring careful design before implementation
Planning Phases
Phase 1: Business Specification
Define what we're building and why:
## Feature: [Name]
### Problem Statement
[What problem does this solve?]
More from ashchupliak/dream-team
kotlin-spring-boot
Kotlin/Spring Boot 3.x patterns - use for backend services, REST APIs, dependency injection, controllers, and service layers
113flyway-migrations
Flyway database migrations - use for schema changes, data migrations, version management, and PostgreSQL DDL
89k8s-helm
Kubernetes and Helm patterns - use for deployment configs, service definitions, ConfigMaps, Secrets, and Helm chart management
82grpc-protobuf
gRPC and Protocol Buffers - use for service-to-service communication, API definitions, streaming, and inter-service contracts
70prisma-patterns
Prisma ORM patterns - use for database access in Next.js, schema design, migrations, transactions, and relations
68nextjs-patterns
Next.js 15 App Router patterns - use for frontend pages, API routes, server components, client components, and middleware
51