ceo

Use when starting work on any project (technical or non-technical) to understand structure, standards, and best practices before making changes

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Apply the code-quality checklist to audit files or directories and produce a Markdown report with findings and suggested fixes. Use when asked to "audit these files", "run a quality check", "code quality review", or "check against the code-quality checklist".

Generate a structured deep research prompt. USE WHEN the user needs to research a complex topic, market, or bug deeply. Capabilities include objective clarification, tech stack validation, and prompt generation.

Use for go-to-market strategy, user acquisition, channel analysis, and performance marketing.

Generate documentation for an existing project. USE WHEN onboarded to a new codebase OR documenting legacy code. Capabilities include architectural mapping, tech stack inventory, and technical debt documentation.

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Transform user requests into detailed, precise prompts for AI models. Use when users say "promptify", "promptify this", or explicitly request prompt engineering or improvement of their request for better AI responses.

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Generate custom checklist for the current feature based on user requirements

Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync

Execute implementation planning workflow using the plan template to generate design artifacts

Use when user wants to work with specifications or create feature requirements following the spec-driven development workflow

Create or update feature specification from natural language feature description

Generate actionable, dependency-ordered tasks.md for the feature based on available design artifacts

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Retrieve up-to-date documentation for software libraries, frameworks, and components via the Context7 API. This skill should be used when looking up documentation for any programming library or framework, finding code examples for specific APIs or features, verifying correct usage of library functions, or obtaining current information about library APIs that may have changed since training.

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment