Design composable agentic primitives for flexible workflows. Use when creating reusable workflow building blocks, designing SDLC primitives, or building agent operations that can be combined in different ways.
Designs reusable workflow primitives (Classify, Plan, Build, Test, Ship) that can be composed for different problem types like bugs, features, and chores. Use when creating flexible SDLC workflows or customizing agent operations for specific organizational needs.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install google-ecosystem@melodic-softwareThis skill is limited to using the following tools:
Guide design of composable agentic primitives for flexible workflow creation.
"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."
| 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 |
What type of work?
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 |
Ensure correct sequencing:
Where should failures stop the pipeline?
Plan -> Build -> [Test GATE] -> Review -> [Review GATE] -> Ship
Classify -> Plan -> Build -> Test -> Review -> Document -> Ship
Classify -> Plan -> Build -> Test -> Review -> Document -> Ship
| |
[GATE] [GATE]
Classify -> Patch -> Test -> Ship
Review -> Patch -> Test -> Ship
Consider:
Classify -> Plan -> [Compliance Review] -> Build -> Test ->
[Security Scan] -> Review -> Document -> [Approval] -> Ship
Build -> Test -> Ship (no planning for small changes)
Provide composition design:
## Workflow Composition
**Problem Class:** {type}
**Entry Trigger:** {trigger}
**Exit Criteria:** {criteria}
### Primitives Selected
1. Classify - Categorize the task
2. Plan - Create implementation spec
3. Build - Implement changes
4. Test - Validate functionality
5. Ship - Deploy to production
### Composition Flow
Classify -> Plan -> Build -> Test -> Ship | [GATE: Must pass]
### Validation Gates
- After Test: Abort if tests fail
- After Review: Optional based on confidence
### Customizations
- [Organization-specific additions]
Date: 2025-12-26 Model: claude-opus-4-5-20251101
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.