<!-- Generated by mstack from Misbah's Build Like This workflow. Regenerate instead of editing. -->

deploy-product

Run Phase 9 with the deployment-delivery skill. The release-manager leads parallel preflight evidence lanes for DevOps, security, testing, and conditional database review, then serializes all stateful release actions.

This prompt follows Misbah Khursheed's Build Like This workflow: establish the user outcome and reasoning before generating implementation, then preserve that reasoning in contracts, boundaries, tests, and documentation.

Project identity and sources of truth

The repository where this prompt is installed is the host project being built. Build Like This is the engineering method used to build it, while mstack only installs and reconciles the method's resources. Do not mistake mstack or Build Like This for the host product unless project-owned sources explicitly say this repository develops mstack itself.

Project-owned docs/, decisions, executable code, and tests are the sources of truth. .mstack/templates/ are reference scaffolds that may be copied and adapted into project-owned documents; they are not requirements and do not replace docs/.

Treat the invocation arguments and current repository state as task input. Discover local instructions and relevant product, architecture, decision, contract, and test context before making material assumptions.

Method

1. Verify explicit authorization for the exact environment and operations, artifact identity, release scope, accountable owners, change window, and communication path.
2. Collect successful acceptance/build/test/security/readiness evidence and confirm compatibility, dependency health, configuration/secrets, backups, and recovery capability.
3. Publish and rehearse the ordered migration/deployment/feature-control sequence with smoke checks, metrics, stop thresholds, decision authority, and rollback/forward recovery.
4. Execute only authorized actions stage by stage, recording versions, timestamps, command results, observations, communications, and gate decisions.
5. Monitor product/system guardrails through progressive exposure; stop and recover when a predeclared threshold is crossed.
6. Complete post-release verification, support/incident handoff, release record, residual-risk ownership, and improvement review date.

Deliverables

• Authorization and go/no-go record tied to exact target, artifact, evidence, owners, and accepted risks.
• Executed release log with migration/deployment stages, smoke checks, monitoring, communication, and recovery actions.
• Post-release outcome/system checks, incidents, residual risks, owners, and measurement handoff.

Constraints

• Do not infer production authorization from repository access, prompt invocation without a named target, or a passing readiness review.
• Do not parallelize migrations, deployments, feature-state changes, or other shared-state actions whose order affects safety.
• Do not expose secrets or use rollback when incompatible data changes require forward recovery.

Delegation and parallel safety

• For a material lifecycle task, the active lead must delegate at least one bounded specialist lane when subagents are available; prefer two or more concurrent lanes only when their evidence or file ownership is independent.
• The active lead owns acceptance criteria and final integration. Supporting agents must not recursively delegate unless explicitly promoted to lead a named lane.
• Give each delegate distinct inputs, outputs, and ownership. Serialize shared documents, contracts, schemas, migrations, deployments, external writes, and overlapping file edits.
• If subagents are unavailable, perform the named specialist passes sequentially and report the limitation; do not imply parallel verification.
• Delegation does not authorize outreach, paid resources, destructive changes, consequential external writes, or production deployment.

Finish with what changed or was decided, exact verification evidence, remaining risks, and the next decision only if one is genuinely required.

User arguments: $ARGUMENTS