Project Skills

Project skills

Back to Home. Related: Development-Workflow, Operations-Memory.

The canonical project skills are tracked under .claude/skills:

• ship — plan, implement, test, review, reconcile, and open a PR for one issue; always stops at the human merge gate.
• ship-phase — coordinate a dependency-aware phase across issues, then open one PR and stop at the merge gate.

Codex discovers the same sources through relative symlinks in .agents/skills:

.agents/skills/ship       -> ../../.claude/skills/ship
.agents/skills/ship-phase -> ../../.claude/skills/ship-phase

Keep .claude/skills canonical. Edit each skill once there; do not replace the links with copies. Both skills can mutate git/GitHub and are only to be invoked when explicitly requested.

The skill instructions also require isolation for concurrent shipping, full unit and build gates, explicit read-only boundaries for review helpers, reconciliation of roadmap/ADR/changelog, and no automatic merge.

Local-only development skills

Some skills are vendored dev tools kept local, not committed to the repo:

• impeccable — the design/UI skill used to author DESIGN.md and PRODUCT.md. Its code and state (.claude/skills/impeccable/, .agents/skills/* content, .impeccable/) are gitignored; only its two output docs are tracked. Install it locally to run /impeccable; nothing in CI or the shipped artifact depends on it.

Rule: only ship/ship-phase (bespoke, project-specific) are committed under .claude/skills. Large general-purpose skills stay local and are documented here.