stoa: Skill for Claude Code

HEGEMON Pattern Extraction — $ARGUMENTS

IP Guard: Patterns describe methodology and approach, never verbatim proprietary code, client names, pricing, or sensitive business data. Anonymize all examples. See hegemon/CLAUDE.md anonymization rules.

Step 1: Identify the Pattern

From the current session's work, identify what is reusable:

1. What recurring problem was solved? (not a one-off fix)
2. Is this transferable to other projects (PRAXIS, ATHLOS, OIKOS)?
3. Does a similar pattern already exist? Check hegemon/patterns/ directory

If the answer to #1 or #2 is "no", this is NOT a pattern — it's a project-specific solution. Skip extraction.

If a similar pattern exists, update it (add to Reuse Log) instead of creating a new one.

Step 2: Categorize

Determine the pattern category:

Category	Examples	Directory
architecture	System design, infrastructure patterns, integration patterns	patterns/architecture/
workflow	Development process, CI/CD, session management, estimation	patterns/workflow/
validation	Review processes, quality gates, Council patterns	patterns/validation/
prompt	Effective prompt structures, agent delegation patterns	patterns/prompt/
communication	Stakeholder management, reporting, documentation patterns	patterns/communication/

Step 3: Assign Pattern ID

Read existing patterns to find the next available ID:

ls hegemon/patterns/*/HEG-PAT-*.md | sort -t- -k3 -n | tail -1

Next ID = highest existing + 1. Format: HEG-PAT-XXX (zero-padded to 3 digits).

Step 4: Write the Pattern File

Create the pattern file using the HEGEMON template. The file MUST include ALL sections:

# HEG-PAT-XXX: [Pattern Name]

## Metadata
- **Origin**: [Project] / [Ticket or context]
- **Category**: [architecture | workflow | prompt | validation | communication]
- **Supervision Tier**: [AUTOPILOT | CO-PILOT | COMMAND]
- **Created**: [YYYY-MM-DD]
- **Last Updated**: [YYYY-MM-DD]

## Problem
[What recurring problem does this pattern solve? 2-3 sentences.]

## Solution
[The reusable approach — methodology, decision trees, workflow structures.
NOT verbatim code. Describe the pattern abstractly enough to apply across projects.]

## Constraints
[When NOT to use this pattern. Preconditions. Limitations.]

## Reuse Log
| Date | Project | Outcome | Adaptations |
|------|---------|---------|-------------|
| [today] | [origin project] | Extracted | Initial extraction |