Backend implementation specialist. Use proactively when: creating or modifying API endpoints, implementing business logic, handling server-side data processing, building authentication or authorization, creating background jobs or scheduled tasks, integrating with third-party services or webhooks, and optimizing…
Copywriter and SEO specialist. Use proactively when: writing or refining landing page copy, marketing content, or product descriptions; defining brand voice and tone; crafting CTAs; planning keyword strategy or content clusters; optimising on-page SEO (title tags, meta descriptions, heading hierarchy, URL slugs)…
Database design and optimization specialist. Use proactively when: designing new database schemas or tables, writing or reviewing database migrations, diagnosing slow queries or N+1 problems, planning indexing strategy, making decisions about data relationships or normalization, and evaluating database technology or…
Containerization specialist. Use proactively when: creating or modifying Dockerfiles, setting up docker-compose for local development or production, optimizing image size with multi-stage builds, configuring container networking or volumes, managing secrets in containerized environments, adding health checks…
Documentation specialist. Use proactively when: a user-facing feature is completed or changed, the onboarding flow is updated, API endpoints are added that affect user experience, any documentation appears outdated or missing, or when preparing a release and docs need to be current. Not for inline code comments…
Frontend implementation specialist. Use proactively when: creating or modifying UI components, implementing pages or layouts, handling client-side state management, working with CSS or styling, integrating with APIs from the client side, optimizing frontend performance, fixing rendering bugs, or improving bundle size…
Project management specialist and TODO.md governor. Use proactively when: the user asks what to work on next, wants to plan a sprint or milestone, needs a feature broken down into tasks, asks about project progress or blockers, wants to reprioritize the backlog, or after a feature is completed and the backlog needs…
QA and testing specialist. Use proactively when: writing Playwright E2E tests for new or modified features, investigating failing tests, assessing test coverage gaps, designing a test strategy for a feature, setting up or configuring test infrastructure, and verifying that implemented behavior matches PRD functional…
Systems architecture specialist. Use proactively when: designing new features before implementation begins, evaluating technology choices, planning system integrations, addressing scalability or performance architecture concerns, resolving conflicts between system components, and recording Architecture Decision…
UI/UX design specialist. Use proactively when: designing new user flows before implementation, creating component or interaction specifications, making design system decisions (colors, typography, spacing, components), evaluating accessibility compliance, reviewing user journeys against PRD requirements, or when a…
Runs after a tool call finishes for Write and Edit tool calls, executing format-on-write.sh and check-naming.sh (2 commands). From josipjelic/orchestrated-project-template.
Save-and-commit checkpoint — verifies docs are updated, runs available linting/tests, then creates a WIP commit so no work is lost before pausing. Usage: /checkpoint [optional: short description of current state].
Orchestrate a multi-agent task — analyzes dependencies, builds a wave execution plan, coordinates with the project manager, creates a feature branch, and runs specialist agents in parallel and sequential waves. Usage: /orchestrate.
Pre-release quality pass — checks backlog readiness, runs QA, updates docs, and verifies the CI/CD pipeline before shipping. Usage: /release [optional: version label e.g. v1.2.0].
Run project onboarding — reads STARTHERE.md and executes the protocol there. Auto-detects new project vs. existing codebase, interviews you (new) or reads the code and asks only what it can't answer (existing), fills docs, builds the backlog. Usage: /start.
Project health overview — renders a structured status card from TODO.md, recent git history, open PRs, and PRD open questions. Read-only. Usage: /status.
Pull the latest agent definitions, skills, hooks, rules, and templates from the upstream orchestrated-project-template repository into this project's .claude/ directory, with a diff summary and confirmation before applying. Usage: /sync-template.