Menu
One-line description of what this skill teaches
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | skill-name-here |
| version | 1.0.0 |
| author | jwilger |
| repository | jwilger/claude-code-plugins |
| description | One-line description of what this skill teaches |
| tags | ["relevant-tag-1","relevant-tag-2"] |
| portability | universal | high | medium | tool-specific | mcp-specific |
| dependencies | [] |
Version: 1.0.0 Portability: [Universal | High | Medium | Tool-Specific | MCP-Specific]
[2-3 sentences describing what this skill teaches and why it matters]
Purpose: [What problem does this solve? What does it enable?]
Scope: [What's included in this skill? What's excluded?]
[Detailed explanation of the principle]
Why this matters: [Rationale]
How to apply: [Concrete guidance]
Example:
[Code, markdown, or other example demonstrating the principle]
[Continue pattern for all principles...]
Rationale: [Why these boundaries exist]
Scenario: [When to use this pattern]
Approach:
Example:
[Concrete example]
[Continue pattern...]
Works well with:
Prerequisites:
Problem: [What goes wrong] Solution: [How to avoid or fix]
[Continue pattern...]
Context: [Setup/situation]
Application:
[Detailed example showing skill in action]
Outcome: [Result]
[Continue pattern...]
Use this checklist to verify you're applying this skill correctly:
Source Documentation:
Related Skills:
External Resources:
Extraction Source: sdlc/commands/shared/[original-protocol-name] Extraction Date: YYYY-MM-DD Last Updated: YYYY-MM-DD Compatibility: Claude Code 2.1+, Cursor, Windsurf, Cline License: MIT (or as specified)
Multi-agent orchestration patterns for delegation, coordination, and conflict resolution
Event Modeling facilitation methodology for event-sourced system design
Local task management using the dot CLI with file-based markdown storage, parent-child hierarchies, and blocking dependencies. Use when managing tasks, creating stories or epics, tracking work items, breaking down features, writing acceptance criteria, or querying task status. Triggers on: "create a task", "add a story", "break down this feature", "what's ready to work on", "show task status", "dot add", "dot ls", "dot ready", "dot tree", or any reference to the dot CLI or .dots/ directory.
Knowledge accumulation and retrieval patterns for file-based agent memory
Red-green-domain TDD cycle with strict phase boundaries and domain modeling review
Brad Frost's Atomic Design methodology for building UI component hierarchies