feature-implementer
Implement feature steps using git worktrees, build and test adaptively, update implementation plan, and generate test plans. This skill should be used when ready to implement one or more steps from an implementation plan, automatically adapting to any framework, language, or project structure.
ux-stitch-iterate
Iterate an existing Stitch design using project and screen context, UX docs, decisions, and anti-slop constraints.
feature-research
Guide interactive research and POC creation to understand features deeply. This skill should be used when planning to implement a new feature and needing to research design patterns, understand integration points in the codebase, consult documentation via MCP Deep Wiki, or create minimal POCs to validate concepts. Can receive CDC.md from feature-specification as input for clear requirements.
feature-specification
Guide iterative specification and CDC (Cahier Des Charges) creation through deep questioning, context analysis, and proactive proposals. Use this skill BEFORE feature-research to clarify requirements, identify prerequisites, define scope, and document complete specifications. Triggers when starting a new feature, task, bug fix, or refactoring and requirements need clarification.
feature-workflow
Orchestrate complete or partial feature implementation workflow with configurable phases. This skill should be used to run the full workflow (specification → research → plan → implement → test → fix) or specific phases, coordinating between all feature-implementation skills automatically.
git-workflow-manager
Manage git worktrees with GitFlow conventions for parallel development. This skill should be used when creating, managing, or cleaning up git worktrees, following standard GitFlow branch naming (feature/, fix/, hotfix/). 100% generic and reusable across all projects.
implementation-planner
Generate comprehensive implementation plans with checkboxes, dependencies, and parallelization details. This skill should be used after feature research is complete to create structured, step-by-step implementation plans that track progress, identify dependencies between tasks, and enable multiple developers to work in parallel.
linear-issue-creator
Create well-formed Linear issues on command for any project. Accepts a GitHub URL or local disk path as project context, explores the codebase and documentation adaptively, then creates a structured issue using DEV-007 templates (Bug, Feature, Tech-Debt, Idée, Hotfix) via the Linear MCP.
test-executor
Execute tests adaptively, analyze failures, generate detailed failure reports, and iterate until tests pass. This skill should be used when running tests from a test plan, working with any language, framework, or test type (E2E, API, unit, integration, performance).
test-fixer
Fix failing tests based on failure reports, verify fixes, and iterate until all tests pass. This skill should be used after test-executor generates failure reports, providing systematic debugging and fixing strategies that work with any framework or language.
test-plan-generator
Generate intelligent, non-redundant test plans based on implementation changes. This skill should be used after implementing features to create comprehensive yet efficient test plans with proper coverage across unit, integration, API, and E2E tests without duplication.
ux-audit
Audit a page, flow, feature, or component for UX, UI, interactions, accessibility, responsive behavior, and anti-slop quality before coding.
ux-bootstrap
Initialize UX/UI DesignOps memory in a WorkflowSkills project. Use when a project has no UX docs, no DESIGN.md, or needs Codex-ready product design onboarding.
ux-code-to-stitch
Translate existing code, routes, components, and DESIGN.md into Stitch-ready briefs or design system inputs.
ux-component-spec
Specify reusable UI components, states, accessibility, responsive behavior, tokens, and implementation constraints before coding.
ux-design-sync
Synchronize DESIGN.md, UX DesignOps docs, Stitch mappings, visual debt, and implementation reality after UI changes.
ux-flow
Define user flows, state matrices, edge cases, and UX acceptance criteria for a UI feature before implementation.
ux-implement-from-stitch
Implement a selected Stitch direction into an existing frontend while preserving app logic, architecture, components, and WorkflowSkills documentation.
ux-polish
Apply a focused UI polish pass while preserving behavior, design system consistency, accessibility, and WorkflowSkills docs.
ux-storybook
Use Storybook as a UI state catalog for component specification, visual QA, and WorkflowSkills UX documentation.
ux-visual-verification
Verify UI changes with the Codex Browser plugin by default, or Playwright/Storybook/equivalent rendering tools when needed, using screenshots, responsive checks, focus states, and accessibility basics. Blocks if no rendering tool is available.
workflow-challenger
Critical review and gap analysis skill that can be invoked at any workflow stage. Use to challenge decisions, identify missing specifications, verify coherence, and surface unaddressed questions in CDC, findings, plans, or any deliverable. Acts as a devil's advocate by deeply analyzing codebase, project documentation ([DOC]-* folders), and context.
skill-name
Describe what this skill does and when to use it.
curate-workbuddy-resource
Review a public repository, document, Skill, MCP integration, workflow, or guide for a WorkBuddy resource directory and recommend include, hold, or exclude using traceable relevance, quality, maintenance, license, provenance, and safety evidence. Use when triaging or re-checking a candidate; not for installing or executing the candidate.
document-quality-review
Review Markdown, Word, PDF, spreadsheet, or presentation deliverables for factual support, internal consistency, completeness, usability, and visible quality before delivery.
skill-security-audit
Audit a third-party Agent Skill, MCP server, connector, or desktop extension before installation by tracing instructions, executable code, dependencies, permissions, credentials, data flow, and irreversible actions.
source-backed-research-brief
Research a defined question and produce a concise, decision-ready brief with traceable current sources, explicit uncertainty, conflicting-evidence handling, and separated facts and inference. Use for market, product, policy, vendor, technical, or other web-backed research; not for literature reviews requiring formal systematic-review methodology.
adr-review
Use when reviewing code for Architecture Decision Record (ADR) compliance during refactoring or code review - checks code against all project ADRs and reports violations with specific fixes
discovery-tree-workflow
Use when planning and tracking work - creates visible, emergent work breakdown using TypeScript API with just-in-time planning and hierarchical task trees
dispatching-incremental-tdd
Use when implementing features or adding functionality - dispatches incremental-tdd-agent that enforces ONE test at a time, preventing batch test writing that defeats incremental design discovery. Maintains discipline through entire feature implementation (10+ test cycles)
dispatching-systematic-debugging
Use when encountering bugs, test failures, unexpected behavior, errors, or performance problems - dispatches systematic-debugging-agent that enforces 4-phase process (root cause investigation, pattern analysis, hypothesis testing, implementation) to prevent quick-fix attempts and ensure proper debugging
incremental-tdd
Use when implementing features or refactoring with TDD - enforces writing ONE test at a time, implementing minimal code to pass, then repeating, preventing batch test writing that defeats incremental design discovery
security-audit-review
Use when reviewing code for security concerns — token handling, injection surfaces, auth paths, secret exposure, and permissions scope. Invoked during adversarial review post-implementation, as an audit-loop reviewer node, or on PRs that touch auth/secrets/deploy surfaces. Distinct from the built-in `/security-review` slash command (which runs an automated scan); this skill guides a human or reviewer-agent through the audit.
sharpening-the-knife
Use when discovering a useful technique, pattern, or insight during work - pause to capture it as a skill before the knowledge evaporates, preventing the "I'll remember this" trap that causes expertise loss
spec-compliance-review
Use when reviewing an implementation against its spec, plan, or written brief — during adversarial review post-implementation, as an audit-loop reviewer node in a pipeline, or at spec-time to self-audit for internal consistency. Maps each spec clause to code evidence and flags drift.
test-watch-focused-patterns
Use when developing tests or refactoring test suites - run tests in watch mode with focused file patterns to get instant feedback on specific test files without running the entire suite
testing-review
Use when reviewing a test harness for adequacy — post-implementation (adversarial review), as an audit-loop reviewer node, or pre-spec to verify that planned coverage reaches every acceptance criterion. Classifies tests as outside-in vs unit, and flags structural blind spots that let green tests miss real regressions.
using-jj
Use when working with Jujutsu (jj) version control for task management and change tracking - provides workflows for examine-commit-work-squash cycle, checkpointing progress, and managing working copies
wishful-thinking-programming
Use when building features with unknowns or uncertainties - start from well-understood parts (business logic, UX, pure functions), write code as if ideal collaborators exist, use mocks to define APIs through usage, preventing analysis paralysis from trying to understand everything upfront
writing-commit-messages
Use when reviewing commit messages for compliance with the seven rules from cbea.ms/git-commit - checks subject line length, imperative mood, line wrapping, and that the message explains what and why
conductor-development
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion, and follows the spec-driven methodology.
k8s-troubleshooter
|
android-additional-tests
Optional - Add comprehensive tests beyond the basic smoke test
android-app-icon
Generate Android adaptive icons from Iconify's 200k+ open source icons
android-ci-tests
Setup GitHub Actions workflow for running Android tests in CI
android-e2e-testing-setup
Setup UI Automator 2.4 smoke test for validating app launches (works with debug and release builds)
android-espresso-dependencies
Add Espresso and AndroidX Test dependencies to Android project
android-fastlane-setup
Setup Fastlane for Play Store deployment with supply and screengrab
android-keystore-generation
Generate production and local development keystores for Android release signing
android-playstore-api-validation
Create and run validation script to test Play Store API connection
Page 1133 of 1660 · 82972 results