codex

Files (1)

• SKILL.md

SKILL.md (first lines)

# Project Kickoff

Run this once at the start of a new project to prepare the repo for Claude Code and Codex collaboration.

## Required outcome

Create these files in the project repo root:

- `AGENTS.md`
- `CLAUDE.md`
- `AGENT_HANDOFF.md`
- `PROJECT_PLAN.md`

Create these repo-local folders and copy in only the relevant approved skills:

- `.claude/skills/`
- `.codex/skills/`

Create the GitHub repo, add the remote, and make the initial commit after the user approves the kickoff plan.

## Workflow

1. Confirm the project repo root. If the project directory does not exist yet, ask where to create it.
2. Ask the user for:
   - Project idea and intended users.
   - Stack or preferred technologies.
   - Goals and first milestone.
   - GitHub repo name.
   - Public or private repo preference.
3. Scan installed skills in both global locations:
   - `C:\Users\User\.claude\skills\`
   - `C:\Users\User\.codex\skills\`
4. Read each candidate skill's `SKILL.md` frontmatter and enough body content to understand its purpose. Ignore missing, malformed, or obviously unrelated skills, but mention any scan errors in the final summary.
5. Identify skills relevant to the new project. For each, record:
   - Skill name.
   - Source agent folder: Claude, Codex, or both.
   - Why it is relevant.
   - Whether it should be copied to `.claude/skills/`, `.codex/skills/`, or both.
6. Before finalizing, check for overlap among relevant skills and already-installed skills in the target repo folders, if any exist. Also compare relevant global skills against each other. If two skills cover similar functionality, stop and ask the user whether to merge or pick one. If the user explicitly chooses to keep both, document the reason. Do not silently copy duplicate functionality.
7. Present the kickoff plan before writing project files:
   - Project summary.
   - Proposed repo name and visibility.
   - Relevant skills and reasons.
   - Any overlap/conflict decisions needed.
   - Files and folders that will be created.
8. After approval, write the four templates, filling project-specific placeholders where the user gave enough information.
9. Create `.claude/skills/` and `.codex/skills/`, then copy only approved relevant skills into the matching repo-local folders. Preserve full skill folders, not just `SKILL.md`.
10. Create the GitHub repo. Prefer the GitHub app tools when available. Otherwise use `gh repo create <name> --private` or `--public` when the GitHub CLI is authenticated. If neither path is available, ask the user to authenticate or provide a remote URL.
11. Initialize git if needed, add all kickoff files, commit with `Initial project kickoff`, and push if a remote is configured.
12. End by summarizing what was created, which skills were copied, the commit hash, and any unresolved follow-up.

## File content requirements

Use the four bundled template files for `AGENTS.md`, `CLAUDE.md`, `AGENT_HANDOFF.md`, and `PROJECT_PLAN.md`. Keep the `read first` rules exact in `CLAUDE.md` and `AGENTS.md`.

Important ownership rules:

- Claude owns brainstorming, planning, and direct edits to `PROJECT_PLAN.md`.
- Codex may suggest `PROJECT_PLAN.md` changes only through the `Evaluate` section in `AGENT_HANDOFF.md`.
- Both agents may work on frontend, backend, infrastructure, documentation, tests, or any other area. The user assigns the task focus per session.
- At the end of every session, the active agent must update `AGENT_HANDOFF.md`.

## Skill overlap rule

Before treating any newly discovered skill as relevant, compare it against already-selected and already-installed skills. If functionality overlaps, flag the overlap to the user and ask whether to merge or pick one. Never silently add duplicate skills.

From shabanakhtar/ai-agent-skills, MIT.

More from shabanakhtar/ai-agent-skills