roblox-site-architect

Roblox Site Growth Pipeline

Coordinate research, planning, implementation, validation, and growth work for a Roblox-focused site. This Skill is a workflow orchestrator: it defines stage gates and deliverables, but it does not claim to generate or deploy a complete production site by itself.

Operating model

The pipeline has seven ordered stages. Each stage writes one durable Markdown artifact under <project-root>/pipeline/ using the schema in references/pipeline-contracts.md. Read that contract before starting or resuming work.

Use a named supporting Skill only when it is available in the current environment and relevant to the request. If it is unavailable, either:

1. produce an equivalent artifact using available capabilities such as searching the web, reading files, and running local commands; or
2. mark the artifact partial or blocked, record the missing capability and evidence gap, and stop at the affected gate.

Never state that a Skill, tool, build, deployment, submission, or external action ran unless its actual result is available in the current work record.

Status and progression

• complete: all exit criteria are met with cited evidence.
• partial: useful work exists, but named gaps remain. Proceed only when those gaps cannot invalidate the next decision.
• blocked: a required input, authorization, or capability is absent. Do not advance.

When resuming, inspect existing artifacts in numeric order. Preserve prior evidence, note superseded conclusions, and update timestamps instead of silently rewriting history.

Inputs

Establish these before Stage 01:

• the Roblox game name or canonical game URL;
• the intended audience, locale, and business objective if known;
• <project-root> if a target project already exists;
• the user's requested scope: research only, planning, local implementation, or authorized external release.

Unknown inputs stay explicitly unknown. A game name alone does not authorize building, purchasing, publishing, or outreach.