recipe

Chains Claude Code Utils commands to automate development workflow orchestration for common scenarios.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/trungtnm/claude-code-utils --skill recipe-trungtnm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recipe
Source: https://github.com/trungtnm/claude-code-utils/tree/main/plugins/skills/recipe
Command: npx skills add https://github.com/trungtnm/claude-code-utils --skill recipe-trungtnm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-built workflow recipes streamline development by chaining Claude Code Utils commands in a deterministic order, eliminating manual sequencing and ensuring prerequisites are respected.

Core Features & Use Cases

  • Pre-built workflows for common patterns such as new-feature, bug-fix, refactor, and spike.
  • Automatic sequencing that checks prerequisites and skips completed phases to accelerate delivery.
  • Supports single-agent and orchestrator-based execution with integrated quality gates and traceability.

Quick Start

Start a new-feature recipe to automatically plan, execute, review beads, and finalize the feature.

Frequently Asked Questions about recipe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate end-to-end development workflows for feature lifecycles?

Automate end-to-end development workflows by chaining Claude Code Utils commands in a deterministic order to handle feature lifecycles like new-feature, bug-fix, refactor, and spike. This eliminates manual sequencing and ensures prerequisites are respected.

Can I skip completed phases when running a bug-fix or refactor workflow?

Completed phases can be skipped during workflow orchestration to accelerate delivery. The automatic sequencing mechanism checks prerequisites and identifies finished steps, allowing the workflow to resume without repeating unnecessary work.

Does workflow orchestration support both single-agent and orchestrator executions?

Workflow orchestration supports both single-agent and orchestrator-based executions. It requires explicit triggers to start and integrates with planning, testing, and bead-tracking tools to provide quality gates and traceability across both execution modes.

What is the best way to ensure prerequisites are respected during development planning?

The best way to respect prerequisites during development planning is using pre-built workflow recipes that chain commands deterministically. This approach checks prerequisites automatically before executing subsequent phases, preventing sequence violations.

Why do I need explicit triggers for workflow orchestration?

Explicit triggers are required for workflow orchestration to ensure deterministic control over when automated command chaining begins. This prevents unintended execution of development workflows while maintaining the integrity of prerequisite checks and phase sequencing.