composable-primitives

# Composable Primitives Skill

Guide design of composable agentic primitives for flexible workflow creation.

## When to Use

- Designing new agentic workflows
- Customizing SDLC for specific needs
- Mapping problem classes to primitives
- Building organization-specific compositions

## The Secret

> "The secret of tactical agentic coding is that it's not about the software developer lifecycle at all. It's about composable agentic primitives you can use to solve any engineering problem class."

## Core Primitives

| Primitive | Purpose | Input | Output |
| --- | --- | --- | --- |
| **Classify** | Categorize input | Issue/task | Classification |
| **Plan** | Create implementation spec | Issue | Plan file |
| **Build** | Implement the plan | Plan file | Code changes |
| **Test** | Validate functionality | Code changes | Pass/fail |
| **Review** | Validate alignment | Spec + code | Issue list |
| **Patch** | Fix specific issues | Issue description | Targeted fix |
| **Document** | Generate documentation | Code changes | Doc files |
| **Ship** | Deploy to production | Validated code | Deployed state |
| **Branch** | Create isolated context | Classification | Branch name |
| **Commit** | Save checkpoint | Changes | Commit hash |

## Composition Workflow

### Step 1: Identify Problem Class

What type of work?

- Chore (simple, low risk)
- Bug (medium complexity, clear criteria)
- Feature (complex, full SDLC)
- Hotfix (urgent, minimal process)
- Documentation (content only)

### Step 2: Select Primitives

Based on problem class, choose primitives:

| Problem Class | Primitives |
| --- | --- |
| Chore | Classify -> Build -> Test -> Ship |
| Bug | Classify -> Plan -> Build -> Test -> Review -> Ship |
| Feature | Full SDLC |
| Hotfix | Patch -> Test -> Ship |
| Documentation | Document -> Review -> Ship |

### Step 3: Order by Dependencies

Ensure correct sequencing:

- Plan before Build (Build needs plan)
- Build before Test (Test needs code)
- Test before Ship (Ship needs v