From draft
Generates customized pre-deployment verification checklists based on project tech stack, covering tests, migrations, configs, monitoring, and rollback plans.
npx claudepluginhub mayurpise/draft --plugin draftThis skill uses the workspace's default tool permissions.
You are generating a pre-deployment verification checklist customized to this project's technology stack.
Generates customizable pre-deployment checklists to verify CI status, tests, reviews, migrations, feature flags, rollback plans, and monitor production deploys.
Generates pre-deployment checklists for code quality, security, performance, infrastructure, database migrations, and produces go/no-go readiness report.
Generates tailored pre-deployment QA checklists by exploring codebase, confirming project understanding, and spawning parallel subagents for frontend, backend, database, security analysis. Use for deploy readiness checks.
Share bugs, ideas, or general feedback.
You are generating a pre-deployment verification checklist customized to this project's technology stack.
Every deployment needs a rollback plan. No exceptions.
Before starting, capture the current git state:
git branch --show-current # Current branch name
git rev-parse --short HEAD # Current commit hash
Store this for the checklist header. The checklist is scoped to this specific branch/commit.
ls draft/ 2>/dev/null
If draft/ doesn't exist, this skill can still run standalone — generate a generic checklist.
Read and follow the base procedure in core/shared/draft-context-loading.md.
Check for arguments:
/draft:deploy-checklist — Interactive: detect active track or ask for service name/draft:deploy-checklist <service> — Generate checklist for named service/draft:deploy-checklist track <id> — Generate from track's change scopeIf a track is active: read draft/tracks/<id>/spec.md and plan.md for change scope.
draft/tech-stack.md — Identify deployment-relevant tech:
draft/workflow.md — Deployment conventions and verification gatesdraft/.ai-context.md — Service topology, dependenciesGenerate a three-phase checklist customized to the project's tech stack. Adapt items based on what the project actually uses — omit irrelevant items (e.g., skip database items if there is no database) and add project-specific items discovered in context.
npm audit / pip audit / equivalent)[specific rollback command] ready to executeInitiate rollback if ANY of these occur:
Present the checklist interactively. For each critical item (marked bold):
Allow the user to:
MANDATORY: Include YAML frontmatter with git metadata. Follow core/shared/git-report-metadata.md.
Include the report header table immediately after frontmatter:
| Field | Value |
|-------|-------|
| **Branch** | `{LOCAL_BRANCH}` → `{REMOTE/BRANCH}` |
| **Commit** | `{SHORT_SHA}` — {COMMIT_MESSAGE} |
| **Generated** | {ISO_TIMESTAMP} |
| **Synced To** | `{FULL_SHA}` |
Save to:
draft/tracks/<id>/deploy-checklist.mddraft/deploy-checklist-<timestamp>.md with symlink deploy-checklist-latest.mdTIMESTAMP=$(date +%Y-%m-%dT%H%M)
# Example: draft/deploy-checklist-2026-03-15T1430.md
ln -sf deploy-checklist-${TIMESTAMP}.md draft/deploy-checklist-latest.md
core/agents/ops.md for production-safety mindsetcore/shared/jira-sync.mdgh CLI for PR details, Jira MCP for ticket contextIf no tech-stack.md: Generate generic checklist with all items, note: "Customize after running /draft:init"
If no active track: Generate standalone checklist, ask which service/release
If no workflow.md: Use sensible defaults, recommend documenting deployment conventions