Agent skill
pmtl-production-ready
PMTL_VN production-ready operating skill. Use for implementation, debugging, hardening, monitoring, deployment-impacting changes, or release-minded code review. This is the high-agency umbrella skill for turning PMTL work into production-safe work with explicit verification and documented recovery paths.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/pmtl-production-ready
SKILL.md
PMTL Production Ready
Legacy umbrella skill. Do not use by default when the canonical taxonomy skills already cover the task.
Use this skill when the task is bigger than a local code tweak and has production implications.
Operating model
This skill is not just a reminder list. It decides which lane to follow:
- implementation lane
- incident/debug lane
- release gate lane
- hardening lane
Run scripts/select_playbook.py --task "<user task>" when the right lane is not obvious.
Read only what applies
- For implementation and refactor work:
references/implementation-lane.md - For runtime failures and regressions:
references/incident-lane.md - For final checks before merge, deploy, or “done”:
references/release-gate.md
Non-negotiables
- Keep logging structured with pino at real boundaries.
- Validate user input and env contracts with Zod.
- Preserve monorepo boundaries and NestJS module pattern (module + controller + service + dto + entities).
- Treat verification as part of delivery, not an optional extra.
- Update docs, skills, and project rules together when conventions change.
Pair with
pmtl-production-baselinefor baseline repo rulespmtl-verify-quality-gateafter meaningful editspmtl-verify-auth-flowandpmtl-verify-search-syncfor domain-specific checkspmtl-runbook-docker-dev-recoverywhen the task is Docker/infra incident-oriented
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?