Menu
Platform Developer: Stage 4 build task. Docker Compose setup, infra config, PR summary authoring, and Stage 4 gate writing for the platform workstream.
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.
Based on SOC occupation classification
Platform Developer: Stage 8 deploy task. Adapter-driven deployment — read config.yml for the adapter, follow adapter instructions, write deploy-log.md and stage-08.json.
G7 — apply property-based testing, mutation testing, and formal verification as a stage-06d sub-stage. "Tests pass" becomes the floor; this skill raises the ceiling. Use after stage-06 PASS, when the diff contains pure functions / critical business logic / state machines worth verifying beyond examples.
Run a structured codebase audit — map architecture, assess health (compliance / tests / docs), perform deep analysis (security / performance / code quality), and synthesize a prioritized roadmap. Use this skill when the user says things like 'audit the codebase', 'understand this project', 'find problems', '/audit', or '/audit-quick'. Phases produce machine-friendly markdown outputs under docs/audit/ that downstream commands (like the implement skill) consume to know where to start work.
QA Developer: Stage 6 test-authoring phase. Map every acceptance criterion to at least one test, write the test suite, and produce pipeline/pr-qa.md. Does NOT run the suite — that is the test-execution phase (skills/qa-test-execution/SKILL.md).
Verify at Stage 6c that every metric, log, and trace promised in the design-spec is actually emitted by the shipped code. Runs on full and hotfix tracks only. Produces the stage-06c gate. Use when the platform role owns observability sign-off after build and QA.
Platform Developer: Stage 4a pre-review task. Run lint, type-check, SCA, license check, security trigger, and hygiene checks. Produce pipeline/gates/stage-04a.json.
| name | platform-build |
| description | Platform Developer: Stage 4 build task. Docker Compose setup, infra config, PR summary authoring, and Stage 4 gate writing for the platform workstream. |
Use this skill when you are the Platform Developer executing the Stage 4 build stage — setting up infra, CI, and the deploy rails for a new feature.
Read pipeline/design-spec.md — set up infra, CI, and root toolchain
config to support what's being built.
Append an ## Assumptions block to pipeline/context.md for non-obvious
infra choices (ports, volumes, healthcheck targets) per coding-principles §1.
Write the Plan preamble at the top of pipeline/pr-platform.md per §4.
Write or update docker-compose.yml in the project root:
healthcheck: to every HTTP service so docker compose up --wait works.env for all secrets and environment-specific values — never hardcodeWrite or update any supporting infra/toolchain config (.env.example,
nginx config, package.json scripts, lockfiles, ESLint/TypeScript config,
Docker/compose files, etc.). Root package-manager scripts and shared
toolchain config are platform-owned unless the design spec or a Principal
ruling assigns them elsewhere. If npm run lint is missing, add the script
and any minimal config needed for Stage 4a to run it mechanically.
Keep source-code changes inside src/infra/; cross-boundary edits need a
CONCERN: line first (coding-principles §3).
Finish pipeline/pr-platform.md. Include ## Out of Scope — Noticed. Also:
## Verify — required before writing a PASS gate. One bullet per
infrastructure criterion you claim to have satisfied, in this exact shape:
## Verify
- **AC-7**: docker-compose brings the stack up cleanly
- `docker compose up --wait`
- → `Network created`, `Container api healthy`, `Container db healthy`,
exit 0 after 14s
- **AC-8**: nginx forwards /api to backend on port 3000
- `curl -i http://localhost/api/health`
- → `HTTP/1.1 200 OK`, body `{"status":"ok"}`, no nginx 502
Each bullet ties one acceptance-criterion ID to (a) the exact command you
ran and (b) the observed output — docker compose ps output, a
curl -i response, a health-check status. Not "infra is set up." A PASS
gate whose ## Verify is empty, missing, or lists ACs you didn't
actually exercise is invalid and will be flagged at peer review.
Write pipeline/gates/stage-04.platform.json with "status": "PASS". PASS
is only honest when every AC has a ## Verify bullet with a real command
and a real observed output. If even one AC is unverified, the right status
is FAIL or escalate back to the PM for clarification — not PASS.