workflow-init-project

Orchestrate Codex project initialization with Go, devcontainer, and Kubernetes workflows.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill workflow-init-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-init-project
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/workflow-init-project
Command: npx skills add https://github.com/joleques/northstar-ai --skill workflow-init-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many new projects lack a consistent, reproducible initialization process that wires together language-specific scaffolding, development container setup, and Kubernetes manifests; this causes onboarding friction, configuration drift, and wasted developer time. This Skill provides an orchestrated workflow to collect project parameters, run the appropriate initializers, and produce a ready-to-adjust project structure.

Core Features & Use Cases

  • Guided Parameter Collection: Prompt for project name, directory, stack selection, default extensions, and Kubernetes parameters, then present a confirmation summary.
  • Conditional Tooling Execution: Automatically run go-initializer when the selected stack is Go, then create a devcontainer and generate Kubernetes artifacts.
  • Integration Behavior: Handles cases where legacy Jenkins workflows or optional skills are missing by explicitly informing the user and continuing with available steps.
  • Use Case: Quickly bootstrap a new Codex-targeted Go service with a reproducible devcontainer and Kubernetes manifests for immediate development and CI onboarding.

Quick Start

Initialize a Codex project named my-app using the Go stack, create a devcontainer, and generate Kubernetes manifests with default parameters.

Frequently Asked Questions about workflow-init-project

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

FAQPage Schema
How do I bootstrap a new Go project with a devcontainer and Kubernetes manifests?

To bootstrap a Go project with a devcontainer and Kubernetes manifests, you can use a guided workflow that collects project parameters, runs go-initializer for the Go stack, and generates the necessary container and k8s artifacts for onboarding.

What is the best way to set up a reproducible development container for a Codex project?

Setting up a reproducible development container for a Codex project involves running an initialization workflow that collects your stack selection and creates a devcontainer configuration alongside your project scaffolding.

Can I use this project initialization workflow if my Jenkins workflows or optional skills are missing?

You can still use this initialization workflow if Jenkins workflows or optional skills are missing, as it explicitly informs you of absent dependencies and continues executing the available steps.

Does the Codex project bootstrap process support stacks other than Go?

The Codex project bootstrap process conditionally invokes go-initializer specifically when the Go stack is selected, while still collecting general project parameters like directory and Kubernetes settings for other configurations.

How do Kubernetes parameters get integrated during new service onboarding?

Kubernetes parameters are integrated during new service onboarding by collecting them through a guided parameter prompt, confirming the choices, and then generating the corresponding Kubernetes manifests as part of the final project structure.