Loading...
Loading...
Found 8,748 Skills
Orchestrates test planning pipeline (research → manual → auto tests). Coordinates ln-521, ln-522, ln-523. Invoked by ln-500-story-quality-gate.
Use this when you need to execute the AI SDLC (Spec Pack) process in the sdlc-dev repository, select/chain together skills from the demand side (raw/solution/prd/prototype/demo) and implementation side (plan/execute/finishing), and use guardrails to avoid context drift, incorrect directory writes, or skipping critical steps under pressure.
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.
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed. Triggers on: 'ask me', 'ask questions about', 'clarify requirements', 'gather requirements', 'I need you to ask', or when the user explicitly wants a question-and-answer session before work begins.
Unified brand discovery that outputs brand.yaml. Merges brand-builder (voice/audience) + design-exploration (visual direction) into one flow. Run once per project to establish brand identity.
Complete end-to-end Android Play Store deployment pipeline setup in one command
Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.
Generic migration orchestrator that reads CHANGELOG.md to understand and execute version-specific migrations
Internal skill. Use cc10x-router for all development tasks.
Use when adding metadata to commits without changing history, tracking review status, test results, code quality annotations, or supplementing commit messages post-hoc - provides git notes commands and patterns for attaching non-invasive metadata to Git objects.
Launch a sub-agent judge to evaluate results produced in the current conversation
Use when finishing a ticket or pull request and the user asks to validate, demo, or sign off on delivered behavior, including non-user-facing changes. Triggers include "UAT", "verify", "walk me through", "show what changed", "can we merge?", "sign off", "acceptance test", "demo this", "ready to merge", "validate the changes", "show me it works", and similar phrases indicating a need for an acceptance walkthrough or demonstration before merge.