spacex-maker

Name: spacex-maker
Availability: InStock
Author: kentoku24

Generate executable SpaceX mission task code from parsed specs each cycle.

Updated Aug 27, 2026

Search Tags:#automation #telemetry #maker #cycle #design-implementation #mission-control #spacex

Ready to run

npx skills add https://github.com/kentoku24/project-guild --skill spacex-maker

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spacex-maker
Source: https://github.com/kentoku24/project-guild/tree/main/docs/skills/spacex-maker
Command: npx skills add https://github.com/kentoku24/project-guild --skill spacex-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SpaceX mission tasks often suffer from handoffs between design and implementation, causing delays and misalignment. The Maker skill merges design and implementation into a single, cycle-driven agent that delivers runnable artifacts each cycle.

Core Features & Use Cases

SPEC → BUILD → OBSERVE cycle integration to rapidly iterate on mission tasks
Lightweight Maker persona that bridges architecture and code for faster delivery
Telemetry-ready outputs and observable artifacts produced every cycle
Works within the /spacex workflow to auto-assemble and validate task components

Quick Start

Start a new Maker cycle by telling Mission Control the cycle number, the objective, and any mission issues.

Frequently Asked Questions about spacex-maker

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

FAQPage Schema

How do I automate spec-to-build workflows for mission control cycles?▼

To automate spec-to-build workflows, the Maker skill combines design and code into a single cycle-driven agent, reading mission issues and parsing specs to deliver runnable artifacts every cycle.

What is a cycle-driven agent for SpaceX mission tasks?▼

A cycle-driven agent for SpaceX mission tasks merges architecture design and code implementation into a single automated process, executing spec-to-build-observe iterations to deliver telemetry-ready outputs each cycle.

How do I bridge the gap between design and implementation in automated mission tasks?▼

You bridge design and implementation by applying a lightweight Maker persona within the SpaceX workflow, auto-assembling and validating task components to prevent handoff delays and misalignment.

Does the SpaceX Maker skill require specific dependencies to generate code skeletons?▼

No external dependencies are required to generate code skeletons, as the Maker skill operates independently within the SpaceX workspace to parse specs and implement mission tasks cycle by cycle.

How do I start a new Maker cycle for mission task automation?▼

To start a new Maker cycle, provide Mission Control with the cycle number, the objective, and any mission issues to trigger the automated spec-to-build workflow for executable task delivery.

What are the limitations of using a cycle-based execution approach for mission-maker tasks?▼

The cycle-based execution approach is limited to operating within the SpaceX workspace workflow, relying on readable mission issues and parseable specs to generate telemetry artifacts and validate task components.