From agency-os
Builds a named, branded signature methodology for an agency — a visual framework that turns expertise into sellable IP. Reads memory files and writes memory/methodology.md.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agency-os:agency-methodologyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
In Industry Rockstar's worldview, every advisor sells **a methodology** — a named, visualized, repeatable system that transforms intangible expertise into a defensible product. It's the difference between *"I do consulting"* and *"I install the 6-Pillar Operating System."*
In Industry Rockstar's worldview, every advisor sells a methodology — a named, visualized, repeatable system that transforms intangible expertise into a defensible product. It's the difference between "I do consulting" and "I install the 6-Pillar Operating System."
Read:
memory/mvv.md — voice and reason for beingmemory/offer-stack.md — the outcome you sellmemory/value-drivers.md — which drivers your methodology operates inProduce memory/methodology.md with:
Generate 5-8 candidate names. Each must:
Categories that work:
Test each: "If a client repeated this back to a peer, would they remember it?"
Pick the right number of phases:
For each phase: name + outcome + duration + signature deliverable.
Describe what the methodology looks like when drawn:
Pick one. Write a brief description of how to render it so Gamma / a designer can produce it.
The 90-second sales-call explanation. Format:
"Our methodology is called {NAME}. It's how we {core promise}. There are {N} phases: {phase 1} where {outcome}; {phase 2} where {outcome}; {phase N} where {outcome}. Most agencies skip {phase X} — that's the one that actually makes {Y} stick."
Connect each phase to:
This is what makes the methodology real and not just a graphic.
Write to memory/methodology.md:
# Signature Methodology: {NAME}
**Last updated:** YYYY-MM-DD
## Promise
{one sentence}
## Structure ({N} phases)
| # | Phase | Outcome | Duration | Signature deliverable |
|---|---|---|---|---|
| 1 | ... | ... | ... | ... |
| 2 | ... | ... | ... | ... |
| ... | ... | ... | ... | ... |
## Visualization
**Shape:** {linear / cycle / pillars / gears / pyramid}
**Render description:** {how it looks — for Gamma / designer}
## 90-second teaching version
> "..."
## Phase → tooling map
| Phase | Sprint Framework alignment | Plugin skill | Client artifact |
|---|---|---|---|
| 1 | Strategic Alignment | `agency-strategic-alignment` | Alignment doc |
| 2 | Process Map | `agency-process-map` | Process map |
| ... | ... | ... | ... |
## Naming alternates considered
- ...
- ...
The methodology is named, structured, and mapped. Now every persona has a defensible answer to "what's your process?".
Want a Gamma-ready slide of the visual? Say so and I'll generate the description block. Want this as a downloadable one-pager for the sales kit?
/agency-content-enginecan render it.
npx claudepluginhub wesley248/agency-os-plugin --plugin agency-osGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.