project

Use this skill when the user asks to "fan out agents", "spawn agents", "use an agent team", "parallel agents", "delegate to subagents", "act as team lead", "orchestrate implementation", "fan out teammates", or when a task decomposes into 2+ independent work items (parallel exploration, one implementer per issue, a multi-lens PR review panel). Covers the basic mechanics of spawning, briefing, supervising, and synthesizing subagents and teammates, plus the hard cap on fleet size.

This skill should be used when the user says "set up CI", "create GitHub Actions", "scaffold CI pipeline", "add CI/CD", "configure continuous integration", "create test workflow", "create release workflow", "add pre-commit hooks", "set up linting pipeline", "configure ruff in CI", "configure biome in CI", "add typo checking", or wants to add, update, or customize CI/CD pipelines for their project. For initial project setup including basic CI, see init-project. Use ci-scaffolding for adding or customizing CI/CD in existing projects.

Use this skill when the user asks to "explore this codebase", "understand this repo", "map the architecture", "review our stack", "get up to speed", "break ground" on an unfamiliar project or research field, "what is the state of this project", "audit the architecture", or before planning changes in a codebase you have not worked in. Produces a verified reconnaissance report before any design or edit.

Use this skill when the user asks to "debug", "find the root cause", "figure out why X fails", "investigate this bug", "this test is flaky", "the build broke", "production incident", "why is the output wrong", or when any observed behavior contradicts expected behavior. Covers the reproduce-isolate-prove-fix-verify loop, anti-shortcut gates, and numerical/scientific debugging.

This skill should be used when the user says "create Dockerfile", "dockerize project", "Docker packaging", "container setup", "multi-stage build", "Docker Compose", "containerize application", "create docker-compose.yml", "create .dockerignore", "optimize Docker image", or wants to containerize their project or create Docker configurations.

This skill should be used when the user says "process documents", "extract text from PDF", "OCR this document", "convert PDF to markdown", "extract emails from documents", "parse document", "document conversion", "batch OCR", "extract structured data from PDF", "read PDF", "extract tables from PDF", "convert Word document", "convert docx to markdown", or wants to extract, convert, or process documents and scanned images.

Use this skill when the user asks to "implement this change", "fix this issue", "add this feature", "make this change properly", "ship this", or for any ordinary single-PR development task: one issue, one branch, one pull request. For multi-phase features use epic-dev; for unfamiliar code run codebase-onboarding first; for failing behavior use the debugging skill.

Execute the project epic development workflow for Codex. Use when the user asks for "epic dev", "epic-dev", "/epic-dev", "run the epic workflow", "create an epic", "resume the epic", "--resume", "--next-phase", "--finalize", phased feature delivery, sprint phases, GitHub sub-issues, or git worktrees for multi-phase implementation.

Use this skill when the user asks to "plan this feature", "write an implementation plan", "design before coding", "think through the approach", "review this plan", or before any multi-file change, architectural decision, experiment with a go/no-go outcome, or strategic pivot. Produces a verifiable plan with pre-registered decision gates and an explicit list of open judgment calls.

Use this skill for "initialize project", "set up project", "scaffold project", "create AGENTS.md", "create CLAUDE.md", "set up rules", "create context directory", "vibe rules", "project templates", "init new project", "set up development structure", "create .rules", "create .context", "create ADR", "architecture decision records", "set up GitHub labels", "default issue labels", "project scaffolding", "set up pre-commit hooks", or when the user wants to initialize a new project with cross-agent development templates, structured documentation, and an optional default GitHub label set.

Install, update, or audit general user-level AI coding instructions across Claude Code, OpenAI Codex, GitHub Copilot CLI, and Cursor. Use when the user asks to set up global instructions, personal AGENTS.md or CLAUDE.md defaults, configure instructions for multiple agent systems, avoid repeated downstream project rules, install model-routing defaults, or migrate Claude-only user rules to cross-agent user scope.

Review pull requests and recent code changes across specialized lenses: general code quality, tests, error handling and silent failures, comments and docs, type design, and simplification. Use when the user asks to review a PR, review recent changes, check tests, check error handling, check comments, analyze types, simplify/refine an implementation, run "review-pr", or before merging phase PRs in the epic-dev workflow.

Use when starting work in an existing repository or before a review, planning, or GitHub operation to identify the repository, worktree, shell, terminal, GitHub CLI, credential inheritance, and native-agent surfaces.

This skill should be used when the user says "security audit", "check for vulnerabilities", "security review", "harden project", "dependency audit", "credential scan", "check for secrets", "scan for secrets", "OWASP review", "security checklist", "audit dependencies", "find vulnerabilities", or wants to review their project for security issues, exposed credentials, or vulnerable dependencies.

This skill should be used when the user asks to "update rules", "sync rules", "update AGENTS.md", "update CLAUDE.md", "refresh rules", "update project config", "sync templates", "update vibe rules", "check for rule updates", "update user rules", "update global config", "refresh AGENTS.md", "refresh CLAUDE.md", "sync .rules directory", "what's new in templates", or wants to update existing agent/rules configuration from the latest templates without overwriting customizations.

This skill should be used when executing the epic-dev workflow, creating epic branches, managing sprint phases, working with git worktrees for phased feature development, or when the user mentions "epic dev", "epic-dev", "/epic-dev", "epic workflow", "sprint phases", "phased development", or "git worktree workflow".