Production Stack Skills — Orchestrator
You are the router for the production-stack-skills pack. When the user invokes /production <subcommand>, dispatch to the appropriate specialized skill.
Command Router
| Command |
Skill |
What It Does |
/production check |
production-check |
Full audit with 0-100 score and prioritized action plan |
/production score |
production-check |
Quick 60-second headline score, top 3 findings |
/production report |
production-check |
Full audit formatted as a shareable Markdown report |
/production fastapi |
production-fastapi |
Apply FastAPI production patterns to current project |
/production postgres |
production-postgres |
Review migrations, indexes, connections, schema design |
/production docker |
production-docker |
Audit or generate production-grade Dockerfile |
/production deploy |
production-deploy |
Pre-deployment checklist walkthrough |
/production monitoring |
production-monitoring |
Add OTEL traces, structured logging, health endpoints |
/production security |
production-security |
Security audit — secrets, CORS, auth, rate limiting |
/production errors |
production-error-handling |
Apply error handling patterns — retries, circuit breakers |
/production review |
production-review |
Production-readiness code review on specific files/PRs |
/production plan |
production-planner |
Architecture planning with production constraints |
Routing Logic
- Parse the subcommand from the user's input
- Detect the project stack (language, framework, database, infrastructure)
- Dispatch to the appropriate skill — load its SKILL.md and follow its instructions
- If no subcommand is given, show the command table above and ask what they'd like to do
- If the subcommand is ambiguous, ask for clarification
No Subcommand — Default Behavior
If the user just says /production without a subcommand, respond with:
Production Stack Skills — available commands:
/production check Full audit with 0-100 score
/production score Quick headline score (60 seconds)
/production fastapi FastAPI production patterns
/production postgres PostgreSQL safety & performance
/production docker Container hardening
/production deploy Pre-deployment checklist
/production monitoring Observability setup
/production security Security hardening
/production errors Error handling patterns
/production review Production-readiness code review
/production plan Architecture planning
/production report Shareable readiness report
What would you like to do?
Stack Detection
Before dispatching, detect the project stack to provide context to the sub-skill:
Check for:
├── Python: pyproject.toml, requirements.txt, setup.py, Pipfile
│ ├── FastAPI: "fastapi" in dependencies
│ ├── Django: "django" in dependencies
│ └── Flask: "flask" in dependencies
├── Node.js: package.json
│ ├── Express: "express" in dependencies
│ └── Fastify: "fastify" in dependencies
├── Go: go.mod
├── Java: pom.xml, build.gradle
├── Database: connection strings, ORM configs, migration directories
├── Docker: Dockerfile, docker-compose.yml
└── CI/CD: .github/workflows/, .gitlab-ci.yml
Pass the detected stack to the sub-skill so it can tailor its recommendations.
General Guidelines
When routing to a sub-skill:
- Be specific: pass the detected stack and relevant file paths
- Be efficient: don't re-detect what the sub-skill will detect
- Be helpful: if the user asks for something that spans multiple skills, run them in sequence
- Cross-reference: after completing one skill, suggest related skills that would help
Example: After /production fastapi, suggest:
"Your FastAPI patterns are solid. Consider running /production docker to harden your container, and /production check for a full audit."
1---2name: production3description: Main orchestrator for the production-stack-skills pack. Routes /production subcommands to specialized skills. Use this skill when the user types /production followed by a subcommand (check, fastapi, postgres, docker, deploy, monitoring, security, errors, report, score). Also triggers when user says 'make this production ready', 'productionize this', or asks about production readiness in general.4---56# Production Stack Skills — Orchestrator78You are the router for the production-stack-skills pack. When the user invokes `/production <subcommand>`, dispatch to the appropriate specialized skill.910## Command Router1112| Command | Skill | What It Does |13|---------|-------|--------------|14| `/production check` | production-check | Full audit with 0-100 score and prioritized action plan |15| `/production score` | production-check | Quick 60-second headline score, top 3 findings |16| `/production report` | production-check | Full audit formatted as a shareable Markdown report |17| `/production fastapi` | production-fastapi | Apply FastAPI production patterns to current project |18| `/production postgres` | production-postgres | Review migrations, indexes, connections, schema design |19| `/production docker` | production-docker | Audit or generate production-grade Dockerfile |20| `/production deploy` | production-deploy | Pre-deployment checklist walkthrough |21| `/production monitoring` | production-monitoring | Add OTEL traces, structured logging, health endpoints |22| `/production security` | production-security | Security audit — secrets, CORS, auth, rate limiting |23| `/production errors` | production-error-handling | Apply error handling patterns — retries, circuit breakers |24| `/production review` | production-review | Production-readiness code review on specific files/PRs |25| `/production plan` | production-planner | Architecture planning with production constraints |2627## Routing Logic28291. **Parse the subcommand** from the user's input302. **Detect the project stack** (language, framework, database, infrastructure)313. **Dispatch to the appropriate skill** — load its SKILL.md and follow its instructions324. **If no subcommand is given**, show the command table above and ask what they'd like to do335. **If the subcommand is ambiguous**, ask for clarification3435## No Subcommand — Default Behavior3637If the user just says `/production` without a subcommand, respond with:3839```40Production Stack Skills — available commands:4142 /production check Full audit with 0-100 score43 /production score Quick headline score (60 seconds)44 /production fastapi FastAPI production patterns45 /production postgres PostgreSQL safety & performance46 /production docker Container hardening47 /production deploy Pre-deployment checklist48 /production monitoring Observability setup49 /production security Security hardening50 /production errors Error handling patterns51 /production review Production-readiness code review52 /production plan Architecture planning53 /production report Shareable readiness report5455What would you like to do?56```5758## Stack Detection5960Before dispatching, detect the project stack to provide context to the sub-skill:6162```63Check for:64├── Python: pyproject.toml, requirements.txt, setup.py, Pipfile65│ ├── FastAPI: "fastapi" in dependencies66│ ├── Django: "django" in dependencies67│ └── Flask: "flask" in dependencies68├── Node.js: package.json69│ ├── Express: "express" in dependencies70│ └── Fastify: "fastify" in dependencies71├── Go: go.mod72├── Java: pom.xml, build.gradle73├── Database: connection strings, ORM configs, migration directories74├── Docker: Dockerfile, docker-compose.yml75└── CI/CD: .github/workflows/, .gitlab-ci.yml76```7778Pass the detected stack to the sub-skill so it can tailor its recommendations.7980## General Guidelines8182When routing to a sub-skill:83- **Be specific**: pass the detected stack and relevant file paths84- **Be efficient**: don't re-detect what the sub-skill will detect85- **Be helpful**: if the user asks for something that spans multiple skills, run them in sequence86- **Cross-reference**: after completing one skill, suggest related skills that would help8788Example: After `/production fastapi`, suggest:89> "Your FastAPI patterns are solid. Consider running `/production docker` to harden your container, and `/production check` for a full audit."
vstorm-co