← Back to workflows
Live Operations Advanced External bundle v1.0.0

Geordi Build Pipeline

A narrow build pipeline for shipping stories without pretending verification is optional.

Installs from a real external skill bundle and runs PRD stories sequentially through Codex with context loading, separate verification, automatic retry, and ACP-first transport to the Mac builder.

Availability
Classification
External bundle
Install mode
Agent-installable
Review status
Source review
Verification mode
Source review

Installs from the linked GitHub skill source through OpenClaw. The artifacts listed here describe the external bundle, not files checked into this website repo.

Install source
GitHub skill bundle
openclaw skills install github:henrino3/enterprise-crew-skills/geordi-build-pipeline
Workflow record
Bundle id
superada.workflow.geordi-build-pipeline
Entrypoint
SKILL.md
Bundle root
github:henrino3/enterprise-crew-skills/geordi-build-pipeline
Artifact count
5 described items

A real external workflow bundle with the skill contract, ACP-aware scripts, YAML workflow definitions, and explicit verification steps that stay outside the coding loop.

Install contract
Installability
Truly installable now
Method
Installable via OpenClaw skill source
Install source spec
github:henrino3/enterprise-crew-skills/geordi-build-pipeline
openclaw skills install github:henrino3/enterprise-crew-skills/geordi-build-pipeline

Canonical source: https://github.com/henrino3/enterprise-crew-skills/tree/main/geordi-build-pipeline

Agent step 1
Review the linked GitHub bundle before install so the transport, workflow YAML, and verification flow are understood.
Agent step 2
Install it into OpenClaw with `openclaw skills install github:henrino3/enterprise-crew-skills/geordi-build-pipeline`.
Agent step 3
Create or initialize the required project context file before any run.
Agent step 4
Review the workflow definition for the target repo and builder host, then launch the skill manually.
Verification command
openclaw skills info geordi-build-pipeline
Current limits
  • Skill installation is real, but successful execution still depends on repo-specific context, builder access, and verification commands.
  • The workflow bundle is externally hosted, not checked into this website repo.
Step 1
Review the external bundle source
Read the linked skill files and workflow definitions before installing anything so the transport, retry, and verification behavior are understood.
Step 2
Install the skill bundle into OpenClaw
Pull the workflow bundle from GitHub so the skill contract and workflow assets are available locally.
openclaw skills install github:henrino3/enterprise-crew-skills/geordi-build-pipeline
Step 3
Ensure a project context file exists
Geordi expects a context file before any implementation run. Create one if the repo does not already have CONTEXT.md or a matching memory context file.
~/clawd/skills/geordi-build-pipeline/scripts/update-context.sh ~/Code/<project> --init
Step 4
Review or adapt the workflow definition
Confirm the YAML workflow points at the right repo, transport mode, verify commands, and target builder host before execution.
Step 5
Run the build pipeline manually
Start the bundle through the Geordi skill, then let ACP or fallback transport execute story work sequentially with separate verification.
openclaw agent run --skill geordi-build-pipeline

If you hand an agent this workflow URL, this install contract is the source of truth for whether it can really install the bundle now, what source to use, and what still needs a human.

What you get

  • Sequential story execution from a plan
  • Build verification outside the coding loop
  • Retry-on-failure flow with explicit blockers

Workflow includes

  • ACP-first transport
  • SSH fallback
  • Local fallback mode
  • Context update requirement

Described artifacts

Skill contract
skill
github:henrino3/enterprise-crew-skills/geordi-build-pipeline/SKILL.md
Canonical operating instructions for the builder pipeline, including ACP-first transport, retries, verification, and context update rules.
Context loader
script
github:henrino3/enterprise-crew-skills/geordi-build-pipeline/scripts/load-context.sh
Pulls project context, package summary, testing notes, and recent repo state into the task prompt before implementation.
Context updater
script
github:henrino3/enterprise-crew-skills/geordi-build-pipeline/scripts/update-context.sh
Appends dated changes back into the project context file after each completed build.
Workflow definitions
manifest
github:henrino3/enterprise-crew-skills/geordi-build-pipeline/workflows/*.yaml
Bundle-level YAML definitions that shape repo, transport, verify, and commit behavior for repeatable runs.
ACP transport helpers
bundle
github:henrino3/enterprise-crew-skills/acp/scripts/acp-run.sh + acp-status.sh
Required runner helpers for dispatching Geordi tasks over ACP and waiting for structured completion.

Requirements

OpenClaw skill install support
runtime
The target environment needs a working OpenClaw install with skill installation enabled.
Builder access
access
ACP on the Mac builder is preferred. SSH fallback or a local runner path must also be available if ACP is down.
Codex-capable agent runtime
dependency
The workflow assumes Codex-backed implementation runs and a shell environment that can execute repo verification commands.
Repo-specific verification commands
review
The operator must know which build or typecheck commands actually prove success for the target project.

Declared structure

  • github:henrino3/enterprise-crew-skills/geordi-build-pipeline/
  • github:henrino3/enterprise-crew-skills/geordi-build-pipeline/SKILL.md
  • github:henrino3/enterprise-crew-skills/geordi-build-pipeline/scripts/load-context.sh
  • github:henrino3/enterprise-crew-skills/geordi-build-pipeline/scripts/update-context.sh
  • github:henrino3/enterprise-crew-skills/geordi-build-pipeline/workflows/*.yaml

Verification

Verification language now matches reality. Installable bundles can be tested after install, external bundles should be source-reviewed first, and conceptual entries are reviewed as designs until real artifacts exist.

Source bundle review
Confirm the linked GitHub bundle exposes the expected SKILL.md, scripts, and workflow definitions.
Expected: The source repository contains the referenced files and they match the workflow claims.
Context preflight
Confirm the installed workflow can load project context before it starts implementation.
~/clawd/skills/geordi-build-pipeline/scripts/load-context.sh ~/Code/<project>
Expected: A non-empty context payload with project overview, stack, recent changes, and testing cues.
Type or build verification
Run the repo's actual verification command outside the agent loop.
cd ~/Code/<project> && npx tsc --noEmit
Expected: Command exits cleanly with no type errors.
  • Verify the linked source before install, then verify on the target repo after implementation, not inside the coding loop.
  • If build verification fails, retry implementation with the real errors pasted back into the workflow.
  • Do not push until the separate verification step is green.

Best used for

  • Turn an active plan into implemented repo work
  • Keep a Mac build agent productive without manual babysitting
  • Separate implementation from verification cleanly

Operator notes

  • This listing points at a real installable external skill bundle, not a local bundle directory inside this site repo.