deploy

Executes production deployments by routing to the method defined in tech-context documentation.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill deploy-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/deploy
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill deploy-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying a completed phase to production requires knowing the project's specific platform, CI/CD setup, and verification method — and getting any step wrong ships untested or partial code. This Skill reads the project's tech-context document to determine the correct deploy method, confirms the phase test gate is open, and executes the deploy safely. ## Core Features & Use Cases - Platform-Agnostic Routing: Reads docs/tech-context.md to detect the deploy target and routes to CI/CD merge triggers, MCP tool deploys, manual CLI commands, or a guided setup flow. - Gate Verification: Confirms the phase test gate is OPEN, all slice branches are merged, and the phase completion record exists before any deploy proceeds. - One-Time CI/CD Setup: Generates GitHub Actions workflow files for Railway, Render, Cloudflare, Fly.io, and AWS App Runner, then walks the user through secret configuration in plain language. - Use Case: After phase testing passes, invoke this Skill to merge development into main, monitor the GitHub Actions pipeline, verify the live environment, and record the deploy in docs/backlog.md. ## Quick Start Deploy the current phase to production using the method configured in the tech setup document.

Frequently Asked Questions about deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a project to production with GitHub Actions?

Merge the base branch into the production branch defined in your tech-context, which triggers the CI/CD pipeline automatically. Monitor the pipeline to completion, then verify the live environment using the project's defined verification method such as a health endpoint or URL check.

How do I set up CI/CD for Railway, Render, or Fly.io?

Generate a .github/workflows/ci.yml file matching your platform, commit it, then add the required secret (RAILWAY_TOKEN, RENDER_DEPLOY_HOOK, or FLY_API_TOKEN) in your GitHub repository settings under Secrets and variables for Actions.

Can I deploy before phase testing is complete?

No. The deploy process stops if the phase test gate is not OPEN or the phase completion record is missing from docs/backlog.md. Phase testing must pass first to prevent shipping untested code.

What happens if deployment verification fails after a successful pipeline?

A failed verification after a green pipeline is treated as an environment issue, not a code issue, since phase testing already confirmed correctness. The failure is surfaced and routed separately without reopening QA.

What if my project has no deploy configuration defined?

The process asks targeted questions about your deployment platform, automation type, trigger branch, and verification method, then writes the answers into docs/tech-context.md before executing the appropriate deploy method.