HeroPrompt
Back to docs
Skills

Understanding Skill Workflows

Deep dive into sequential, branching, and iterative workflow patterns.

Updated 2026-02-15

Understanding Skill Workflows

Skills use three primary workflow patterns: sequential, branching, and iterative. Understanding these patterns helps you navigate complex multi-step projects.

Sequential Workflows

Steps must be completed in a specific order. Each step depends on the previous one.

Structure

text
Step 1: Foundation
  ↓
Step 2: Build on Foundation
  ↓
Step 3: Integrate Components
  ↓
Step 4: Finalize

When to Use

  • Dependencies exist — Later steps need outputs from earlier steps
  • Order matters — Doing things out of sequence causes problems
  • Learning paths — Concepts build progressively

Example: API Development

text
1. Design API schema
   → Endpoints, request/response formats, authentication

2. Implement database models
   → Based on schema from Step 1

3. Build API endpoints
   → Using models from Step 2

4. Add tests
   → Validate endpoints from Step 3

5. Document API
   → Based on final implementation

You can't skip Step 2 and jump to Step 3 — the models must exist first.

Branching Workflows

Decision points lead to different execution paths based on your context or requirements.

Structure

text
Start
  ↓
Question / Decision Point
  ├─ Path A (if condition A)
  │   ↓
  │   Steps for Path A
  │   ↓
  └─ Path B (if condition B)
      ↓
      Steps for Path B
      ↓
Converge → Continue Together

When to Use

  • Multiple valid approaches — Different solutions for different contexts
  • Technology choices — React vs Vue, SQL vs NoSQL, etc.
  • Scale variations — Small startup vs enterprise
  • Expertise levels — Beginner vs advanced implementations

Example: Frontend Framework Choice

text
Question: What's your team's expertise?

├─ React Experience
│   ↓
│   Step A1: Set up Create React App
│   Step A2: Configure React Router
│   Step A3: Add React Query for data fetching
│
└─ Vue Experience
    ↓
    Step B1: Set up Vite with Vue 3
    Step B2: Configure Vue Router
    Step B3: Add Pinia for state management

→ Both paths converge at:
  Step 4: Implement authentication
  Step 5: Deploy to production

The branch determines your tech stack, but the later steps (auth, deploy) are the same.

Iterative Workflows

Steps repeat until quality criteria are met or goals are achieved.

Structure

text
Step 1: Initial Implementation
  ↓
Step 2: Review / Evaluate
  ↓
Meets criteria? ─ No → Step 3: Refine → Back to Step 2
  │
  Yes
  ↓
Step 4: Finalize

When to Use

  • Quality refinement — Design iterations, performance tuning
  • Feedback loops — User testing, code review
  • Incremental improvement — Optimization passes
  • Trial and error — Experimentation, A/B testing

Example: UI Design Iteration

text
1. Create initial mockup
   ↓
2. Get feedback from stakeholders
   ↓
3. Check: Does it meet requirements?
   ├─ No → Refine design → Back to Step 2
   │         (Iterate on colors, layout, interactions)
   └─ Yes
      ↓
4. Implement final design in code

You might loop through Steps 2-3 multiple times before moving to Step 4.

Hybrid Workflows

Real-world Skills often combine all three patterns.

Example: Full-Stack App Development

text
Phase 1: Planning (Sequential)
  1. Define requirements
  2. Design database schema
  3. Plan API structure

Phase 2: Backend (Branching)
  Question: What database?
    ├─ PostgreSQL → Use SQLAlchemy
    └─ MongoDB → Use Mongoose

Phase 3: Frontend (Iterative)
  1. Build UI components
  2. Test with users
  3. Refine → Repeat until satisfied

Phase 4: Deployment (Sequential)
  1. Set up CI/CD
  2. Configure hosting
  3. Deploy

Workflow Indicators in Skills

Skills show workflow types using labels:

  • 📋 Sequential — Follow in order
  • 🔀 Branching — Choose your path
  • 🔄 Iterative — Repeat until done
  • 🔗 Hybrid — Mix of patterns

Navigating Workflows

Sequential

  • Progress linearly — Don't skip ahead
  • Validate each step — Ensure quality before moving on
  • Track completion — Check off steps as you finish

Branching

  • Evaluate decision criteria — Answer the questions honestly
  • Commit to a path — Don't switch mid-stream
  • Understand trade-offs — Know why you chose this path

Iterative

  • Set exit criteria — Know when "good enough" is reached
  • Time-box iterations — Avoid infinite loops
  • Track changes — Document what you tried and what worked

Tips for Success

  1. Read the full workflow first — Understand the big picture before starting
  2. Gather prerequisites — Ensure you have tools, access, knowledge needed
  3. Follow the prescribed order — Resist the urge to "optimize" the workflow
  4. Use checkpoints — Validate outputs at each phase before continuing
  5. Take breaks — Complex Skills can take hours or days — pace yourself

Workflow Validation

Each workflow step includes validation criteria. Before moving to the next step, verify:

✅ Sequential workflows:

  • Previous step completed successfully
  • Outputs are ready for next step
  • No errors or warnings

✅ Branching workflows:

  • Decision was made consciously
  • Chosen path matches your context
  • Requirements for this branch are met

✅ Iterative workflows:

  • Exit criteria defined upfront
  • Current iteration shows improvement
  • Ready to finalize or needs another pass

Next Steps

Previous
Skills Overview
Next
Resources