Run any Skill in Manus with one click

Get Started

bootstrap

Stars5

Forks4

UpdatedJuly 16, 2026 at 14:16

Prepare the local environment required by a ProdOps execution before Git flow, tests, or implementation begin.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

produtoreativo

produtoreativo/payments-api

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	bootstrap
description	Prepare the local environment required by a ProdOps execution before Git flow, tests, or implementation begin.

BOOTSTRAP

Bootstrap prepares the execution environment. It does not assess product readiness, read implementation code or tests, create branches, or implement behavior.

Product readiness belongs to the /downstream orchestrator. Git flow belongs to /hack start.

Inputs

Repository setup scripts and package manifests
Environment variable names from example files
Local infrastructure configuration
Bootstrap and smoke gates from prodops/exec/manifest.yaml

OBCs, BDD Features, risks, Reliability Plans and the Iteration Plan are not Bootstrap inputs.

Flow

Identify the packages and local services required by the repository.
Verify required runtimes and command-line tools are available.
Install dependencies using the repository's declared package manager.
Prepare local infrastructure through the repository setup scripts.
Verify required environment variable names without reading or exposing secret values.
Run the smoke gate defined in prodops/exec/manifest.yaml.
Report the environment as ready or return a concrete blocker.

Guardrails

Do not read or modify production implementation code.
Do not inspect or execute behavior tests; those belong to Hack and Finish.
Do not create, switch, merge, rebase, stash, or delete Git branches.
Do not read or create OBCs, BDD Features, risks, Reliability Plans or Iteration Plan entries.
Do not generate a context capsule.
Do not expose .env values, tokens, credentials or PII.
Do not silently discard local work.

Post-conditions

Dependencies are installed.
Required local services are available.
Environment configuration requirements are known without secrets being exposed.
The smoke gate passes, or the environment blocker is explicit.
/hack start can establish the Git flow after Downstream readiness is reached.

More from this repository

same repository

diligence-diligence-async

produtoreativo/payments-api

Proactive drift-scan cycle. Reads all active OBCs and Issues, identifies divergences, and repairs what can be automated. Runs across the entire active backlog, not for a specific OBC.

2026-07-245

diligence-scan

produtoreativo/payments-api

Read all active OBCs and compare declared state with backlogs and external tools. Produces a divergence list. Does not repair — only identifies gaps.

2026-07-245

diligence-diligence-sync

produtoreativo/payments-api

Event-driven cycle triggered by a product decision. Captures the decision as an OBC, attaches a Work Item, promotes it through the backlog hierarchy, and closes it when the OBC reaches Operational. Runs for a specific OBC.

2026-07-245

diligence-capture

produtoreativo/payments-api

Create or update an OBC from the decision that triggered the Diligence Sync cycle. Use when an Assessment decision, Discovery experiment, or Operation signal requires canonical state to be recorded before Work Items are created.

2026-07-245

diligence

produtoreativo/payments-api

Synchronize OBC state across backlogs and tools. Runs event-driven cycle (diligence-sync) or proactive drift-scan cycle (diligence-async). Never touches product code.

2026-07-245

diligence-flag

produtoreativo/payments-api

Classify divergences from Scan and register them as pending Diligence items with severity and corrective action. Does not repair — only signals.

2026-07-235

name	bootstrap
description	Prepare the local environment required by a ProdOps execution before Git flow, tests, or implementation begin.

BOOTSTRAP

Bootstrap prepares the execution environment. It does not assess product readiness, read implementation code or tests, create branches, or implement behavior.

Product readiness belongs to the /downstream orchestrator. Git flow belongs to /hack start.

Inputs

Repository setup scripts and package manifests
Environment variable names from example files
Local infrastructure configuration
Bootstrap and smoke gates from prodops/exec/manifest.yaml

OBCs, BDD Features, risks, Reliability Plans and the Iteration Plan are not Bootstrap inputs.

Flow

Identify the packages and local services required by the repository.
Verify required runtimes and command-line tools are available.
Install dependencies using the repository's declared package manager.
Prepare local infrastructure through the repository setup scripts.
Verify required environment variable names without reading or exposing secret values.
Run the smoke gate defined in prodops/exec/manifest.yaml.
Report the environment as ready or return a concrete blocker.

Guardrails

Do not read or modify production implementation code.
Do not inspect or execute behavior tests; those belong to Hack and Finish.
Do not create, switch, merge, rebase, stash, or delete Git branches.
Do not read or create OBCs, BDD Features, risks, Reliability Plans or Iteration Plan entries.
Do not generate a context capsule.
Do not expose .env values, tokens, credentials or PII.
Do not silently discard local work.

Post-conditions

Dependencies are installed.
Required local services are available.
Environment configuration requirements are known without secrets being exposed.
The smoke gate passes, or the environment blocker is explicit.
/hack start can establish the Git flow after Downstream readiness is reached.