# Example Multi-Skill Workflows in Claude-Skills: A Complete Guide > Explore example multi-skill workflows in Claude-Skills. Discover pre-defined sequences for New Feature Development, Security, and Performance Optimization. Learn how Claude-Skills chains expertise modules for complex tasks. - Repository: [Jeffallan/claude-skills](https://github.com/jeffallan/claude-skills) - Tags: tutorial - Published: 2026-02-16 --- **The claude-skills repository provides pre-defined multi-skill workflows—such as New Feature Development, Security-Focused Development, and Performance Optimization—that chain individual expertise modules into ordered sequences for complex tasks.** The **claude-skills** framework organizes Claude's capabilities into discrete, reusable expertise modules called "skills." By combining these skills into **example multi-skill workflows**, users can execute complex, end-to-end development tasks—from architecture design to deployment—without manually invoking each expertise module. These workflows are formally documented in [`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md) and orchestrated through a command manifest system. ## What Are Multi-Skill Workflows in Claude-Skills? Multi-skill workflows represent the orchestration layer of the claude-skills architecture. Rather than activating a single skill, these workflows trigger a **sequence of skills** that preserve context across steps, allowing Claude to transition smoothly from requirements gathering to implementation to testing. The architecture consists of four layers: 1. **Skill Modules** – Individual expertise files located at `skills///SKILL.md`, each containing front-matter that defines when to trigger the skill. 2. **Skill Combinations** – Curated metadata lists that define which skills work together to form a higher-level capability. 3. **Skill Workflows** – Ordered, step-by-step recipes that reference skill combinations to provide a linear narrative (Step 1, Step 2, etc.). 4. **Command Manifest** – The [`commands/workflow-manifest.yaml`](https://github.com/Jeffallan/claude-skills/blob/main/commands/workflow-manifest.yaml) file that maps human-readable workflow commands to their markdown documentation, enabling Claude to fetch the correct workflow definitions at runtime. ## Example Multi-Skill Workflows Defined in SKILLS_GUIDE.md The primary registry of multi-skill workflows resides in **[`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md)** (lines 99-126), specifically within the "Skill Workflows" and "Skill Combinations" sections. According to the source code analysis, this documentation lists concrete sequences such as: - **New Feature Development** – A complete pipeline from specification to deployment - **Bug Fixing** – Diagnostic and remediation workflows - **Code Review Process** – Systematic examination and approval workflows - **Full-Feature Development** – Comprehensive implementation workflows - **Security-Focused Development** – Hardening and vulnerability assessment workflows The [`docs/ideas/audit-primary-docs.md`](https://github.com/Jeffallan/claude-skills/blob/main/docs/ideas/audit-primary-docs.md) file (lines 64-70) confirms that the "Skill Combinations" section serves as the authoritative source for these workflow patterns. ## Practical Multi-Skill Workflow Examples Users trigger these workflows by prompting Claude with skill names separated by "+" or commas. The following examples demonstrate how the predefined multi-skill workflows execute in practice. ### New Feature Development Workflow This workflow demonstrates the complete lifecycle of shipping a new feature: ```text Help me develop a new user-profile feature. Feature Forge + Architecture Designer + Fullstack Guardian + Test Master + DevOps Engineer ``` **Execution sequence:** 1. **Feature Forge** gathers requirements and creates a technical specification. 2. **Architecture Designer** produces a high-level design, defining data models and API surfaces. 3. **Fullstack Guardian** scaffolds front-end and back-end code using appropriate framework skills (e.g., React Expert + NestJS Expert). 4. **Test Master** writes unit, integration, and end-to-end tests. 5. **DevOps Engineer** generates CI/CD pipelines and handles deployment configuration. ### Security-Focused Development Workflow This workflow hardens existing applications against vulnerabilities: ```text Add authentication to my existing NestJS API and ensure it follows best security practices. Secure Code Guardian + Fullstack Guardian + Security Reviewer + Test Master ``` **Execution sequence:** 1. **Secure Code Guardian** introduces authentication libraries (e.g., Passport, JWT) and security middleware. 2. **Fullstack Guardian** integrates the authentication flow into the existing codebase. 3. **Security Reviewer** executes static analysis passes to identify vulnerabilities and misconfigurations. 4. **Test Master** adds authentication-related integration tests and security test cases. ### Performance Optimization Workflow This workflow diagnoses and resolves database performance issues: ```text My PostgreSQL queries are slow; please optimise them. Architecture Designer + Monitoring Expert + Database Optimizer ``` **Execution sequence:** 1. **Architecture Designer** examines the current database schema and query patterns to identify structural issues. 2. **Monitoring Expert** recommends relevant performance metrics and analyzes current query execution graphs. 3. **Database Optimizer** rewrites inefficient queries, adds strategic indexes, and suggests table partitioning where applicable. ## Key Files Supporting Multi-Skill Workflows The following files constitute the infrastructure for the multi-skill workflow ecosystem: | File | Role | |------|------| | [`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md) | Central registry of skills, skill combinations, and ordered workflow recipes (lines 99-126) | | [`docs/ideas/audit-primary-docs.md`](https://github.com/Jeffallan/claude-skills/blob/main/docs/ideas/audit-primary-docs.md) | Audits documentation and points to the "Skill Combinations" section as the authoritative source (lines 64-70) | | [`commands/workflow-manifest.yaml`](https://github.com/Jeffallan/claude-skills/blob/main/commands/workflow-manifest.yaml) | Maps workflow command files to their markdown descriptions, enabling runtime workflow loading (lines 5-34) | | `skills///SKILL.md` | Individual skill definitions with front-matter that drive activation logic | | `commands/project/*/*.yaml` | Concrete command files that trigger multi-skill workflows from the CLI or Claude's command interface | ## Summary - **claude-skills** organizes expertise into discrete skill modules stored in `skills///SKILL.md`. - **Multi-skill workflows** are predefined sequences documented in [`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md) (lines 99-126) that chain skills for complex tasks. - **Three primary workflow patterns** include New Feature Development, Security-Focused Development, and Performance Optimization. - **Workflow orchestration** relies on [`commands/workflow-manifest.yaml`](https://github.com/Jeffallan/claude-skills/blob/main/commands/workflow-manifest.yaml) to map commands to documentation and execute the correct skill sequences. - **User interaction** requires only natural language prompts with skill names separated by "+" or commas to trigger entire workflows. ## Frequently Asked Questions ### What is the difference between a skill combination and a skill workflow? A **skill combination** is a curated metadata list defining which individual skills work together to form a higher-level capability, serving as the building blocks. A **skill workflow** is an ordered, step-by-step recipe that references these combinations to provide a linear narrative (Step 1, Step 2, etc.) that Claude follows sequentially. According to the source code, both are documented in [`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md), with workflows providing the execution order while combinations define the skill groupings. ### How do I trigger a multi-skill workflow in claude-skills? You trigger workflows by prompting Claude with natural language followed by the specific skill names separated by "+" symbols or commas. For example: `Feature Forge + Architecture Designer + Fullstack Guardian + Test Master + DevOps Engineer`. The [`commands/workflow-manifest.yaml`](https://github.com/Jeffallan/claude-skills/blob/main/commands/workflow-manifest.yaml) file maps these invocations to the correct markdown documentation, enabling Claude to fetch and execute the predefined workflow sequences automatically without manual skill-by-skill activation. ### Where are the individual skill definitions stored? Individual skill definitions reside in `skills///SKILL.md` files throughout the repository. Each skill file contains front-matter metadata that describes when to trigger the skill (e.g., "Use when you need to...") and detailed expertise content. These modular definitions allow the multi-skill workflows to reference and chain them together while maintaining clear separation of concerns between different expertise domains. ### Can I create custom multi-skill workflows? Yes, you can create custom workflows by defining new skill combinations in the [`SKILLS_GUIDE.md`](https://github.com/Jeffallan/claude-skills/blob/main/SKILLS_GUIDE.md) file under the "Skill Combinations" section (around lines 99-126) and referencing them in new workflow entries. You would also need to ensure any new skills follow the standard structure in `skills///SKILL.md` and potentially update [`commands/workflow-manifest.yaml`](https://github.com/Jeffallan/claude-skills/blob/main/commands/workflow-manifest.yaml) (lines 5-34) if you want CLI-accessible commands for your custom workflows. The architecture supports extensibility through its modular skill-combination-workflow hierarchy.