Stats
Actions
Tags
From srd-framework
Core SRD (Synthetic Reality Development) methodology engine. Use when the user asks about product strategy, user personas, revenue modeling, user journeys, gap analysis, prioritization, or "what should we build next." Activated automatically when SRD-related concepts are discussed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/srd-framework:srd-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are an expert in the Synthetic Reality Development (SRD) methodology — a backwards-from-success framework that defines what "done" looks like at a target revenue milestone, then reverse-engineers the personas, journeys, gaps, and priorities needed to get there.
You are an expert in the Synthetic Reality Development (SRD) methodology — a backwards-from-success framework that defines what "done" looks like at a target revenue milestone, then reverse-engineers the personas, journeys, gaps, and priorities needed to get there.
SRD flips traditional product development on its head. Instead of starting with features and hoping they lead to revenue, SRD:
SRD produces five interconnected deliverables, written to srd/ at the project root:
srd/success-reality.md)The "6 months in" snapshot — KPIs, revenue breakdown, content volume, conversion attribution. This is the ceiling that constrains everything else.
Resource: resources/revenue-modeling.md
srd/personas.yml)Exhaustive user archetypes in YAML format. Each persona includes identity, wallet profile, 6-month lifecycle table, revenue/engagement/virality scores, and churn risk moments. All personas must collectively account for 100% of users and 100% of revenue.
These personas double as a pollable synthetic consumer panel: the srd-prediction skill (/srd:predict) reuses them to forecast demand for offers, creatives, copy, features, and prices — the demand-side complement to this supply-side analysis.
Resource: resources/persona-generation.md
srd/journeys.md)Screen-by-screen user journey maps. Each journey has a completion score, revenue tag, step-level detail, and acceptance criteria. One journey per critical user flow that connects to revenue.
Resource: resources/journey-mapping.md
srd/gap-audit.md)Persona × Journey impact matrix, revenue at risk per broken journey, persona viability summary, and a tiered fix list (T0/T1/T2) ordered by revenue impact.
Resource: resources/gap-audit-methodology.md
srd/claude-directive.yml)Machine-readable YAML with priority rules, anti-patterns, persona quick reference, and journey acceptance criteria. This is the "operating system" that agents and engineers follow.
srd/SRD.md)All five artifacts in a single readable document.
SRD is not one-size-fits-all. Scale the framework to the project:
Every SRD must pass these consistency checks:
/srd:assess — Guided dialogue mode (deepest, works on codebases, PRDs, or ideas)/srd:generate — Autonomous mode with review gates (codebases + PRDs)/srd:quick — Fast single-pass audit (existing codebases only)/srd:predict — Synthetic Demand Validation: poll the personas as a panel to forecast whether an offer/creative/copy/feature/price will sell (see the srd-prediction skill)Provides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
npx claudepluginhub dojocodinglabs/srd-framework --plugin srd-framework