[WIP] Create Ugotta Codex Codespace template repository

[Copilot]

Implementation Plan: Codex/Copilot-Friendly Template

• Create .github/ directory
• Add .github/copilot-instructions.md - Copilot's constitution for the repo
• Add .github/pull_request_template.md - Structured PR template
• Add docs/CODEX_WORKFLOW.md - Codex usage guidelines
• Add docs/HANDOFF_PROTOCOL.md - Claude → Codex → Copilot handoff packet
• Add .github/workflows/quick-check.yml - Minimal quality gate workflow
• Update README.md with:
  • Codex + Copilot workflow section
  • How to create a new repo from this template section
  • Quality checks section (Codespaces compatibility)
• Verify all changes work correctly
• Run code review
• Run security checks

Original prompt

Create Template #2: ugotta-codex-codespace-template

You’ll do this once, then we’ll reuse it forever.

Step 1 — Create the new repo from your existing template
1. Open your template repo on GitHub: JeffreyLovett/claude-github-codespace-template
2. Click Use this template
3. New repo name: ugotta-codex-codespace-template
4. Set it Public template (so you can clone it into new projects fast)
5. Create repo

⸻

Step 2 — Add a “Copilot does the leg work” work order (in-repo)

We’re going to make Copilot (in GitHub + VS Code/Codespaces) do most of the setup by giving it:
• clear files to create
• exact acceptance checks
• a PR workflow

Add these files (Copilot-friendly)

A) .github/copilot-instructions.md
This is Copilot’s “constitution” for this repo.

Copilot Instructions (Ugotta Codex Template)

Goal

This repository is a reusable Codespaces + Codex-ready starter template. Keep changes safe, minimal, and well-documented.

Rules

• Do not add secrets or tokens. Never commit API keys.
• Prefer small, atomic commits.
• Maintain compatibility with GitHub Codespaces / devcontainers.
• Keep Node and Python versions aligned with existing devcontainer config.
• Update docs when changing setup behavior.

Required Outputs

When completing tasks, ensure:

• README is updated (if behavior changes)
• New docs go in /docs
• Any automation goes in /.github/workflows
• PR description includes: What changed, Why, How to test

Quality Gates

Before marking work complete:

• Confirm repository opens in Codespaces
• Run basic checks if present (lint/test)
• Ensure links in README/docs are valid

B) .github/pull_request_template.md
Forces structured PRs from Copilot/Codex (and humans).

What changed

Why

How to test

Checklist

• No secrets committed
• Docs updated (if needed)
• Works in Codespaces

C) docs/CODEX_WORKFLOW.md
Codex baton-pass + PR discipline.

Codex Workflow (Ugotta Template)

When to use Codex

Use Codex when implementation work is large, repetitive, or needs PR-based delivery.

Standard Task Packet (paste into Codex)

• Objective:
• Repo:
• Constraints:
• Files allowed to change:
• Commands to run:
• Acceptance checks:

Output format

Codex should deliver:

1. PR with changes
2. Summary of changes
3. How to test
4. Notes/risks

D) docs/HANDOFF_PROTOCOL.md
Claude → Codex → Copilot “handoff packet” so nothing stalls at 75%.

Handoff Protocol

Handoff Packet

• Objective (definition of done):
• Current status:
• Next tasks (bulleted, ordered):
• Constraints (must not break):
• Files/paths involved:
• How to verify success:

Rule

If unsure, create a PR draft rather than pushing directly to main.

⸻

Step 3 — Make Copilot do the leg work (two ways)

Option A: Use Copilot Chat in Codespaces / VS Code (recommended)
1. Open the new repo in Codespaces
2. Open Copilot Chat
3. Paste this “work order”:

Copilot Work Order Prompt

You are working in repo: ugotta-codex-codespace-template.

Create the following files exactly (if they don't exist):

• .github/copilot-instructions.md
• .github/pull_request_template.md
• docs/CODEX_WORKFLOW.md
• docs/HANDOFF_PROTOCOL.md

Then update README.md with:

• A short “Codex + Copilot workflow” section
• A “How to create a new repo from this template” section
• A “Quality checks” section (Codespaces opens, node --version, python --version)

Do not add secrets. Keep changes minimal and consistent with existing style.
After edits, provide a short summary of changes.

Option B: Use Copilot directly on GitHub (PR from the web)

If you have Copilot enabled in GitHub web UI:
• Create a branch
• Add/commit the files with Copilot assistance
• Open PR using the PR template

⸻

Step 4 — Add a minimal “quality gate” workflow (optional but smart)

If you want Copilot/Codex to always be forced into “green checks,” add:

.github/workflows/quick-check.yml

This is lightweight and catches broken formatting quickly.

name: quick-check

on:
pull_request:
workflow_dispatch:

jobs:
repo-sanity:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Basic file presence
run: |
test -f README.md
test -d docs
test -d .github
echo "OK"

Copilot prompt to add it

Add a minimal GitHub Actions workflow at .github/workflows/quick-check.yml that runs on pull_request and workflow_dispatch and checks README.md exists and docs/ and .github/ directories exist. Keep it simple.

⸻

Step 5 — The scalable “factory” workflow (repeatable process)

Once this repo exists, every new project becomes:
1. Use this template → create repo
2. Open in Codespaces
3. Run “Copilot Work Order Prompt” (customize for the project)
4. If Copilot hits complexity: hand off to Codex using the Handoff Packet
5. Merge PR after checks

⸻

Your immediate next action (1 minute)

Do Step 1 now (create the new repo from template).
Then tell me the repo is created (or paste the repo link), and I’ll...

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[JeffreyLovett]

Great